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

Alert: Resources using Deprecated API Namespaces should be updated. #159

Open
1 of 3 tasks
sr229 opened this issue Mar 1, 2021 · 11 comments
Open
1 of 3 tasks

Alert: Resources using Deprecated API Namespaces should be updated. #159

sr229 opened this issue Mar 1, 2021 · 11 comments
Assignees

Comments

@sr229
Copy link
Contributor

sr229 commented Mar 1, 2021

This issue is a:

  • Bug Report
  • Enhancement suggestion
  • Feature request

We have some offending Applications that still uses deprecated API namespaces, from my discovery, the following WILL NOT work on K3s 1.20+

  • litmuschaos (uses apiextensions.k8s.io/v1beta1, deprecated in favor of apiextensions.k8s.io/v1)
  • bitwardenrs (uses extensions/v1beta1 Ingress classes. Will not work on Kubernetes 1.22)
  • rancher (example uses deprecated extensions/v1beta1 Ingress class for post install guide)
@sr229
Copy link
Contributor Author

sr229 commented Mar 1, 2021

Would like to add argo in the list since they also use deprecated resources.

@DoNnMyTh
Copy link
Contributor

DoNnMyTh commented Mar 2, 2021

  • litmuschaos uses apiextensions.k8s.io/v1beta1 in their latest release https://litmuschaos.github.io/litmus/litmus-operator-v1.13.0.yaml
  • bitwardenrs uses extensions/v1beta1 in its latest helm chart at https://github.com/k8s-at-home/charts/tree/master/charts/bitwardenrs
  • rancher post_install.md can be updated to extensions/v1 reference https://github.com/rancher/rancher/blob/master/chart/templates/ingress.yaml
  • argo cd can be updated with https://github.com/argoproj/argo-cd/blob/master/manifests/install.yaml but it's still on older resources

@saiyam1814
Copy link
Contributor

@DoNnMyTh would you like to take up and update these ?

@DoNnMyTh
Copy link
Contributor

DoNnMyTh commented Mar 5, 2021

@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.

@DoNnMyTh
Copy link
Contributor

DoNnMyTh commented Mar 5, 2021

Assign this to me and will be done next week :)

@sr229
Copy link
Contributor Author

sr229 commented Mar 6, 2021

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.

@DoNnMyTh
Copy link
Contributor

DoNnMyTh commented Mar 6, 2021

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

@DoNnMyTh
Copy link
Contributor

DoNnMyTh commented Mar 6, 2021

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

@DoNnMyTh
Copy link
Contributor

DoNnMyTh commented Mar 8, 2021

@keithhubner Can you look bitwardenrs

@DoNnMyTh
Copy link
Contributor

@stevefan1999-personal Can you please look at Argo CD

@Johannestegner
Copy link
Contributor

I updated the CRDs to v1 in Traefik2 (#293)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants