kube-arangodb
kube-arangodb copied to clipboard
Do not change args of un-upgraded members during an upgrade
In an upgrade from 3.4 to 3.5, we're changing the args for servers groups and the image version in 1 change.
If during this update a non-upgrade pod is restarted, it will get the new args, which is not intended. (e.g. breaks because a new 3.5 feature is used)