CODEWITHSUNDEEP
kubernetesamazon-eksnginx-ingress
AT07
AT07

Reputation: 53

Getting failed calling webhook "validate.nginx.ingress.kubernetes.io": error when applying ingress resource/rules yaml file in NginxIngress Controller

I'm getting below error whenever I'm trying to apply an ingress resource/rules yaml file:

failed calling webhook "validate.nginx.ingress.kubernetes.io": Post "https://ingress-nginx-controller-admission.ingress-nginx.svc:443/networking/v1/ingresses?timeout=10s": EOF

It seems there are multiple errors for "failed calling webhook "validate.nginx.ingress.kubernetes.io": Post "https://ingress-nginx-controller-admission.ingress-nginx.svc:443/networking/v1/ingresses?timeout=10s": Error here

Like below:

  1. context deadline exceeded
  2. x509: certificate signed by unknown authority
  3. Temporary Redirect
  4. EOF
  5. no endpoints available for service "ingress-nginx-controller-admission"

...and many more.

My Observations:

As soon as the the ingress resource/rules yaml is applied, the above error is shown and the Ingress Controller gets restarted as shown below:

NAME                                        READY   STATUS      RESTARTS          AGE
ingress-nginx-controller-5cf97b7d74-zvrr6   1/1     Running            6          30m
ingress-nginx-controller-5cf97b7d74-zvrr6   0/1     OOMKilled          6          30m

ingress-nginx-controller-5cf97b7d74-zvrr6   0/1     CrashLoopBackOff   6          30m

ingress-nginx-controller-5cf97b7d74-zvrr6   0/1     Running            7          31m

ingress-nginx-controller-5cf97b7d74-zvrr6   1/1     Running            7          32m

One possible solution could be (not sure though) mentioned here: https://stackoverflow.com/a/69289313/12241977

But not sure if it could possibly work in case of Managed Kubernetes services like AWS EKS as we don't have access to kube-api server.

Also the section "kind: ValidatingWebhookConfiguration" has below field from yaml:

clientConfig:
  service:
    namespace: ingress-nginx
    name: ingress-nginx-controller-admission
    path: /networking/v1/ingresses

So what does the "path: /networking/v1/ingresses" do & where it resides or simply where we can find this path? I checked the validation webhook using below command but, not able to get where to find the above path

kubectl describe validatingwebhookconfigurations ingress-nginx-admission

Setup Details

I installed using the Bare-metal method exposed with NodePort

Ingress Controller Version - v1.1.0

Kubernetes Cluster Version (AWS EKS): 1.21

Upvotes: 2

Views: 6992

Answers (1)

AT07
AT07

Reputation: 53

Ok, I got this working now: I was getting the status as "OOMKilled" (Out Of Memory). So what I did is I've added the "limits:" section under "resources:" section of Deployment yaml as below:

      resources:
        requests:
          cpu: 100m
          memory: 90Mi
        limits:              
          cpu: 200m
          memory: 190Mi

Now, it works fine for me.

Upvotes: 2

Related Questions