Closed runyontr closed 1 year ago
my first experience with it failing was disabling a BB component when packaging/deploying, and the remove failed because it tried to delete the HelmRelease for said component.
The use of --ignore-not-found
has fixed the remove from failing.
Assuming this is not desired, but there are still some orphaned components that remain after remove. Namely:
@runyontr - what would you think about rearranging the zarf.yaml actions.onRemove.before so the kyverno HR delete is before the kyverno webhook cleanups?
- cmd: ./zarf tools kubectl delete helmrelease -n bigbang kyvernopolicies --ignore-not-found
description: Delete kyvernopolicies
- cmd: ./zarf tools kubectl delete helmrelease -n bigbang kyverno --ignore-not-found
description: Delete kyverno
- cmd: ./zarf tools kubectl delete validatingwebhookconfigurations.admissionregistration.k8s.io kyverno-policy-validating-webhook-cfg kyverno-resource-validating-webhook-cfg --ignore-not-found
description: Cleanup validating webhoooks from kyverno
- cmd: ./zarf tools kubectl delete mutatingwebhookconfigurations.admissionregistration.k8s.io kyverno-policy-mutating-webhook-cfg kyverno-resource-mutating-webhook-cfg kyverno-verify-mutating-webhook-cfg --ignore-not-found
description: Cleanup mutating webhooks from kyverno
in my testing, this removed the kyverno components without the lingering webhooks remaining on zarf package remove.
Sounds great to me!
@MxNxPx do you want to make this contribution?
Lots of issue uninstalling and having hanging resources/namespaces/etc