Re: [kubernetes/kubernetes] ConfigMap/Secret Volume can become orphaned at termination if a required configmap/secret never exists (#64788)
Kubernetes Submit Queue
[MILESTONENOTIFIER] Milestone Issue Needs Attention
@saad-ali @kubernetes/sig-storage-misc
Action required: During code slush, issues in the milestone should be in progress.
If this issue is not being actively worked on, please remove it from the milestone.
If it is being worked on, please add the status/in-progress label so it can be tracked with other in-flight issues.
Note: If this issue is not resolved or labeled as priority/critical-urgent by Tuesday, June 5th it will be moved out of the v1.11 milestone.
sig/storage: Issue will be escalated to these SIGs if needed.priority/important-soon: Escalate to the issue owners and SIG owner; move out of milestone after several unsuccessful escalation attempts.kind/bug: Fixes a bug discovered during the current release.
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
Hemant Kumar
Kubernetes Submit Queue
[MILESTONENOTIFIER] Milestone Issue Needs Attention
@gnufied @saad-ali @kubernetes/sig-storage-misc
Action required: During code slush, issues in the milestone should be in progress.
If this issue is not being actively worked on, please remove it from the milestone.
If it is being worked on, please add the status/in-progress label so it can be tracked with other in-flight issues.
Note: If this issue is not resolved or labeled as priority/critical-urgent by Tuesday, June 5th it will be moved out of the v1.11 milestone.
sig/storage: Issue will be escalated to these SIGs if needed.priority/important-soon: Escalate to the issue owners and SIG owner; move out of milestone after several unsuccessful escalation attempts.kind/bug: Fixes a bug discovered during the current release.
—
Kubernetes Submit Queue
[MILESTONENOTIFIER] Milestone Removed From Issue
@gnufied @saad-ali @kubernetes/sig-storage-misc
Important: Code freeze is in effect and only issues with priority/critical-urgent may remain in the v1.11 milestone.
Kubernetes Submit Queue
[MILESTONENOTIFIER] Milestone Issue Needs Attention
Action Required: This issue has not been updated since Jun 5. Please provide an update.
Note: This issue is marked as priority/critical-urgent, and must be updated every 1 day during code freeze.
Example update:
ACK. In progress
ETA: DD/MM/YYYY
Risks: Complicated fix required
sig/storage: Issue will be escalated to these SIGs if needed.
priority/critical-urgent: Never automatically move issue out of a release milestone; continually escalate to contributor and SIG through all available channels.
kind/bug: Fixes a bug discovered during the current release.
Saad Ali
Reopening
#64855 fixed the issue if the secret does not exist.
But if the secret exists, but the specified key does not exist, the same issue is hit.
Saad Ali
Reopened #64788.
guineveresaenger
@saad-ali - any updates on work on this?
Hemant Kumar
I will look into this. Sorry, somehow I did not see notification for this.
Hemant Kumar
It is still on track. I aim to fix this by Tuesday.
guineveresaenger
@gnufied - can you please let us know of the status? At this point in the release cycle, we really do need daily updates on either the issue or an open PR, since we cannot see any work being done.
Saad Ali
This should not be treated as a release blocker since the behavior has existed prior to 1.12. If the fix takes too long, I'm ok dropping it from 1.12.
That said, @gnufied says he'll open up fix PR for this tmr Sept 14. So will leave it in 1.12 for now.
Saad Ali
PR is approved and awaiting merge: #68691