You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I ran an update on a cassandra instance to apply PROMETHEUS_EXPORTER_ENABLED=false to a default installation.
It did not remove the prometheus-exporter from the statefulset.
$ kubectl kudo install --instance cassandra-off cassandra
$ kubectl kudo update -p PROMETHEUS_EXPORTER_ENABLED=false --instance cassandra-off
Instance cassandra-off was updated.
$ kubectl describe statefulset cassandra-off-node
[...]
Pod Template:
[...]
Containers:
cassandra:
Image: mesosphere/cassandra:3.11.5-0.1.2-SNAPSHOT
[...]
Environment:
[...]
PROMETHEUS_EXPORTER_ENABLED: false
[...]
prometheus-exporter:
Image: mesosphere/cassandra-prometheus-exporter:2.2.1-0.1.2-SNAPSHOT
[...]
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal SuccessfulDelete 5m56s (x2 over 18h) statefulset-controller delete Pod cassandra-off-node-2 in StatefulSet cassandra-off-node successful
Normal SuccessfulCreate 5m39s (x3 over 18h) statefulset-controller create Pod cassandra-off-node-2 in StatefulSet cassandra-off-node successful
Normal SuccessfulDelete 4m9s (x2 over 18h) statefulset-controller delete Pod cassandra-off-node-1 in StatefulSet cassandra-off-node successful
Normal SuccessfulCreate 3m59s (x3 over 18h) statefulset-controller create Pod cassandra-off-node-1 in StatefulSet cassandra-off-node successful
Normal SuccessfulDelete 3m33s (x2 over 18h) statefulset-controller delete Pod cassandra-off-node-0 in StatefulSet cassandra-off-node successful
Normal SuccessfulCreate 3m19s (x3 over 18h) statefulset-controller create Pod cassandra-off-node-0 in StatefulSet cassandra-off-node successful
You can see that the value for the parameter was propagated correctly, and the statefulset was updated.
What you expected to happen:
It should have removed a container from the stateful set.
How to reproduce it (as minimally and precisely as possible):
See the commands in first section.
Anything else we need to know?:
The prometheus-exporter container definition is conditional on PROMETHEUS_EXPORTER_ENABLED being true, but it is a part of a largr resource (statefulset) which is being applied unconditionally. This makes this issue different from #1147.
I also confirmed that leaving out the prometheus-exporter container works correctly when PROMETHEUS_EXPORTER_ENABLED=falseat the moment of initial installation. Therefore I'm reasonably confident that this must be the patch implementation which causes removal of fields to be ignored.
Unassigning for now, since I will be unavailable next week.
If anyone decides to tackle this in my absence, they may find the above draft PR with a minimal (if ugly) repro useful.
If not, I'll return to this in February.
What happened:
I ran an update on a cassandra instance to apply
PROMETHEUS_EXPORTER_ENABLED=false
to a default installation.It did not remove the
prometheus-exporter
from the statefulset.You can see that the value for the parameter was propagated correctly, and the statefulset was updated.
What you expected to happen:
It should have removed a container from the stateful set.
How to reproduce it (as minimally and precisely as possible):
See the commands in first section.
Anything else we need to know?:
The
prometheus-exporter
container definition is conditional onPROMETHEUS_EXPORTER_ENABLED
beingtrue
, but it is a part of a largr resource (statefulset) which is being applied unconditionally. This makes this issue different from #1147.I also confirmed that leaving out the
prometheus-exporter
container works correctly whenPROMETHEUS_EXPORTER_ENABLED=false
at the moment of initial installation. Therefore I'm reasonably confident that this must be the patch implementation which causes removal of fields to be ignored.cc @mpereira
Environment:
kubectl version
):kubectl kudo version
):cassandra
master
(after0.1.2
)PRETTY_NAME="Debian GNU/Linux 10 (buster)"
uname -a
):Linux beczulka 5.3.0-0.bpo.2-amd64 #1 SMP Debian 5.3.9-2~bpo10+1 (2019-11-13) x86_64 GNU/Linux
The text was updated successfully, but these errors were encountered: