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

GCE error unable to create HTTPS LB #1417

Closed
tonglil opened this Issue Sep 25, 2017 · 9 comments

Comments

Projects
None yet
7 participants
@tonglil
Copy link
Contributor

tonglil commented Sep 25, 2017

I am getting a strange error that I cannot debug when I tried to create an ingress today (that was working a couple days ago):

googleapi: Error 400: Invalid value for field 'namedPorts[2].port': '0'. Must be greater than or equal to 1, invalid

This Stackoverflow answer doesn't work for me as there are no port mappings on my instance groups.

Any insight into this?

@tonglil

This comment has been minimized.

Copy link
Contributor

tonglil commented Sep 25, 2017

This is the manifest:

---
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
 name: test
spec:
 backend:
   serviceName: echo-app
   servicePort: 88
---
apiVersion: v1
kind: Service
metadata:
  name: echo-app
spec:
  type: NodePort
  selector:
    app: echo-app
  ports:
    - name: http
      port: 88
      protocol: TCP
      targetPort: 8000

kubectl version:

Client Version: version.Info{Major:"1", Minor:"7", GitVersion:"v1.7.5", GitCommit:"17d7182a7ccbb167074be7a87f0a68bd00d58d97", GitTreeState:"clean", BuildDate:"2017-08-31T09:14:02Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"7", GitVersion:"v1.7.5", GitCommit:"17d7182a7ccbb167074be7a87f0a68bd00d58d97", GitTreeState:"clean", BuildDate:"2017-08-31T08:56:23Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}

@tonglil tonglil changed the title Strange GCE error unable to create HTTPS LB GCE error unable to create HTTPS LB Sep 25, 2017

@aledbf aledbf added the backend/gce label Sep 26, 2017

@nicksardo

This comment has been minimized.

Copy link
Member

nicksardo commented Sep 26, 2017

Hey @tonglil
Error events can appear for any/all ingresses regardless of the ingress that caused it. I'm guessing a service without type NodePort was referenced in one of your ingress manifests.

@tonglil

This comment has been minimized.

Copy link
Contributor

tonglil commented Sep 29, 2017

@nicksardo the strange thing was that the manifests didn't change (for the 2 ingress in the cluster).

It's likely it was a temporary issue. I can reopen if I encounter it again.

Thanks for following up!

@tonglil tonglil closed this Sep 29, 2017

@lvnilesh

This comment has been minimized.

Copy link

lvnilesh commented Nov 23, 2017

It was working for me two hours ago. I changed nothing and now I see. Hope it is temporary.

googleapi: Error 400: Invalid value for field 'namedPorts[0].port': '0'. Must be greater than or equal to 1, invalid
@dfang

This comment has been minimized.

Copy link

dfang commented Dec 7, 2017

same here

@aledbf

This comment has been minimized.

Copy link
Member

aledbf commented Dec 7, 2017

@nicksardo

This comment has been minimized.

Copy link
Member

nicksardo commented Dec 7, 2017

This comes up all the time. It always happens when one of your ingress objects references a service which doesn't have type NodePort. kubernetes/ingress-gce#75

@ptagr

This comment has been minimized.

Copy link

ptagr commented Mar 24, 2018

got the error. Service had to be NodePort

@Freyert

This comment has been minimized.

Copy link

Freyert commented Sep 10, 2018

I ran into this issue today, and the solution was to delete and re-install the NGINX ingress controller. I can route to ClusterIP services again!

I suppose this is indicative of something sinister though.

This is using stable/nginx-ingress-0.28.2 from https://github.com/helm/charts

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment