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

When available, use networking.k8s.io/v1 API version for Ingresses #180

Closed
LCaparelli opened this issue Oct 18, 2020 · 0 comments · Fixed by #182
Closed

When available, use networking.k8s.io/v1 API version for Ingresses #180

LCaparelli opened this issue Oct 18, 2020 · 0 comments · Fixed by #182
Assignees
Labels
RFE 🙏 Request For Enhancements
Milestone

Comments

@LCaparelli
Copy link
Member

Is your feature request related to a problem? Please describe.
networking.k8s.io/v1beta1 is deprecated in Kubernetes v1.19+ and running the operator in more recent clusters runs into:

W1018 19:47:08.954666 14552 warnings.go:67] networking.k8s.io/v1beta1 Ingress is deprecated in v1.19+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress

Describe the solution you'd like
It would be nice if the Operator used v1 Ingresses when available.

Describe alternatives you've considered
N/A

Additional context
N/A

Would you be able to assist in testing this feature if implemented?
Yes

@LCaparelli LCaparelli added the RFE 🙏 Request For Enhancements label Oct 18, 2020
@LCaparelli LCaparelli added this to the v0.4.0 milestone Oct 18, 2020
@LCaparelli LCaparelli self-assigned this Oct 18, 2020
@ricardozanini ricardozanini modified the milestones: v0.4.0, v0.5.0 Oct 27, 2020
@LCaparelli LCaparelli modified the milestones: v0.5.0, v0.4.0 Oct 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
RFE 🙏 Request For Enhancements
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants