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

CRDs not updated when upgrading from v5.5.x to v6.x #148

Closed
54nd20 opened this issue Feb 16, 2024 · 0 comments · Fixed by #120
Closed

CRDs not updated when upgrading from v5.5.x to v6.x #148

54nd20 opened this issue Feb 16, 2024 · 0 comments · Fixed by #120
Labels
bug Something isn't working

Comments

@54nd20
Copy link
Member

54nd20 commented Feb 16, 2024

When upgrading from v5.5.x to v6.x argocd is updated to v2.9.2 but the CRDs are not updated. In particular CRD "applications.argoproj.io" needs to be updated. If that is not done, we run into issue argoproj/argo-cd#15220 which leads to very high CPU usage and the following warning messages in the log of the argocd application controller:

W0216 16:49:14.378592       1 warnings.go:70] unknown field "status.controllerNamespace"
W0216 16:49:14.378615       1 warnings.go:70] unknown field "status.sync.comparedTo.ignoreDifferences"

Change in CPU usage after updating the CRD "applications.argoproj.io":
argocd-application-controller

Steps to Reproduce the Problem

  1. Update component-argocd from v5.5.x to v6.x following procedure in documentation

Actual Behavior

  • Warnings in log of argocd-application-controller
  • Very high cpu usage of argocd-application-controller

Expected Behavior

  • Normal cpu usage
@54nd20 54nd20 added the bug Something isn't working label Feb 16, 2024
@DebakelOrakel DebakelOrakel linked a pull request Feb 19, 2024 that will close this issue
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant