Scarlett King
07/15/2021, 3:34 PMKevin Kho
07/15/2021, 4:09 PMScarlett King
07/15/2021, 4:47 PMMariia Kerimova
07/15/2021, 5:08 PMkubectl get secret
)? And did you set existingSecret
in the helm chart?Scarlett King
07/16/2021, 8:25 AMMariia Kerimova
07/16/2021, 2:38 PMpostgresql-password
and value from your KeyVault, and set existingSecret to the name of the Kubernetes secret you've created, then it should work.Scarlett King
07/20/2021, 9:11 AMMariia Kerimova
07/20/2021, 2:15 PMDali
07/21/2021, 8:27 PMpostgresql.postgresqlPassword
with postgresql.existingSecret
set to null
. Did anyone get this running?
• When using postgresql.existingSecret
we misread the comment and thought that the secret should be called postgresql-password
, rather than the key. We should have paid more attention.
• It looked like the setup expects a database called prefect
to exist in postgresql instance. Once we created it manually things progressed further. The init container seems to assume it exists and starts with upgrade.
• Last piece of the puzzle was that our postgresql instance was at quite an old version (9.6) and didn't support all the syntax in migration scripts - once we upgraded postgresql to 11 (Spinal Tap reference coincidental) we were finally able to get the whole thing running.
Hope this helps, either to folks going down the same route or you Prefect folks with updating docs/scripts.
And finally big shout out to @Laura Lorenz ❤️ for the youtube presentation - it made things look a lot less scary and @Zanie ❤️ for getting the helm chart together - without it we may not even embark on this journey or may have abandoned it at some point.Mariia Kerimova
07/21/2021, 11:19 PMZanie
07/22/2021, 12:12 AM