calico: avoid POD restart during initial deploy (#6886)
calico PODs are first started and then in a handler killed and restarted for no reason, nothing has changed. By using the existing variable 'calico_cni_config' (only defined when calico has already started) the restart can be skipped.
This commit is contained in:
parent
a27eebb225
commit
70bbb3e280
1 changed files with 1 additions and 0 deletions
|
@ -1,6 +1,7 @@
|
||||||
---
|
---
|
||||||
- name: reset_calico_cni
|
- name: reset_calico_cni
|
||||||
command: /bin/true
|
command: /bin/true
|
||||||
|
when: calico_cni_config is defined
|
||||||
notify:
|
notify:
|
||||||
- delete 10-calico.conflist
|
- delete 10-calico.conflist
|
||||||
- docker | delete calico-node containers
|
- docker | delete calico-node containers
|
||||||
|
|
Loading…
Reference in a new issue