removing k8s application destroys storage
Bug #1814517 reported by
Ian Booth
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
When removing any application with storage, unless --destroy-storage is used, the storage should be retained after deletion. With k8s apps, the PVs are deleted even without --destroy-storage.
It looks like the PV Reclaim Policy is always set to Delete.
Changed in juju: | |
milestone: | 2.5.2 → 2.5.3 |
Changed in juju: | |
milestone: | 2.5.3 → 2.5.4 |
Changed in juju: | |
milestone: | 2.5.4 → 2.5.5 |
Changed in juju: | |
milestone: | 2.5.6 → 2.5.8 |
Changed in juju: | |
milestone: | 2.5.8 → 2.5.9 |
Changed in juju: | |
milestone: | 2.5.9 → none |
To post a comment you must log in.
This can happen if a default, existing storage class is used, that is not created by Juju. The storage class's Reclaim Policy attribute defines the policy on any volume it creates. We may need to look at trying to edit the policy on volumes after creation.