Difference between revisions of "Error: waiting for EKS Add-On"
Jump to navigation
Jump to search
| Line 4: | Line 4: | ||
webhook-service" | webhook-service" | ||
│ | │ | ||
| − | │ with module. | + | │ with module.clusters-EKS.module.eks.aws_eks_addon.this["coredns"], |
| − | │ on .terraform/modules/ | + | │ on .terraform/modules/clusters-EKS.eks/main.tf line 390, in resource "[[aws_eks_addon]]" "this": |
│ 390: resource "aws_eks_addon" "this" { | │ 390: resource "aws_eks_addon" "this" { | ||
Revision as of 14:24, 18 January 2024
Error: waiting for EKS Add-On (yourcluster:coredns) create: unexpected state 'CREATE_FAILED', wanted target 'ACTIVE'. last error: : AdmissionRequestDenied: Internal error occurred: failed calling webhook "check-ignore-label.gatekeeper.sh": failed to call webhook: Post "https://gatekeeper-webhook-service.gatekeeper-system.svc:443/v1/admitlabel?timeout=3s": no endpoints available for service "gatekeeper- webhook-service" │ │ with module.clusters-EKS.module.eks.aws_eks_addon.this["coredns"], │ on .terraform/modules/clusters-EKS.eks/main.tf line 390, in resource "aws_eks_addon" "this": │ 390: resource "aws_eks_addon" "this" {
Related
See also
- EKS,
eksctl, EKS add-ons, Amazon EKS cluster role, Terraform EKS, Kubernetes Autoscaler, Karpenter, Terraform module: EKS, Terraform resource: aws eks node group, Terraform data source: aws_eks_cluster, AWS Controllers for Kubernetes, AWS Load Balancer Controller, Amazon EKS Anywhere, Kustomize,aws-iam-authenticator, ACK, tEKS, Amazon EKS authorization, Amazon EKS authentication, Nodegroup, EKS storage,aws-ebs-csi-driver, aws-efs-csi-driver, aws-load-balancer-controller, amazon-vpc-cni-k8s, EKS security, EKS Best Practices Guides,hardeneks, EKS versions,fargate-scheduler,eks-connector, Resilience in Amazon EKS, EKS control plane logging, Security groups for Pods in EKS
Advertising:
