-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Upgrading k3s version to v1.24.3 fails to perform argocd commands #10422
Comments
What is the version of your Argo CD CLI please? |
ArgoCD CLI version is v2.3.4 |
Please use a CLI either 2.4.x or >= 2.3.7, as those version will contain the fix #9546 which added support for Kubernetes >=1.24 |
Confirmed working 2.3.7 |
This worked. But after upgrading i'm getting this error on my cluster when I do an argo list:
|
Current argo CD CLI version: 2.3.7 |
It seems that the cluster doesn't have the proper CRDs installed. However, I think you should move that to the Argo workflows issue tracker. |
any update on this? Is there any solutions, we are waiting for response to get this fixed |
jannfis Any updates here? |
I'm pretty sure this is a problem with the cluster, not with Argo CD. "The server could not find the requested resource" usually means that the appropriate CRDs are not installed. |
@jannfis Thank you, Found the issue, since we are using latest version of k3s i.e v1.24.3+k3s1, it requires latest CRD's updated with the latest apiVersion. |
Checklist:
argocd version
.Describe the bug
Production Environment:
K3s Version:
k3s:v1.21.4-k3s1
Cluster Configuration:
Eks clusters having 4 spot nodes.
We noticed our workflows are failing due to this error - "Failed to wait for service account secret: timed out waiting for the condition". Started happening after upgrading k3s to v1.24.3.
After performing the steps updated here, did solve the issue - #9422 (comment)
To Reproduce
Upgrade k3s to 1.24.3 and then this happens during argocd cluster add or argocd app create step
ArgoCD Version
v2.4.2
Logs
time="2022-08-22T08:39:32Z" level=info msg="ClusterRoleBinding "argocd-manager-role-binding" updated"
time="2022-08-22T08:40:02Z" level=fatal msg="Failed to wait for service account secret: timed out waiting for the condition"
time="2022-08-22T08:40:04Z" level=fatal msg="rpc error: code = InvalidArgument desc = application spec for k3s-upgrade3 is invalid: InvalidSpecError: Unable to get cluster: rpc erro
r: code = NotFound desc = cluster "https://onboarding-tenant.atlan.dev/kubernetes/virtualcluster/loft-cluster-loh2p/vcluster-k3s-upgrade3/k3s-upgrade3\" not found"
Please let me know if any more information is required.
The text was updated successfully, but these errors were encountered: