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

Support networking.k8s.io ingresses #53

Closed
Aluxima opened this issue Sep 27, 2021 · 2 comments · Fixed by #64
Closed

Support networking.k8s.io ingresses #53

Aluxima opened this issue Sep 27, 2021 · 2 comments · Fixed by #64

Comments

@Aluxima
Copy link
Contributor

Aluxima commented Sep 27, 2021

Kubernetes extensions/v1beta1 Ingress will be removed in 1.22.

In order to support all Kubernetes versions, Yggdrasil could try working with networking.k8s.io ingresses first before falling back to extensions/v1beta1 if the cluster doesn't have the new API capability.

Any thoughts on other ways to handle both versions?
@Joseph-Irving
Copy link
Contributor

Doing some kind of fallback is one way, but this could get a bit messy if your clusters are on different versions. It might be easier just to change it to networking.k8s and mark the min kubernetes version as 1.19, anything older than that is officially unsupported now anyway.

@Aluxima
Copy link
Contributor Author

Aluxima commented Sep 29, 2021

Yeah it will be cleaner to completely switch to networking.k8s.
However we still have some old k8s cluster not supporting this apiversion yet, so we will have to wait until we upgrade.

@Aluxima Aluxima mentioned this issue Jun 28, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Use sharedInformers, fix CPU usage, support all ingress apiGroups Aluxima/yggdrasil
2 participants
@Joseph-Irving @Aluxima