Kubernetes Nginx Ingress not finding service endpoint

Question

I'm having some trouble getting the Nginx ingress controller working in my Kubernetes cluster. I have created the nginx-ingress deployments, services, roles, etc., according to https://kubernetes.github.io/ingress-nginx/deploy/

I also deployed a simple hello-world app which listens on port 8080

apiVersion: apps/v1
kind: DaemonSet
metadata:
  name: hello-world
  namespace: default
spec:
  selector:
    matchLabels:
      name: hello-world
  template:
    metadata:
      labels:
        name: hello-world
    spec:
      containers:
      - name: hello-world
        image: myrepo/hello-world
        resources:
          requests:
            memory: 200Mi
            cpu: 150m
          limits:
            cpu: 300m
        ports:
          - name: http
            containerPort: 8080
            protocol: TCP

And created a service for it

kind: Service
apiVersion: v1
metadata:
  namespace: default
  name: hello-world
spec:
  selector:
    app: hello-world
  ports:
    - name: server
      port: 8080

Finally, I created a TLS secret (my-tls-secret) and deployed the nginx ingress per the instructions. For example:

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  annotations:
    kubernetes.io/ingress.class: nginx
  name: hello-world
  namespace: default
spec:
  rules:
    - host: hello-world.mydomain.com
      http:
        paths:
        - path: /
          backend:
            serviceName: hello-world
            servicePort: server
  tls:
      - hosts:
          - hello-world.mydomain.com
        secretName: my-tls-cert

However, I am unable to ever reach my application, and in the logs I see

W0103 19:11:15.712062       6 controller.go:826] Service "default/hello-world" does not have any active Endpoint.
I0103 19:11:15.712254       6 controller.go:172] Configuration changes detected, backend reload required.
I0103 19:11:15.864774       6 controller.go:190] Backend successfully reloaded.

I am not sure why it says Service "default/hello-world" does not have any active Endpoint. I have used a similar service definition for the traefik ingress controller without any issues.

I'm hoping I'm missing something obvious with the nginx ingress. Any help you can provide would be appreciated!

naming everything hello-world is a really nice way to get stuck later — J011195
– J011195, Commented Jun 2, 2020 at 14:53
i suppose it was not actually the connection of nginx with the service but the connection of the service with the pod which failed. i think its totally irrelevant which labels you use as long as they match, — U.V.
– U.V., Commented Feb 23, 2021 at 10:21
This is one of those post on SO where all answers are right basically — nnsense
– nnsense, Commented Aug 14, 2022 at 8:26

cookandy · Accepted Answer · 2019-01-03 22:25:12Z

43

I discovered what I was doing wrong. In my application definition I was using name as my selector

  selector:
    matchLabels:
      name: hello-world
  template:
    metadata:
      labels:
        name: hello-world

Whereas in my service I was using app

  selector:
    app: hello-world

After updating my service to use app, it worked

  selector:
    matchLabels:
      app: hello-world
  template:
    metadata:
      labels:
        app: hello-world

answered Jan 3, 2019 at 22:25

cookandy

1,0751 gold badge9 silver badges17 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

Tara Prasad Gurung Over a year ago

Exactly, I had a similar cased of wrong labels in deployment and the service section.

rantlr Over a year ago

@cookandy Did you mean after updating the application definition to use app, it worked?

Malkavian Dec 12, 2024 at 9:18

I might have a similar error. could you take a look here and tell me if I am doing same mistake? serverfault.com/questions/1168759/…

Rostislav Matl · Accepted Answer · 2019-11-20 21:43:32Z

5

Another situation when it may happen is when ingress class of the ingress controller does not match ingress class in the ingress resource manifest used for your services.

Nginx installation command, short example:

  helm install stable/nginx-ingress \
  --name ${INGRESS_RELEASE_NAME} \
  --namespace ${K8S_NAMESPACE} \
  --set controller.scope.enabled=true \
  --set controller.scope.namespace=${K8S_NAMESPACE} \
  --set controller.ingressClass=${NGINX_INGRESS_CLASS}

ingress resource spec. , excerpt:

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  labels:
  annotations:
    # folowing line is not valid for K8s or Helm, 
    # but reflects the values must be the same
    kubernetes.io/ingress.class: ${NGINX_INGRESS_CLASS}

edited Nov 20, 2019 at 21:43

answered Oct 24, 2019 at 12:32

Rostislav Matl

4,5934 gold badges32 silver badges55 bronze badges

Comments

try-catch-finally · Accepted Answer · 2021-09-16 08:58:12Z

5

In our case, this was caused by having the ingress resource definition on a different namespace then the services.

kind: Ingress
apiVersion: networking.k8s.io/v1beta1
metadata:
  name: nginx-ingress-rules
  namespace: **default**       #<= make sure this is the same value like the namespace on the services you are trying to reach

edited Sep 16, 2021 at 8:58

try-catch-finally

7,6606 gold badges50 silver badges71 bronze badges

answered Apr 2, 2021 at 13:37

user2995891

1111 silver badge8 bronze badges

Comments

kerlyn · Accepted Answer · 2021-09-04 18:49:15Z

1

In my case, I included an "id" directive in my Service selector that was missing from the Deployment metadata and this prevented the endpoints controller from finding the correct Pod. I expect the reverse case would also fail:

---
apiVersion: v1
kind: Service
metadata:
  name: some-service
spec:
  ports:
    - name: port-name
      port: 1234
      protocol: TCP
  selector:
    app: some-app
    id: "0"  ## include in both or neither

answered Sep 4, 2021 at 18:49

kerlyn

3682 silver badges10 bronze badges

Comments

Eternal21 · Accepted Answer · 2022-08-28 01:07:08Z

0

In my case the actual deployment containers that the service was pointing to were not running, due to ImagePullError. Once I resolved the issue, and the containers started running, the endpoint error went away.

edited Aug 28, 2022 at 1:07

answered Aug 28, 2022 at 0:52

Eternal21

4,7843 gold badges57 silver badges72 bronze badges

Comments

Bill-- · Accepted Answer · 2023-06-11 21:13:51Z

0

I had written in the wrong host domain in my ingress resource spec.

answered Jun 11, 2023 at 21:13

Bill--

1803 silver badges7 bronze badges

Collectives™ on Stack Overflow

Kubernetes Nginx Ingress not finding service endpoint

6 Answers 6

3 Comments

Comments

Comments

Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

6 Answers 6

3 Comments

Comments

Comments

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related