Removing application removes custom resources that should persist
Bug #1862390 reported by
Kenneth Koski
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Medium
|
Yang Kelvin Liu |
Bug Description
In the Kubeflow bundle, there is a charm that creates a Profile object, which in turn gets an associated namespace created for it. I would like to be able to mark the Profile object as not getting removed when the associated charm is removed. This would let us redeploy that charm or Kubeflow as a whole without deleting user data, which is stored in the associated namespace.
Changed in juju: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I'm running into an issue where `juju destroy-model kubeflow` will remove the `kubeflow- dashboard` charm, triggering a delete of the Profile resource that it created when deployed. However, the Profile object has a finalizer on it that requires the `kubeflow-profiles` charm to clear before it can actually get deleted. That charm also got deleted with the destroy model step, so the Profile object can't get deleted, and hangs the kubeflow namespace deletion.
With https:/ /bugs.launchpad .net/juju/ +bug/1860688 landing, Profile resources will be cluster-scoped, and it seems like we can use the logic of deleting all namespaced resources associated with a charm when it's deleted, and leave cluster-scoped resources alone. That would prevent this namespace deletion hang issue from occurring.