Upgrade Guide Running pre-flight check (Required) Upgrading Cilium Version Specific Notes Advanced Configuration Core Agent Network Policy Policy Enforcement Modes Rule Basics Layer 3 Examples Layer 4 deploy the “connectivity-check” to test connectivity between pods. It is recommended to create a separate namespace for this. kubectl create ns cilium-test Deploy the check with: kubectl apply -n cilium-test p75 1/1 Running 0 68s Note If you deploy the connectivity check to a single node cluster, pods that check multi- node functionalities will remain in the Pending state. This is expected

Upgrade Guide Running pre-flight check (Required) Upgrading Cilium Version Specific Notes Advanced Configuration Core Agent Network Policy Policy Enforcement Modes Rule Basics Layer 3 Examples Layer 4 com/cilium/cilium- cli/releases/latest/download/cilium-linux-amd64.tar.gz{,.sha256sum} sha256sum --check cilium-linux-amd64.tar.gz.sha256sum sudo tar xzvfC cilium-linux-amd64.tar.gz /usr/local/bin rm cilium-linux-amd64 detected, will skip some flow validation steps � [k8s-cluster] Creating namespace for connectivity check... (...) ----------------------------------------------------------------------- ----------------

pre-flight check (Required) Upgrading Micro Versions Upgrading Minor Versions Step 3: Rolling Back Version Specific Notes Advanced Configuration Network Policy Policy Enforcement Modes Rule Basics Layer 1/1 Running 0 13m Deploy the connectivity test You can deploy the “connectivity-check” to test connectivity between pods. kubectl apply -f https://raw.githubusercontent.com/cilium/cilium/v1 1/1 Running 0 13m Deploy the connectivity test You can deploy the “connectivity-check” to test connectivity between pods. kubectl apply -f https://raw.githubusercontent.com/cilium/cilium/v1

Upgrade Guide Running pre-flight check (Required) Upgrading Cilium Version Specific Notes Advanced Configuration Core Agent Network Policy Policy Enforcement Modes Rule Basics Layer 3 Examples Layer 4 deploy the “connectivity-check” to test connectivity between pods. It is recommended to create a separate namespace for this. kubectl create ns cilium-test Deploy the check with: kubectl apply -n cilium-test 7 1/1 Running 0 66s Note If you deploy the connectivity check to a single node cluster, pods that check multi- node functionalities will remain in the Pending state. This is expected

Guide Running pre-flight check (Required) Upgrading Cilium Step 3: Rolling Back Version Specific Notes Advanced Configuration Network Policy Policy Enforcement Modes Rule Basics Layer 3 Examples Layer 1/1 Running 0 13m Deploy the connectivity test You can deploy the “connectivity-check” to test connectivity between pods. kubectl apply -f https://raw.githubusercontent.com/cilium/cilium/v1 1/1 Running 0 13m Deploy the connectivity test You can deploy the “connectivity-check” to test connectivity between pods. kubectl apply -f https://raw.githubusercontent.com/cilium/cilium/v1

Upgrade Guide Running pre-flight check (Required) Upgrading Cilium Version Specific Notes Advanced Configuration Core Agent Network Policy Policy Enforcement Modes Rule Basics Layer 3 Examples Layer cli/releases/download/${CILIUM_CLI_VERSION}/cilium- linux-${CLI_ARCH}.tar.gz{,.sha256sum} sha256sum --check cilium-linux-${CLI_ARCH}.tar.gz.sha256sum sudo tar xzvfC cilium-linux-${CLI_ARCH}.tar.gz /usr/local/bin detected, will skip some flow validation steps � [k8s-cluster] Creating namespace for connectivity check... (...) ----------------------------------------------------------------------- ----------------

Rolling Back Version Specific Notes Advanced Configura�on Network Policy Policy Enforcement Modes Rule Basics Layer 3 Examples Layer 4 Examples Layer 7 Examples Kubernetes Endpoint Lifecycle Troubleshoo�ng correctly, a DNS reverse lookup on a pod IP must map back to pod name. If you are using CoreDNS, check the CoreDNS ConfigMap and validate that in-addr.arpa and ip6.arpa are listed as wildcards for the create 2 separate CloudFormation stacks for cluster itself and th [ℹ] if you encounter any issues, check CloudFormation console or try 'eksc [ℹ] creating cluster stack "eksctl-ridiculous-gopher-1548608219-cluster"