ConfigMap / Secret Orchestration

[kfox1111]

Enhancement Description

• One-line enhancement description (can be used as a release note): Support for proper orchestration of deployments/statefulsets/daemonsets when configmaps/secrets are involved.
• Kubernetes Enhancement Proposal: ConfigMap / Secret Orchestration #948
• Discussion Link: predates this requirement. most recent discussion: Facilitate ConfigMap rollouts / management kubernetes#22368
• Primary contact (assignee): kfox1111
• Responsible SIGs: unclear. app? core? storage?
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y):
  • Beta release target (x.y):
  • Stable release target (x.y):
• Alpha
  • KEP (k/enhancements) update PR(s): ConfigMap / Secret Orchestration #948
  • Code (k/k) update PR(s):
  • Docs (k/website) update PR(s):

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

[kfox1111]

Not sure which apply. taking a stab at a few.
/sig apps
/sig storage
/sig usability

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[kfox1111]

/remove-lifecycle rotten

[SOF3]

How would this interact with secrets created for serviceaccounts?

[kfox1111]

How k8s creates the secret and how it gets into the pod, either by rolling all the pods, or by continually injecting the updated secret seems like the same issue as a user doing it?

Maybe different though if kubelet itself is generating secrets and there is no k8s secret involved?