in-addr.arpa and ip6.arpa are listed as wildcards for the kubernetes block like this: kubectl -n kube-system edit cm coredns [...] apiVersion: v1 data: Corefile: | .:53 { errors Installation You can monitor as Cilium and all required components are being installed: kubectl -n kube-system get pods --watch NAME READY STATUS RESTART as well if required and validate that Cilium is managing kube-dns or coredns by running: kubectl -n kube-system get cep You should see kube-dns-xxx or coredns-xxx pods. In order for the en�re system

7b5cdbcbb8-kjl65 ♻ Restarted unmanaged pod kube-system/stackdriver-metadata-agent- cluster-level-6cc964cddf-8n2rt This indicates that your cluster was already running some pods before Cilium was deployed and the instead of VPC CNI, so the aws-node DaemonSet has to be patched to prevent conflict behavior. kubectl -n kube-system patch daemonset aws-node --type='strategic' - p='{"spec":{"template":{"spec":{"nodeSelector":{"io NAME:.metadata.name,HOSTNETWORK:. spec.hostNetwork --no-headers=true | grep '' | awk '{print "-n "$1" "$2}' | xargs -L 1 -r kubectl delete pod pod "event-exporter-v0.2.3-f9c896d75-cbvcz" deleted pod

Installation You can monitor as Cilium and all required components are being installed: kubectl -n kube-system get pods --watch NAME READY STATUS RESTARTS separate namespace for this. kubectl create ns cilium-test Deploy the check with: kubectl apply -n cilium-test -f https://raw.githubusercontent.com/cilium/ci It will deploy a series of deployments which and the readiness and liveness gate indicates success or failure of the test: $ kubectl get pods -n cilium-test NAME READY STATUS RESTARTS AGE

Installation You can monitor as Cilium and all required components are being installed: kubectl -n kube-system get pods --watch NAME READY STATUS RESTARTS NAME:.metadata.name,HOSTNETWORK:. spec.hostNetwork --no-headers=true | grep '' | awk '{print "-n "$1" "$2}' | xargs -L 1 -r kubectl delete pod pod "event-exporter-v0.2.3-f9c896d75-cbvcz" deleted pod x5f" deleted pod "kube-dns-autoscaler-76fcd5f658-22r72" deleted pod "kube-state-metrics-7d9774bbd5-n6m5k" deleted pod "l7-default-backend-6f8697844f-d2rq2" deleted pod "metrics-server-v0.3.1-54699c9cc8-7l5w2"

Installation You can monitor as Cilium and all required components are being installed: kubectl -n kube-system get pods --watch NAME READY STATUS RESTARTS Installation You can monitor as Cilium and all required components are being installed: kubectl -n kube-system get pods --watch NAME READY STATUS RESTARTS Installation You can monitor as Cilium and all required components are being installed: kubectl -n kube-system get pods --watch NAME READY STATUS RESTARTS

Installation You can monitor as Cilium and all required components are being installed: kubectl -n kube-system get pods --watch NAME READY STATUS RESTARTS separate namespace for this. kubectl create ns cilium-test Deploy the check with: kubectl apply -n cilium-test -f https://raw.githubusercontent.com/cilium/ci It will deploy a series of deployments which and the readiness and liveness gate indicates success or failure of the test: $ kubectl get pods -n cilium-test NAME READY STATUS RESTARTS AGE

7b5cdbcbb8-kjl65 ♻ Restarted unmanaged pod kube-system/stackdriver-metadata-agent- cluster-level-6cc964cddf-8n2rt This indicates that your cluster was already running some pods before Cilium was deployed and the instead of VPC CNI, so the aws-node DaemonSet has to be patched to prevent conflict behavior. kubectl -n kube-system patch daemonset aws-node --type='strategic' - p='{"spec":{"template":{"spec":{"nodeSelector":{"io NAME:.metadata.name,HOSTNETWORK:. spec.hostNetwork --no-headers=true | grep '' | awk '{print "-n "$1" "$2}' | xargs -L 1 -r kubectl delete pod pod "event-exporter-v0.2.3-f9c896d75-cbvcz" deleted pod