Closed gaba-mlindner closed 3 years ago
Thanks for the report! I have opened a PR with the fix: https://github.com/gruntwork-io/kubergrunt/pull/130
Looking at the related PR and tests now!
This is now handled in https://github.com/gruntwork-io/kubergrunt/releases/tag/v0.7.2
Just FYI, I upgraded another cluster with the v0.7.2 version last night and it worked like a charm without manual intervention. Thanks for the quick fix!
Thanks for closing the loop!
I just upgraded my lab EKS cluster (managed by Gruntwork's
terraform-aws-eks
modules) from 1.19 to 1.20 and ran into some issues with kubergrunt's CoreDNS update.After the module's provisioner had executed
eks sync-core-components ..
, DNS resolution inside the cluster stopped working and the new CoreDNS pods starting logging errors like:Quick googling led me to AWS' docs (see step 5): https://docs.aws.amazon.com/eks/latest/userguide/managing-coredns.html#updating-coredns-add-on
It turns out that the CoreDNS 1.8.3 update requires additional permissions.
Manually patching the
system:coredns
clusterrole resolved my issues, but I think it would make sense to havekubergrunt
handle this kind of thing automatically (since it's already patching the image version and configmap anyways).versions: terraform
v1.0.0
terragruntv0.29.2
kubergruntv0.7.1
terraform-aws-eksv0.41.0