Closed sagittariuslee closed 2 months ago
Thank you for reporting us your feedback!
The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-5736.
This message was autogenerated
@sagittariuslee I understand that this is not an issue with how the node-affinity charm is working, but rather K8s mechanics when other Pods have set nodeSelectorTerms
.
My understanding in this case is that the work needs to be done in the other Charms that have nodeSelectorTerms
and if they need to be modified.
So I want to close this issue because of the above, but before that do I miss something?
@kimwnasptd Yes, you are right. This has to be done on the other charms that manage the DaemonSet (in this case, it is the Metallb charm).
Bug Description
The
nodeSelector
term injected to DaemonSet pods will be ignored due to the fact thatTo Reproduce
juju deploy metallb --channel 1.28/stable --trust --config namespace=metallb
juju deploy namespace-node-affinity --trust
kubectl label namespaces metallb namespace-node-affinity=enabled
settings.yaml
SETTINGS_YAML=$(cat settings.yaml)
juju config namespace-node-affinity settings_yaml="$SETTINGS_YAML"
kubectl delete pods -n metallb metallb-0
(theoperator
pod formetallb
app.)kubectl get pods -n metallb metallb-0 -o yaml
, we can see in the yaml for the newly created pod:now pick another pod
speaker-ngkg8
which was spawned by the charm pod, before deletion:kubectl delete pods -n metallb speaker-ngkg8
kubectl get pods -n metallb speaker-k59pk -o yaml
, check this newly created pod:We can see the
nodeSelector
term is injected. However, this newly created pod will stay invm-0
due to the fact thatIn this case, the second term is going to be ignored.
Environment
juju version: 2.9.43 kubernetes: v1.24.17
Relevant Log Output
Additional Context
No response