kubernetes
/
kops
mirror of https://github.com/kubernetes/kops.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Improve cilium feature documentation

This commit is contained in:
Ole Markus With 2020-06-26 14:11:30 +02:00
parent 51235b2edc
commit fea1aa0ae8
1 changed files with 16 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
docs/networking/cilium.md
View File

@ -27,7 +27,9 @@ kops create cluster \
### Using etcd for agent state sync ### Using etcd for agent state sync
By default, Cilium will use CRDs for synchronizing agent state. This can cause performance problems on larger clusters. As of kops 1.18, kops can manage an etcd cluster using etcd-manager dedicated for cilium agent state sync. The [Cilium docs](https://docs.cilium.io/en/stable/gettingstarted/k8s-install-external-etcd/) contains recommendations for this must be enabled. This feature is in beta state as of kops 1.18.
By default, Cilium will use CRDs for synchronizing agent state. This can cause performance problems on larger clusters. As of kops 1.18, kops can manage an etcd cluster using etcd-manager dedicated for cilium agent state sync. The [Cilium docs](https://docs.cilium.io/en/stable/gettingstarted/k8s-install-external-etcd/) contains recommendations for when this must be enabled.
Add the following to `spec.etcdClusters`: Add the following to `spec.etcdClusters`:
Make sure `instanceGroup` match the other etcd clusters. Make sure `instanceGroup` match the other etcd clusters.
@ -43,6 +45,15 @@ Make sure `instanceGroup` match the other etcd clusters.
name: cilium name: cilium
``` ```
If this is an existing cluster, it is important that you roll the entire cluster so that all the nodes can connect to the new etcd cluster.
```sh
kops update cluster
kops update cluster --yes
kops rolling-update cluster --force --yes
```
Then enable etcd as kvstore: Then enable etcd as kvstore:
```yaml ```yaml
@ -60,6 +71,8 @@ Read more about this in the [Cilium docs](https://docs.cilium.io/en/stable/getti
Be aware that you need to use an AMI with at least Linux 4.19.57 for this feature to work. Be aware that you need to use an AMI with at least Linux 4.19.57 for this feature to work.
Also be aware that while enabling this on an existing cluster is safe, disabling this is disruptive and requires you to run `kops rolling-upgrade cluster --cloudonly`.
```yaml ```yaml
kubeProxy: kubeProxy:
enabled: false enabled: false
@ -70,6 +83,8 @@ Be aware that you need to use an AMI with at least Linux 4.19.57 for this featur
### Enabling Cilium ENI IPAM ### Enabling Cilium ENI IPAM
This feature is in beta state as of kops 1.18.
As of Kops 1.18, you can have Cilium provision AWS managed adresses and attach them directly to Pods much like Lyft VPC and AWS VPC. See [the Cilium docs for more information](https://docs.cilium.io/en/v1.6/concepts/ipam/eni/) As of Kops 1.18, you can have Cilium provision AWS managed adresses and attach them directly to Pods much like Lyft VPC and AWS VPC. See [the Cilium docs for more information](https://docs.cilium.io/en/v1.6/concepts/ipam/eni/)
When using ENI IPAM you need to disable masquerading in Cilium as well. When using ENI IPAM you need to disable masquerading in Cilium as well.