Use calico/cni with fix for node name issue

kubernetes · Sep 2, 2020 · 7a24b82 · 7a24b82
1 parent 1006f90
commit 7a24b82
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 4 deletions.
diff --git a/upup/models/bindata.go b/upup/models/bindata.go
diff --git a/upup/models/cloudup/resources/addons/networking.projectcalico.org/k8s-1.16.yaml.template b/upup/models/cloudup/resources/addons/networking.projectcalico.org/k8s-1.16.yaml.template
@@ -3709,7 +3709,7 @@ spec:
         # It can be deleted if this is a fresh installation, or if you have already
         # upgraded to use calico-ipam.
         - name: upgrade-ipam
-          image: calico/cni:v3.16.0
+          image: calico/cni:v3.16.0-2-gf6793aa
           command: ["/opt/cni/bin/calico-ipam", "-upgrade"]
           envFrom:
           - configMapRef:
@@ -3736,7 +3736,7 @@ spec:
         # This container installs the CNI binaries
         # and CNI network config file on each node.
         - name: install-cni
-          image: calico/cni:v3.16.0
+          image: calico/cni:v3.16.0-2-gf6793aa
           command: ["/opt/cni/bin/install"]
           envFrom:
           - configMapRef: