Consolidate workload controller status

[ravisantoshgudimetla]

Enhancement Description

Only deployment controller has status to reflect the state during it's lifecycle. This enhancement extends the scope of those of states to other controllers(DaemonSet and StatefulSet). Please note that while the states are same, their definition may change depending on how workload controller performs operations like updates, deletions etc.

• One-line enhancement description (can be used as a release note):
• Kubernetes Enhancement Proposal: Consolidate workload controllers status #2833
• Discussion Link:
• Primary contact (assignee):
• Responsible SIGs:
• 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): Consolidate workload controllers status #2833
  • 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.

/sig apps

[salaxander]

/milestone v1.23

[kevindelgado]

Hi @ravisantoshgudimetla! 1.23 Enhancements team here. Just checking in as we approach enhancements freeze on Thursday 09/09. Here's where this enhancement currently stands:

• KEP file using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable
• KEP has a test plan section filled out.
• KEP has up to date graduation criteria.
• KEP has a production readiness review that has been completed and merged into k/enhancements.

Looks like for this one we would just need the KEP to merge by enhancements freeze :)

Also, can you update this issue's description when you get a chance to make it easier for us to track. (i.e. link to the KEP PR, one line summary, correct alpha release target)

Thanks!

[kevindelgado]

Hi @ravisantoshgudimetla

Ping! As a reminder your PR (#2833) needs to merge by EOD PST tomorrow September 9th to be included in the 1.23 Release. After that time you will need to request an exception.

Lmk if you need anything,
Kevin

[soltysh]

@kevindelgado Ravid and I decide we're drop that from 1.23 milestone, can you remove it also from the tracking sheet as well?

/milestone clear

[k8s-triage-robot]

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[ravisantoshgudimetla]

/remove-lifecycle stale

Targeting for 1.24 as alpha.