-
Notifications
You must be signed in to change notification settings - Fork 194
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
Alert: Resources using Deprecated API Namespaces should be updated. #159
Comments
Would like to add |
|
@DoNnMyTh would you like to take up and update these ? |
@saiyam1814 i commented these because i can update all to latest version but most of them are still on /v1beta1. What ever you say i'll do. |
Assign this to me and will be done next week :) |
We'll need to update some of the CRDs upstream as well and/or inform the maintainers regarding this because once K3s v1.22 is out, their applications will no longer work. |
Sure @sr229, I'll update above this week, but issue many projects haven't moved to newer resources so i'm thinking we should update them when they will update it, and we can put a warning postinstall.md |
AFAIK 1.22 is still 5 to 6 months away so i guess they got time to update it, and as soon as they update it we will also update it |
@keithhubner Can you look bitwardenrs |
@stevefan1999-personal Can you please look at Argo CD |
I updated the CRDs to v1 in Traefik2 (#293) |
This issue is a:
We have some offending Applications that still uses deprecated API namespaces, from my discovery, the following WILL NOT work on K3s 1.20+
litmuschaos
(usesapiextensions.k8s.io/v1beta1
, deprecated in favor ofapiextensions.k8s.io/v1
)bitwardenrs
(usesextensions/v1beta1
Ingress classes. Will not work on Kubernetes 1.22)rancher
(example uses deprecatedextensions/v1beta1
Ingress class for post install guide)The text was updated successfully, but these errors were encountered: