-
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
Static ip on internal ingress #1171
Comments
Mee too. So I am not alone. |
I have the same problem, I tried different ways but none of those worked for me. |
Hi all, This is not currently supported since internal ingress requires a regional static IP, but is planned for GA. I have created a PR for this here: #1174 |
Hello, this should be launching in Rapid + Regular channel within the next two weeks! |
From my understanding this landed in 1.9. I tried this on a shared vpc setup and I get I am on gke
Is this feature supposed to work with shared vpc where the internal IP is not in the same project where gke? |
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. |
Not sure whether it is too late but I found a potential solution for this on stackoverflow:
|
By anychance did you get this working? Facing similar issue |
@sumeetoc
|
Anyone looking for solution, basically the service project is used to create the resource, and host subnetwork url is used as reference Example:
|
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
Rotten issues close after 30d of inactivity. Send feedback to sig-contributor-experience at kubernetes/community. |
@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. |
Hi, I've been struggling to set static ip for my internal ingress (GCP Kubernetes with a Deployment, Service NodePort and Internal Ingress).
I'm creating this issue because I can't find a way or an annotation to specify an internal static ip to the internal ingress.
Is this currently supported?
The text was updated successfully, but these errors were encountered: