Skip to content

Updating the cluster-operator from 1.2.0 to 1.3.0 did not result in a rolling STS update, as mentioned in the release notes #2699

Answered by mkuratczyk
gerhard asked this question in Other
Discussion options

You must be logged in to vote

If I'm not mistaken, only TLS-enabled clusters will be restarted (since we mount TLS secrets differently in 1.3.0). I don't think there is any simple way to check that on the user side - we need to be more explicit in the release note based on our understanding of what we change (eg. in this case we know we change the way TLS secrets are defined in the StatefulSet and therefore we know this will only affect TLS-enabled clusters).

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@gerhard
Comment options

Answer selected by michaelklishin
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants