We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Feedback from helping a customer get this working:
I imagine it’s a fairly common use case to want to bind to a reserved IP at the point of creating the cluster (or later defining an Ingress manually). It feels a little disjointed that it’s not picked up at the Ingress level. Coming from GCP, a reserved IP can be bound in the same place that routing is defined.
I imagine it’s a fairly common use case to want to bind to a reserved IP at the point of creating the cluster (or later defining an Ingress manually).
It feels a little disjointed that it’s not picked up at the Ingress level.
Coming from GCP, a reserved IP can be bound in the same place that routing is defined.
We should review what GCP is doing and if we can make this user experience more intuitive
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Feedback from helping a customer get this working:
We should review what GCP is doing and if we can make this user experience more intuitive
The text was updated successfully, but these errors were encountered: