From 159a62b4ff4f25b79e83dd3080b02fc3c216a2f0 Mon Sep 17 00:00:00 2001 From: EliseCastle23 Date: Wed, 31 Jan 2024 14:56:16 -0700 Subject: [PATCH] adding step to update coredns --- gen3/bin/migrate-to-vpc-cni.sh | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/gen3/bin/migrate-to-vpc-cni.sh b/gen3/bin/migrate-to-vpc-cni.sh index 510d9ebef..1737f655d 100644 --- a/gen3/bin/migrate-to-vpc-cni.sh +++ b/gen3/bin/migrate-to-vpc-cni.sh @@ -48,10 +48,14 @@ else gen3 kube-setup-karpenter deploy --force || { gen3_log_err "kube-setup-karpenter failed"; exit 1; } fi -# Cordon all the nodes before running gen3 roll all" +# Cordon all the nodes before running gen3 roll all gen3_log_info "Cordoning all nodes" kubectl get nodes --no-headers -o custom-columns=":metadata.name" | grep -v '^fargate' | xargs -I{} kubectl cordon {} +# Backup and update CoreDNS +kubectl get deployment coredns -n kube-system -o yaml > aws-k8s-coredns-old.yaml +kubectl set image deployment.apps/coredns -n kube-system coredns=602401143452.dkr.ecr.us-east-1.amazonaws.com/eks/coredns:v1.9.3-eksbuild.10 + # Run a "gen3 roll all" so all nodes use the new mounted BPF File System gen3_log_info "Cycling all the nodes by running gen3 roll all" gen3 roll all --fast || exit 1