-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consolidate workload controller status #2804
Comments
/milestone v1.23 |
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:
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 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 |
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:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale Targeting for 1.24 as alpha. |
Hello @ravisantoshgudimetla @soltysh 👋, 1.24 Enhancements team here. Just checking in as we approach enhancements freeze on 18:00pm PT on Thursday Feb 3rd, 2022. For note, This enhancement is targeting for stage Here’s where this enhancement currently stands:
Looks like for this one, we would just require updating the open KEP PR #2833 for following & have it merged:
At the moment, the status of this enhancement is marked as |
Hello @ravisantoshgudimetla @soltysh , just a quick check-in again, as we approach the 1.24 enhancements freeze. Please plan to get #2833 merged before enhancements freeze on Thursday, February 3rd at 18:00pm PT. For note, the current status of the enhancement is at |
@Priyankasaggu11929 PR should be updated, currently waiting for PRR |
With KEP PR #2833 merged now, this enhancement is ready for the 1.24 enhancements freeze. 🚀 For note, the status is |
Hi @ravisantoshgudimetla 👋🏻 1.24 Docs shadow here. This enhancement is marked as 'Needs Docs' for the 1.24 release. Please follow the steps detailed in the documentation to open a PR against the dev-1.24 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thu March 31, 11:59 PM PDT. Also, if needed take a look at Documenting for a release to familiarize yourself with the docs requirement for the release. Thanks! |
Hello @atiratree @ravisantoshgudimetla 👋 I'm just checking in once more as we approach the 1.24 Code Freeze on 18:00 PDT, Tuesday, March 29th 2022 Please ensure the following items are completed:
For note, the status of this enhancement is currently marked as Could you please link any recent PRs for the enhancement in the issue description (if any)? I wasn't able to identify any related PRs on the Kubernetes/Kubernetes repository. Thank you so much! |
@ravisantoshgudimetla Will you please confirm if you are going to implement this feature in 1.24? Thanks! |
Hi @mehabhalodiya - We will not get the PR merged this release. The goal is to have the KEP merged this release. |
Thanks for the headsup @ravisantoshgudimetla. Removing this feature from the 1.24 release |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close not-planned |
@k8s-triage-robot: Closing this issue, marking it as "Not Planned". In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/reopen |
@atiratree: Reopened this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
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:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close not-planned |
@k8s-triage-robot: Closing this issue, marking it as "Not Planned". In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
This is an area that can still be improved. /reopen |
@atiratree: Reopened this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
There is still an interest in offering more conditions: kubernetes/kubernetes#79606 (comment) |
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.
k/enhancements
) update PR(s): Consolidate workload controllers status #2833k/k
) update PR(s):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
The text was updated successfully, but these errors were encountered: