-
Notifications
You must be signed in to change notification settings - Fork 303
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
ingress controller gave me 2 IP addresses instead of 1 when I added TLS #410
Comments
Of course, it could have been an error on the Google API side, not the controller. |
/kind bug |
/assign |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
I was simply running the ingress on WAN port 80 and everything was working fine. Then at the same time I added a tls cert and this annotation to an ingress manifest:
And now the kubernetes ingress object reports that it is listening on both ports, but in fact the original IP address only listens to port 80. When I log into the GCP console, I can see that my port 443 frontend has a different IP than the port 80 frontend.
The k8s cluster is GKE v1.10.5-gke.2.
I do not think this is supposed to happen. Email me if you want specifics (username at gmail), I don't want to publicly post the project details today.
The text was updated successfully, but these errors were encountered: