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

ArgoCD v1alpha1 version is deprecated #153

Open
megian opened this issue Jul 25, 2024 · 2 comments
Open

ArgoCD v1alpha1 version is deprecated #153

megian opened this issue Jul 25, 2024 · 2 comments

Comments

@megian
Copy link
Contributor

megian commented Jul 25, 2024

Since the ArgoCD Operator version 0.8.0, the v1beta1 is default. Older objects are going to be converted. Steward restores it and this creates a ping-pong every minute:

W0725 09:06:10.334131       1 warnings.go:70] ArgoCD v1alpha1 version is deprecated and will be converted to v1beta1 automatically. Moving forward, please use v1beta1 as the ArgoCD API version.
@DebakelOrakel
Copy link

DebakelOrakel commented Jul 25, 2024

That should not be the case.
Afaik steward does not create ArgoCD CR, it only checks if an ArgoCD is present.
The ArgoCD resource is created by component-argocd.

@megian
Copy link
Contributor Author

megian commented Jul 25, 2024

@HappyTetrahedron Steward is checking every minute if the ArgoCD Instance on type v1alpha1 object exists

Version: "v1alpha1",
. And it automatically gets converted to v1beta1. So are we sure, the Go implementation can read it on the old API path as well?

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

2 participants