We noticed that changes in "command" section does not trigger update of statefulset. For example, change of first line to sysctl -w vm.dirty_background_bytes=1600001 produces following log in postgres-operator (and doesn't trigger "syncing statefulsets"):
To get your changes applied to sts you have to patch any other parameter of manifest, for example if I change initContainer's name to sysctl-container-revision-2 then i can see in operator's log that sts is being updated:
The operator makes a few diffs on conatiner level including initContainers, but commands are not included. I think, that's something you'd rather bake into your initContainer image itself.
Please, answer some short questions which should help us to understand your problem / question better?
Hi,
We are using initContainer to tune some kernel settings for nodes running postgres. postgresql manifest looks like this:
We noticed that changes in "command" section does not trigger update of statefulset. For example, change of first line to
sysctl -w vm.dirty_background_bytes=1600001
produces following log in postgres-operator (and doesn't trigger "syncing statefulsets"):To get your changes applied to sts you have to patch any other parameter of manifest, for example if I change initContainer's name to
sysctl-container-revision-2
then i can see in operator's log that sts is being updated: