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
-
Part of rabbitmq/tgir#20 we bumped the cluster-operator from 1.2.0 to 1.3.0 and were expecting to see STS updating, as per the release notes, but this did not happen. We (+@Gsantomaggio) have two questions:
cc @mkuratczyk More contextcluster-operator logs
events
rabbitmq-bugs describe that shows no pod updates
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
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 |
Beta Was this translation helpful? Give feedback.
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).