-
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
Kubeadm machine/structured output #1053
Comments
@akutz Enhancement Freeze for Kubernetes 1.15 has passed and this did not meet the deadline. If there is a need for this to be in 1.15, please file an Enhancement Exception. Thank you. |
Hi @kacole2, We are discussing this during today's kubeadm call, and I'll ask for people's thoughts on that there. Thank you! |
Per discussion we're gunna hold for 1.15 and try to settle on the KEP for implementation in 1.16. |
/stage alpha Hi @akutz, I'm the 1.16 Enhancement Lead. I've added this to the 1.16 Tracking Spreadsheet. As a reminder, every enhancement requires a KEP in an implementable state with Graduation Criteria explaining each alpha/beta/stable stages requirements. Milestone dates are Enhancement Freeze 7/30 and Code Freeze 8/29. |
I'm planning to finish this POC kubernetes/kubernetes#78764 |
I'd like to manage the PoC via the KEP, but I'm also happy to transfer ownership of the KEP to @bart0sh as I'm now engaged in another activity that doesn't leave me a lot of time for the KEP. |
@neolit123 @kacole2, if I'm not wrong, this issue should be set to tracked yes |
updated -> tracked/yes. |
@akutz @neolit123 @fabriziopandini -- One of the 1.16 enhancement shadows here -- Just as a friendly reminder that the KEP itself must be in an Thanks! |
thanks for the heads up @mrbobbytables
sent PR for that:
updated. |
/remove-lifecycle stale |
Hi @neolit123 Enhancements Lead here. Any plans for this in 1.20? Thanks! |
Likely, no. Will update here if we change our plans.
|
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
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. |
/remove-lifecycle stale |
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. |
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 |
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 |
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 |
tracking issue following the new format is here: |
Enhancement Description
/sig cluster-lifecycle
cc @bart0sh
The text was updated successfully, but these errors were encountered: