Open adamissaoui opened 1 month ago
Hi, I think this might be related to argocd as it does not use helm but helm template and applying manifests what in the end is not a helm release (helm release version secret will not exist)
@machecazzon is correct. Since deploying with ArgoCD uses helm template, the virtual cluster is deployed with manifests instead of a helm release. The vcluster CLI currently assumes that the virtual clusters were created with helm (not with manifests) and try to delete using helm, which relies on the helm release secret.
We've added an enhancement into our backlog in order to improve the experience.
What happened?
when creating vcluster using cli, the deletion works fine however when creating the vcluster using argocd application the deletion is not works.
only if i delete the argocd application the vcluster got deleted.
What did you expect to happen?
The vcluster delete should delete any vcluster that can be listed through cli
How can we reproduce it (as minimally and precisely as possible)?
vcluster list | grep vc-1
Output :
vc-1 | arn:aws:eks:us-east-1:123456789:cluster/VCLUSTER | vcluster-vc-1 | Running | 0.19.6 | | 2024-07-09 10:39:54 +0100 IST | 24h57m51s | OSS
vcluster delete vc-1 --debug
Anything else we need to know?
No response
Host cluster Kubernetes version
vcluster version
VCluster Config