kubernetes: Calico / NetworkPolicy broken in GCE provider

https://github.com/kubernetes/kubernetes/pull/31023#issuecomment-246860748 broke the salt-based Calico install in the GCE kube-up deployments, since the GCI image doesn’t use salt and instead relies on cloud-config.

e.g

NETWORK_POLICY_PROVIDER=calico cluster/kube-up.sh

which used to work, doesn’t any more.

This should be fixed when the Calico self-hosted installation PR https://github.com/kubernetes/kubernetes/pull/30598/files hits, which will install Calico using a DaemonSet.

Keeping a list of the things that are going wrong since the switch to GCI:

Node components are no longer installed (Will be fixed by #30598)
calico/node:v0.22.0 failing due to missing ip_set kernel support.
NETWORK_POLICY_PROVIDER=calico no longer sets --network-plugin=cni on kubelet.

About this issue

Original URL
State: closed
Created 8 years ago
Comments: 27 (26 by maintainers)

Commits related to this issue

Merge pull request #38169 from caseydavenport/calico-daemonset Automatic merge from submit-queue Update Calico add-on **What this PR does / why we need it:** Updates Calico to the latest version... — committed to kubernetes/kubernetes by deleted user 7 years ago

Most upvoted comments

@Amey-D might be able to provide more inputs from GCI side. From a release perspective, we might be able to get a build with ip sets in one of the upcoming patch releases for v1.4.0 depending on the GCI changes required. Thanks for the detailed feedback!

vishh on Sep 14, 2016