Conversation
|
Please set the appropriate release note label. |
|
test-focus K8sDemos |
|
🤯 I thought Daemonset guaranteed this. |
|
@joestringer it actually does, but if you delete the DaemonSet and recreate it (like we do in CI), two Cilium pods can run on the same node in parallel. Edit: The deletion/recreation causes K8s to treat these pods technically as from two different DaemonSets (which is true I guess). |
joestringer
left a comment
There was a problem hiding this comment.
Not particularly familiar with the syntax here but it LGTM.
This change makes sure that two Cilium pods cannot be running on the same node in parallel. Signed-off-by: Maciej Kwiek <maciej@isovalent.com>
36fd867 to
92c545d
Compare
|
Moved the affinity to |
|
test-focus K8sDemos |
brb
left a comment
There was a problem hiding this comment.
I assume this won't interfere with https://github.com/cilium/cilium/blob/master/test/helpers/kubectl.go#L2117.
|
@brb I don't think so, this is AntiAffinity, the code you pointed to adds nodeAffinity , but good catch, I forgot about this bit. Will run net-next suite just to make sure that nothing breaks |
|
test-net-next |
|
retest-net-next |
|
test-missed-k8s |
|
hit #11867 |
|
Note to backporters: @nebril will take over backporting this to 1.7 as it has some conflicts with how the CI is setup. |
|
Doing some clean-up, I notice the |
|
Oh I missed it, thank you. |
|
#12077 was eventually closed by Joe (#12077 (comment)), I'm removing the label. |
This change makes sure that two Cilium pods cannot be running on the
same node in parallel. Which can happen in case an daemonset is deleted and immediately created.
Fixes: #11828