c12s-kubespray/roles/network_plugin/calico/templates/cni-calico.conf.j2

{
  "name": "calico-k8s-network",
{% if not legacy_calicoctl %}
  "hostname": "{{ ansible_hostname }}",
{% endif %}
  "type": "calico",
  "etcd_endpoints": "{{ etcd_access_endpoint }}",
  "etcd_cert_file": "{{ etcd_cert_dir }}/node-{{ inventory_hostname }}.pem",
  "etcd_key_file": "{{ etcd_cert_dir }}/node-{{ inventory_hostname }}-key.pem",
  "etcd_ca_cert_file": "{{ etcd_cert_dir }}/ca.pem",
  "log_level": "info",
  "ipam": {
    "type": "calico-ipam"
  },
{% if enable_network_policy %}
  "policy": {
    "type": "k8s"
  },
{% endif %}
{% if calico_mtu is defined and calico_mtu is number %}
  "mtu": {{ calico_mtu }},
{% endif %}
  "kubernetes": {
    "kubeconfig": "{{ kube_config_dir }}/node-kubeconfig.yaml"
  }
}
split network plugins into distinct roles 2016-01-30 15:04:47 +00:00			`{`
			`"name": "calico-k8s-network",`
Fix possible problems with legacy calicoctl When running legacy calicoctl we do not specify calico hostname in calico-node container thus we should not specify it in CNI config. Also move 'legacy_calicoctl' set_fact task to the top. 2016-12-07 11:13:12 +00:00			`{% if not legacy_calicoctl %}`
Switch to ansible_hostname in calico For consistancy with kubernetes services we should use the same hostname for nodes, which is 'ansible_hostname'. Also fixing missed 'kube-node' in templates, Calico is installed on 'k8s-cluster' roles, not only 'kube-node'. 2017-01-25 10:47:42 +00:00			`"hostname": "{{ ansible_hostname }}",`
Fix possible problems with legacy calicoctl When running legacy calicoctl we do not specify calico hostname in calico-node container thus we should not specify it in CNI config. Also move 'legacy_calicoctl' set_fact task to the top. 2016-12-07 11:13:12 +00:00			`{% endif %}`
split network plugins into distinct roles 2016-01-30 15:04:47 +00:00			`"type": "calico",`
Remove etcd-proxy from all nodes and use etcd multiaccess 2016-11-09 10:31:12 +00:00			`"etcd_endpoints": "{{ etcd_access_endpoint }}",`
Individual etcd ssl certs Includes hooks for triggering calico, kubelet, and kube-apiserver restarts if etcd certs changed. 2016-12-13 09:03:35 +00:00			`"etcd_cert_file": "{{ etcd_cert_dir }}/node-{{ inventory_hostname }}.pem",`
			`"etcd_key_file": "{{ etcd_cert_dir }}/node-{{ inventory_hostname }}-key.pem",`
Add etcd TLS support 2016-11-09 10:44:41 +00:00			`"etcd_ca_cert_file": "{{ etcd_cert_dir }}/ca.pem",`
split network plugins into distinct roles 2016-01-30 15:04:47 +00:00			`"log_level": "info",`
			`"ipam": {`
			`"type": "calico-ipam"`
Changes in Kubernetes and Calico-CNI plugin config files required for usage of Calico CNI plugin version 1.4.2 2016-10-06 10:06:19 +00:00			`},`
Move calico-policy-controller into separate role By default Calico CNI does not create any network access policies or profiles if 'policy' is enabled in CNI config. And without any policies/profiles network access to/from PODs is blocked. K8s related policies are created by calico-policy-controller in such case. So we need to start it as soon as possible, before any real workloads. This patch also fixes kube-api port in calico-policy-controller yaml template. Closes #1132 2017-03-13 15:04:31 +00:00			`{% if enable_network_policy %}`
Add possibility to enable network policy via Calico network controller The requirements for network policy feature are described here [1]. In order to enable it, appropriate configuration must be provided to the CNI plug in and Calico policy controller must be set up. Beside that corresponding extensions needed to be enabled in k8s API. Now to turn on the feature user can define `enable_network_policy` customization variable for Ansible. [1] http://kubernetes.io/docs/user-guide/networkpolicies/ 2016-10-10 14:09:50 +00:00			`"policy": {`
			`"type": "k8s"`
			`},`
Move CNI config and add MTU support for calico-cni - Move CNI configuration creation for Calico to appropriate network_plugin role from kubernetes/node. - Add support for MTU configuration in Calico. 2016-11-14 07:48:28 +00:00			`{% endif %}`
			`{% if calico_mtu is defined and calico_mtu is number %}`
			`"mtu": {{ calico_mtu }},`
Add possibility to enable network policy via Calico network controller The requirements for network policy feature are described here [1]. In order to enable it, appropriate configuration must be provided to the CNI plug in and Calico policy controller must be set up. Beside that corresponding extensions needed to be enabled in k8s API. Now to turn on the feature user can define `enable_network_policy` customization variable for Ansible. [1] http://kubernetes.io/docs/user-guide/networkpolicies/ 2016-10-10 14:09:50 +00:00			`{% endif %}`
Changes in Kubernetes and Calico-CNI plugin config files required for usage of Calico CNI plugin version 1.4.2 2016-10-06 10:06:19 +00:00			`"kubernetes": {`
			`"kubeconfig": "{{ kube_config_dir }}/node-kubeconfig.yaml"`
split network plugins into distinct roles 2016-01-30 15:04:47 +00:00			`}`
			`}`