-
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
Clarify or remove the "status is only observations" rule #2527
Comments
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
As per KEP kubernetes/enhancements#2527 - remove the "from observation" guidance and add some discussion of when to use status fields vs. additional types for allocated resources.
As per KEP kubernetes/enhancements#2527 - remove the "from observation" guidance and add some discussion of when to use status fields vs. additional types for allocated resources.
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
/remove-lifecycle rotten |
As per KEP kubernetes/enhancements#2527 - remove the "from observation" guidance and add some discussion of when to use status fields vs. additional types for allocated resources.
As per KEP kubernetes/enhancements#2527 - remove the "from observation" guidance and add some discussion of when to use status fields vs. additional types for allocated resources.
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 |
As per KEP kubernetes/enhancements#2527 - remove the "from observation" guidance and add some discussion of when to use status fields vs. additional types for allocated resources.
The Kubernetes project currently lacks enough active 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 rotten |
/remove-lifecycle rotten |
impl PR is pending: kubernetes/community#5842 |
As per KEP kubernetes/enhancements#2527 - remove the "from observation" guidance and add some discussion of when to use status fields vs. additional types for allocated resources.
As per KEP kubernetes/enhancements#2527 - remove the "from observation" guidance and add some discussion of when to use status fields vs. additional types for allocated resources.
As per KEP kubernetes/enhancements#2527 - remove the "from observation" guidance and add some discussion of when to use status fields vs. additional types for allocated resources.
As per KEP kubernetes/enhancements#2527 - remove the "from observation" guidance and add some discussion of when to use status fields vs. additional types for allocated resources.
As per KEP kubernetes/enhancements#2527 - remove the "from observation" guidance and add some discussion of when to use status fields vs. additional types for allocated resources.
* Loosen the meaning of status in API conventions As per KEP kubernetes/enhancements#2527 - remove the "from observation" guidance and add some discussion of when to use status fields vs. additional types for allocated resources. * Backtick spec and status * Act on feedback
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 |
The Kubernetes project currently lacks enough active 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 rotten |
Looks like this one is actually done now? @thockin thoughts? |
The Kubernetes project currently lacks enough active 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. /close |
@k8s-triage-robot: Closing 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. |
Enhancement Description
The text was updated successfully, but these errors were encountered: