AWS EKS terraform "pod disruption budget already exists"

Question

Hi,

We use terraform to deploy EKS clusters and self manage the CoreDNS add on. Until very recently we could deploy without failure but now whenever we create and EKS cluster a pod disruption budget is created by AWS, blocking our pod disruption budget deployment. When I look at the pdb created by AWS it is linked to the managed addon which does not exists in our scenario. We believe this to be a bug but are we right to believe so?

Regards,

Tom van Veen

Accepted Answer

AWS EKS introduced managed add-ons, including CoreDNS, to simplify the management and maintenance of certain Kubernetes components. 
These managed add-ons are automatically created and managed by AWS EKS. Quoting from AWS blog   "We added new components like PodDisruptionBudget (PDB), implemented opinionated defaults (e.g., using health plugin for pod health checks) and enhanced the JSON configuration schema to allow customers to customize more parameters of the add-on" "https://aws.amazon.com/it/blogs/containers/recent-changes-to-the-coredns-add-on/#:~:text=Amazon%20Elastic%20Kubernetes%20Service%20(Amazon,ons%20for%20Amazon%20EKS%20clusters."I  strongly suggest you should reachout to AWS Support for assistance and they will  provide insights into the behavior you are observing and offer guidance on potential solutions or workarounds in case of any bugs.

AWS EKS terraform "pod disruption budget already exists"

相关内容