It does't patch the coreDNS after create fargate profile
zhaoyi0113 opened this issue · 4 comments
Based on https://docs.aws.amazon.com/eks/latest/userguide/fargate-getting-started.html, we need to patch the core dns pod by this command:
kubectl patch deployment coredns \
-n kube-system \
--type json \
-p='[{"op": "remove", "path": "/spec/template/metadata/annotations/eks.amazonaws.com~1compute-type"}]'
it seems this module doesn't patch it.
This will require to couple module with kubernetes provider. I would suggest not to do it, but instead orchestrate it with another module that explicitly just does CoreDns patch
Is there an end-to-end example of booting a Fargate cluster with a "normal" setup?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically closed because it has not had recent activity since being marked as stale.