The operator doesn't handle any updates to the NatsStreamingCluster spec other than the size setting. So if you update the server version, that won't get passed down to the managed pods. Same with annotations.
The operator does seem to pass down these properties when creating new pods, but if the pods are already running, updates don't take effect. This is a serious lack since it prevents you from managing the streaming server version being run, but it is also important if you are providing the configuration file via a configmap like below, where you want to make sure that the pods are restarted if there are configmap changes upon deploy as recommended here:
In the case of the version, not even deleting the pods will get them restarted with the updated streaming server version. This works however with the nats operator.
The operator doesn't handle any updates to the
NatsStreamingCluster
spec other than the size setting. So if you update the server version, that won't get passed down to the managed pods. Same with annotations.The operator does seem to pass down these properties when creating new pods, but if the pods are already running, updates don't take effect. This is a serious lack since it prevents you from managing the streaming server version being run, but it is also important if you are providing the configuration file via a configmap like below, where you want to make sure that the pods are restarted if there are configmap changes upon deploy as recommended here:
In the case of the version, not even deleting the pods will get them restarted with the updated streaming server version. This works however with the nats operator.