-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
Kubernetes 1.30 regression: runtime error: invalid memory address or nil pointer dereference
on server-side diff
#18548
Comments
runtime error: invalid memory address or nil pointer dereference
on server-side diff
When gitops engine initializes a cluster cache, it uses k8s libraries to load a GVKParser based on the cluster's OpenAPI v2 doc. In k8s 1.30, the OpenAPI doc lists the same GVK for some resources multiple times (by suffixing a The duplicated GVKs in the OpenAPI doc is a problem that k8s has had before. It was fixed a few months ago but seems to have been reintroduced in 1.30. I'm looking into it more next week. |
I'm not sure if this is the same issue, but I'm seeing something similar. I'm also on AWs EKS but kubernetes version 1.28. This causes the refresh button to spin indefinitely. Tried invalidating the cache, but it didn't help. Only happens with serverside diff set to true.
|
Checklist:
argocd version
.Describe the bug
Since upgrading to kubernetes 1.30, when syncing an Application that require server side diffs, like Kyverno (official chart) or MongoDB Percona Operator (official chart), the application remains in UNKNOWN HEAD state and no resources are synced or displayed in the UI.
This works with no issues on kubernetes 1.27. This is happening on a pristine EKS 1.30 environment we're testing.
Cluster cache clearing does not help.
The logs for argo's application controller:
To Reproduce
Expected behavior
Argo syncs normally
Screenshots
Version
Tested on 3 versions (no argo cli available)
Logs
The text was updated successfully, but these errors were encountered: