Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug. Service does not have any active endpoints. 0.9.0-beta.11 #984

Closed
z1oy opened this issue Jul 17, 2017 · 2 comments
Closed

Bug. Service does not have any active endpoints. 0.9.0-beta.11 #984

z1oy opened this issue Jul 17, 2017 · 2 comments

Comments

@z1oy
Copy link

z1oy commented Jul 17, 2017

Hi!

My conf:

---
apiVersion: v1
kind: ConfigMap
metadata:
  name: nginx-ingress-controller-tcp
  namespace: kube-system
data:
  "5001": "ns/logstash:5001"

---
apiVersion: v1
kind: ConfigMap
metadata:
  name: nginx-ingress-controller-udp
  namespace: kube-system
data:
  "5001": "ns/logstash:5001"

If i use two protocols in service:

---
apiVersion: v1
kind: Service
metadata:
  name: logstash
  namespace: ns
spec:
  ports:
  - name: log
    protocol: UDP
    port: 5001
    targetPort: 5001
  - name: log2
    protocol: TCP
    port: 5001
    targetPort: 5001

I got error:
5 controller.go:542] service ns/logstash does not have any active endpoints for port 5001 and protocol TCP

If I delete the first record about the udp, then the tcp starts working.

If the ports are the same, the controller sees only the first entry in the service.

@z1oy
Copy link
Author

z1oy commented Jul 17, 2017

Changing the port number helps to get around this problem

@aledbf
Copy link
Member

aledbf commented Aug 22, 2017

Closing. This was fixed in #1078

@aledbf aledbf closed this as completed Aug 22, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants