If you are trying to resolve an environment-specific issue or have a one-off question about the edge case that does not require a feature then please consider asking a question in argocd slack channel.
We are ramping up to upgrade our clusters from 1.20 to 1.21. in 1.21 the cronjob batrh/v1beta1 API is deprecated. I updated a bunch of my resources because apparently we had about 10.
I am then greeted with
If the batch/v1beta1 resource already exists if you click into it from the app view I get
If you are trying to resolve an environment-specific issue or have a one-off question about the edge case that does not require a feature then please consider asking a question in argocd slack channel.
Checklist:
argocd version
.Describe the bug
We are ramping up to upgrade our clusters from 1.20 to 1.21. in 1.21 the cronjob batrh/v1beta1 API is deprecated. I updated a bunch of my resources because apparently we had about 10.
I am then greeted with
If the batch/v1beta1 resource already exists if you click into it from the app view I get
To Reproduce
https://github.com/kubernetes-sigs/descheduler/tree/master/charts/descheduler
install 0.19 descheduler-helm-chart
then upgrade to 0.22.1 descheduler.
Expected behavior
I expect my cronjob resource to sync and update.
Screenshots
above
Version
Logs