Repository navigation
keycloak-operator: Rolling updates not working as expected. #40354
Replies: 2 comments
|
Please create an issue instead. This is a bug with the update logic handling of initContainers. |
0 replies
|
Closing the discussion, moved to issue #40360 |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I am seeing the following issues with the keycloak-operator:
When
spec.update.strategy=Autopods are not refreshed, and the operator fails with the following:Is this a permissions issue, and to what?
When
spec.update={ strategy=Explicit; revision=26.2.5 }and pods are refreshed, but are replaced, rolling deployment is never executed. It is expected always to use rolling when Explicit is set.Details
26.2.526.2.526.2.5Has anyone else had similar issues with the deployments?
Any insights would be greatly appreciated.
All reactions