-
Notifications
You must be signed in to change notification settings - Fork 993
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
K8s 1.16 compatibility: statefulset moved to apps/v1 #674
Comments
Thanks for noticing. Have to check if replacing |
my only concern was backwards compat. afaik the controller only updates the STS without affecting the existing pods, so it'd be safe. |
Is it confirmed this is seamless upgrade - operator will update the statefulset leaving the pods intact? |
I am having trouble getting the Postgres operator to run on k8s v 1.16.0 or 1.16.1 although it runs fine for me on 1.15.3. Has anyone had any success run it on v1.16.x ? |
@Keithsc I asked on the Slack channel and got the answer that the following docker image should already contain the fix and work - it did for me: Patching the deployment yaml file with this image: |
I am having trouble getting the Postgres operator to run on k8s v 1.15.0(my kubernetes cluster) or 1.16.2 (my Minikube).
After I deployment PostgreSQL
|
I did not find any migration guide. Upgrading the Operator is working fine. But the existing Statefulsets are NOT changed (recreated) .... whats the desired migration path? Ok ... after a lot of confusion were we saw even newly created ones had app/v1beta2 ... we looked again. Stupidly enough only the KUbernetes dashboard printed v1beta2 even though it was app/v1 ... did not check on kubectl :( and as we'Re migrating on Kubernetes 1.15.3 of course it was still the old K8 dashboard. |
The current
generateStatefulSet()
uses theapps/v1beta1
api which has been deprecated in kubernetes 1.16.The controller is thus unable to instantiate the cluster.
The text was updated successfully, but these errors were encountered: