Difference between revisions of "Error: waiting for EKS Add-On"
Jump to navigation
Jump to search
(One intermediate revision by the same user not shown) | |||
Line 16: | Line 16: | ||
│ | │ | ||
│ with module.downstream-clusters-EKS.module.eks.aws_eks_addon.this["kube-proxy"], | │ with module.downstream-clusters-EKS.module.eks.aws_eks_addon.this["kube-proxy"], | ||
− | │ on .terraform/modules/xxx/main.tf line 390, in resource "aws_eks_addon" "this": | + | │ on .terraform/modules/xxx/main.tf line 390, in resource "[[aws_eks_addon]]" "this": |
│ 390: resource "aws_eks_addon" "this" { | │ 390: resource "aws_eks_addon" "this" { | ||
Line 47: | Line 47: | ||
* [[Gatekeeper (Kubernetes)]] | * [[Gatekeeper (Kubernetes)]] | ||
* <code>[[service "gatekeeper-webhook-service" not found]]</code> | * <code>[[service "gatekeeper-webhook-service" not found]]</code> | ||
+ | * <code>[[kubectl get pods -n kube-system]]</code> | ||
== See also == | == See also == |
Latest revision as of 12:16, 22 February 2024
Contents
no endpoints available for service[edit]
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" {
Solution: relaunch terraform apply or remove them manually
Service "XXXX" not found[edit]
Error: waiting for EKS Add-On .../... .../... service "gatekeeper-webhook-service" not found
timeout while waiting for state to become[edit]
Error: waiting for EKS Add-On (xxx:kube-proxy) update (1234): timeout while waiting for state to become 'Successful' (last state: 'InProgress', timeout: 20m0s) │ │ with module.downstream-clusters-EKS.module.eks.aws_eks_addon.this["kube-proxy"], │ on .terraform/modules/xxx/main.tf line 390, in resource "aws_eks_addon" "this": │ 390: resource "aws_eks_addon" "this" {
Error: waiting for EKS Add-On (xxxx:coredns) update (1234): timeout while waiting for state to become 'Successful' (last state: 'InProgress', timeout: 20m0s) │ │ with module.downstream-clusters-EKS.module.eks.aws_eks_addon.this["coredns"], │ on .terraform/modules/xxx/main.tf line 390, in resource "aws_eks_addon" "this": │ 390: resource "aws_eks_addon" "this" {
Error: waiting for EKS Add-On (xxx:vpc-cni) update (122345): timeout while waiting for state to become 'Successful' (last state: 'InProgress', timeout: 20m0s) │ │ with module.downstream-clusters-EKS.module.eks.aws_eks_addon.before_compute["vpc-cni"], │ on .terraform/modules/xxxx/main.tf line 418, in resource "aws_eks_addon" "before_compute": │ 418: resource "aws_eks_addon" "before_compute" {
Error: waiting for EKS Add-On (xxx:aws-efs-csi-driver) update (123456): timeout while waiting for state to become 'Successful' (last state: 'InProgress', timeout: 20m0s). Consider setting attribute "" to "OVERWRITE" │ │ with module.downstream-clusters-EKS.module.efs_addon[0].aws_eks_addon.efs_addon, │ on .terraform/modules/xxx/modules/efs-addon/main.tf line 72, in resource "aws_eks_addon" "efs_addon": │ 72: resource "aws_eks_addon" "efs_addon" {
Related[edit]
helm status gatekeeper -n gatekeeper-system
- Gatekeeper (Kubernetes)
service "gatekeeper-webhook-service" not found
kubectl get pods -n kube-system
See also[edit]
- Terraform apply examples with errors
- CoreDNS,
kube-dns
, Know how to configure and use CoreDNS,Corefile
- AWS EKS Addons: best practices,
vpc-cni, kube-proxy, coredns, aws-ebs-csi-driver, aws-efs-csi-driver, aws-guardduty-agent, amazon-cloudwatch-observability, aws eks describe-addon-versions, aws eks create-addon, aws eks list-addons
Advertising: