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

Gateway.Spec.Addresses.Value should be optional #3612

Open
robscott opened this issue Feb 13, 2025 · 1 comment · May be fixed by #3616
Open

Gateway.Spec.Addresses.Value should be optional #3612

robscott opened this issue Feb 13, 2025 · 1 comment · May be fixed by #3616
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Milestone

Comments

@robscott
Copy link
Member

robscott commented Feb 13, 2025

What would you like to be added:
I'd like Gateway.Spec.Addresses.Value to be optional.

Why this is needed:
It should be valid to request a type of address without specifying the value that address should have. For example, on Google Cloud, we have a Cross Region ILB and we'd like users to be able to request ephemeral addresses in specific locations. That is currently quite challenging when the value of a requested address must be specified.

Note: Per our versioning policy it is valid to make required fields optional in a minor release across any release channel.

@robscott robscott added the kind/feature Categorizes issue or PR as related to a new feature. label Feb 13, 2025
@robscott robscott added this to the v1.3.0 milestone Feb 13, 2025
@EyalPazz
Copy link
Contributor

/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
Status: In Progress
Development

Successfully merging a pull request may close this issue.

2 participants