Skip to content
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

Allow for kubernetes.civo.com/ipv4-address to be picked up from an ingress object #11

Open
DMajrekar opened this issue Oct 25, 2022 · 0 comments

Comments

@DMajrekar
Copy link
Contributor

DMajrekar commented Oct 25, 2022

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.

We should review what GCP is doing and if we can make this user experience more intuitive

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant