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.

Sign up for GitHub

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

Jump to bottom

Update any defined ingresses to use the new schema #371

Open
bmonkman opened this issue Apr 19, 2021 · 1 comment
Open

Update any defined ingresses to use the new schema #371

bmonkman opened this issue Apr 19, 2021 · 1 comment
Labels
enhancement good first issue Good first ticket, minimal dependencies

Comments

@bmonkman
Copy link
Contributor

As of EKS 1.19, k8s is starting to deprecate the beta ingress schema in favour of the new stable one, resulting in messages like:
Warning: extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress

Let's change the apiVersion for any ingresses in Zero projects. Probably just the two backend projects and the notification service at the moment
@bmonkman bmonkman added enhancement good first issue Good first ticket, minimal dependencies labels Apr 19, 2021
@bmonkman
Copy link
Contributor Author

Also update PodDisruptionBudget which has gone from policy/v1beta1 to policy/v1

@edmondop edmondop mentioned this issue Aug 23, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement good first issue Good first ticket, minimal dependencies
Projects
Zero - Full project view
Status: Up Next
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bmonkman