githubusercontent.com/cilium/cilium/v1.5/exam kubectl create -f https://raw.githubusercontent.com/cilium/cilium/v1.5/exam kubectl create -f https://raw.githubusercontent.com/cilium/cilium/v1.5/exam kubectl create -f githubusercontent.com/cilium/cilium/v1.5/exam kubectl create -f https://raw.githubusercontent.com/cilium/cilium/v1.5/exam kubectl create -f https://raw.githubusercontent.com/cilium/cilium/v1.5/exam Next steps Now /var/snap/microk8s/current/args/cni-network/cni.conf curl https://raw.githubusercontent.com/cilium/cilium/v1.5/plugins/cilium-c systemctl restart snap.microk8s.daemon-containerd.service systemctl restart snap.microk8s

From Managed Kubernetes to App Platform: 1.5 Years of Cilium Usage at DigitalOcean Timo Reimann, DigitalOcean October 28, 2020 digitalocean.com History / Context ● DigitalOcean Kubernetes Service

x 1.3.y Required Minimal to None Clients must reconnect[1] >=1.2.5 1.5.y Required Minimal to None Clients must reconnect[1] 1.5.x 1.6.y Required Minimal to None Clients must reconnect[1] Annotations: the DaemonSet. Adding the options to the ConfigMap will not impact the ability to rollback. Cilium 1.5.y and earlier are compatible with the options although their values will be ignored as both options described in Upgrading Minor Versions. Users running older versions should first upgrade to the latest v1.5.x point release to minimize disruption of service connections during upgrade. Changes that may require

x 1.3.y Required Minimal to None Clients must reconnect[1] >=1.2.5 1.5.y Required Minimal to None Clients must reconnect[1] 1.5.x 1.6.y Required Minimal to None Clients must reconnect[1] 1.6.x 1 the DaemonSet. Adding the options to the ConfigMap will not impact the ability to rollback. Cilium 1.5.y and earlier are compatible with the options although their values will be ignored as both options as described in Upgrading Cilium. Users running older versions should first upgrade to the latest v1.5.x point release to minimize disruption of service connections during upgrade. Changes that may require

x 1.3.y Required Minimal to None Clients must reconnect[1] >=1.2.5 1.5.y Required Minimal to None Clients must reconnect[1] 1.5.x 1.6.y Required Minimal to None Clients must reconnect[1] 1.6.x 1 calls. See API Rate Limiting for more information. Upgrading from >=1.7.0 to 1.8.y Since Cilium 1.5, the TCP connection tracking table size parameter bpf-ct- global-tcp-max in the daemon was set to the the DaemonSet. Adding the options to the ConfigMap will not impact the ability to rollback. Cilium 1.5.y and earlier are compatible with the options although their values will be ignored as both options

information, see section Container HostPort Support. Upgrading from >=1.7.0 to 1.8.y Since Cilium 1.5, the TCP connection tracking table size parameter bpf-ct-global- tcp-max in the daemon was set to the

information, see section Container HostPort Support. Upgrading from >=1.7.0 to 1.8.y Since Cilium 1.5, the TCP connection tracking table size parameter bpf-ct-global- tcp-max in the daemon was set to the