the host networking namespace directly. Upgrade Guide This upgrade guide is intended for Cilium 1.3 or later running on Kubernetes. It is assuming that Cilium has been deployed using standard procedures automa�cally the case. If you are looking for instruc�ons for upgrading from a version of Cilium prior to 1.3, then please consult the documenta�on from that release. Running a pre-flight DaemonSet When rolling Clients must reconnect[1] Current version Target version DaemonSet upgrade L3 impact L7 impact 1.2.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.1.x 1.2.y Required Temporary disruption[2] Clients must reconnect[1] 1.2.x 1.3.y Required Minimal to None Clients must reconnect[1] >=1.2.5 1.5.y Required Minimal to None Clients Cilium guide. Upgrading DNS Polling deployments to DNS Proxy (preferred) In cilium versions 1.2 and 1.3 DNS Polling was automatically used to obtain IP information for use in toFQDNs.matchName rules in DNS not impacted and will retain DNS data when restarted or upgraded. Affected versions Cilium 1.2 and 1.3 when using DNS Polling with toFQDNs.matchName policy rules and upgrading to cilium 1.4.0 or later.

Clients must reconnect[1] Current version Target version Full YAML update L3 impact L7 impact 1.2.x 1.3.y Required Minimal to None Clients must reconnect[1] >=1.2.5 1.5.y Required Minimal to None Clients

L3 impact L7 impact 1.1.x 1.2.y Required Temporary disruption[2] Clients must reconnect[1] 1.2.x 1.3.y Required Minimal to None Clients must reconnect[1] >=1.2.5 1.5.y Required Minimal to None Clients