kube-addon-update.sh

cluster/saltbase/salt/kube-addons/init.sls

@@ -1,3 +1,16 @@
+addon-dir-delete:
+  file.absent:
+    - name: /etc/kubernetes/addons
+
+addon-dir-create:
+  file.directory:
+    - name: /etc/kubernetes/addons
+    - user: root
+    - group: root
+    - mode: 0755
+    - require:
+        - file: addon-dir-delete
+
 {% if pillar.get('enable_cluster_monitoring', '').lower() == 'influxdb' %}
 /etc/kubernetes/addons/cluster-monitoring/influxdb:
   file.recurse:
@@ -58,6 +71,13 @@
     - group: root
     - mode: 755
 
+/etc/kubernetes/kube-addon-update.sh:
+  file.managed:
+    - source: salt://kube-addons/kube-addon-update.sh
+    - user: root
+    - group: root
+    - mode: 755
+
 {% if grains['os_family'] == 'RedHat' %}
 
 /usr/lib/systemd/system/kube-addons.service:
@@ -77,6 +97,16 @@
 
 {% endif %}
 
+# Stop kube-addons service each time salt is executed, just in case
+# there was a modification of addons.
+# Actually, this should be handled by watching file changes, but
+# somehow it doesn't work.
+service-kube-addon-stop:
+  service.dead:
+    - name: kube-addons
+
 kube-addons:
   service.running:
     - enable: True
+    - require:
+        - service: service-kube-addon-stop