-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Comments
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:
|
Hey @tonglil |
@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! |
It was working for me two hours ago. I changed nothing and now I see. Hope it is temporary.
|
same here |
@dfang please open a new issue in https://github.com/kubernetes/ingress-gce |
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 |
got the error. Service had to be |
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 |
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):
This Stackoverflow answer doesn't work for me as there are no port mappings on my instance groups.
Any insight into this?
The text was updated successfully, but these errors were encountered: