Details
-
Improvement
-
Status: Resolved
-
Blocker
-
Resolution: Fixed
-
None
Description
Quoting Mike here on the need for this from a supportability perspective:
Upon reviewing our code I realized that we're deleting persistent volumes when we delete pods. This means that in some cases we're deleting logs that may contain valuable debugging information before users can get a chance to collect logs from them. Without also fixing this issue we wouldn't get much benefit from adding a persistent volume to the logs directory for clusters with ephemeral storage because the logs would likely get cleaned up after a failure anyways.
We can disable volume deletion by default and add a flag to enable it if user wants it.
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Rank | Ranked higher |
| Fix Version/s | 1.2.0 [ 15308 ] | |
| Fix Version/s | 1.1.0 [ 15163 ] |
| Issue Type | Task [ 3 ] | Improvement [ 4 ] |
| Fix Version/s | 1.1.0 [ 15163 ] | |
| Fix Version/s | 1.2.0 [ 15308 ] |
| Rank | Ranked higher |
| Assignee | Tommie McAfee [ tommie ] | Simon Murray [ simon.murray ] |
| Labels | kubernetes | kubernetes releasenote |
| Priority | Major [ 3 ] | Blocker [ 1 ] |
| Rank | Ranked higher |
| Sprint | Kubernetes 8/13-8/27 [ 549 ] |
| Rank | Ranked higher |
| Rank | Ranked lower |
| Summary | Keep volumes after Pod deletion | Persistent Volume Janitor |
| Resolution | Fixed [ 1 ] | |
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Sprint |
| Rank | Ranked higher |
Description for release notes:
Known Issue: Pod volumes are deleted when pods are deleted. This means that important debugging information may not be available after a failure.
Workaround: None