Replies: 1 comment
-
Hi there ! Any idea or good soul who has a lead? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi there,
Context
extension/v1beta1
ofingresses
replaced bynetworking.k8s.io/v1
.v2.0.3+8d2b13d
(yes we need to upgrade 😅 )Observation
When using the cascaded deletion, we had
Applications
that were stuck in deletion while waiting for leaf resources to be deleted.Troubleshooting
In the App of app
Application
objects we noticedwhereas in
Question
Why are the API version different between the
.status.operationState.syncResult.resources
and.status.resources
?networking.k8s.io/v1
networking.k8s.io/v1
by kubectlOur hypothesis is that our current version of Argo-cd "finalizer" only supports this kind of "hard-coded" API version of the ingress and is stuck since it does not found the objects it is looking for with the strict API version. But more precision are welcome.
As a workaround, we manually delete the ingresses objects with the
networking.k8s.io/v1
API version and everything ends ok.In advance, many thanks for your time, help and explanations 🙏🏻
Beta Was this translation helpful? Give feedback.
All reactions