Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Kubeadm machine/structured output #1053

Closed
akutz opened this issue May 8, 2019 · 55 comments
Closed

Kubeadm machine/structured output #1053

akutz opened this issue May 8, 2019 · 55 comments
Assignees
@neolit123 @bart0sh
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team

Comments

@akutz
Copy link
Member

akutz commented May 8, 2019 •
edited by neolit123

Enhancement Description

/sig cluster-lifecycle

cc @bart0sh
@k8s-ci-robot k8s-ci-robot added needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels May 8, 2019
@kacole2
Copy link
Contributor

kacole2 commented May 8, 2019

@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.

@kacole2 kacole2 added the tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team label May 8, 2019
@akutz
Copy link
Member Author

akutz commented May 8, 2019

Hi @kacole2,

We are discussing this during today's kubeadm call, and I'll ask for people's thoughts on that there. Thank you!

@neolit123 neolit123 self-assigned this May 8, 2019
@akutz akutz mentioned this issue May 8, 2019
Merged
@timothysc
Copy link
Member

Per discussion we're gunna hold for 1.15 and try to settle on the KEP for implementation in 1.16.

@timothysc timothysc added this to the v1.16 milestone May 9, 2019
@akutz akutz mentioned this issue May 20, 2019
Closed
5 tasks
@kacole2
Copy link
Contributor

kacole2 commented Jul 9, 2019

/stage alpha
/milestone v1.16

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.

@k8s-ci-robot k8s-ci-robot added the stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status label Jul 9, 2019
@kacole2 kacole2 added tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team and removed tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team labels Jul 9, 2019
@neolit123
Copy link
Member

@akutz @bart0sh would you have bandwidth for this in 1.16?
let me know so that we can update the tracking.

@neolit123 neolit123 added tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team and removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels Jul 16, 2019
@neolit123 neolit123 removed this from the v1.16 milestone Jul 16, 2019
@bart0sh
Copy link
Contributor

bart0sh commented Jul 17, 2019

I'm planning to finish this POC kubernetes/kubernetes#78764
We need to decide what to do with the KEP though.

@akutz
Copy link
Member Author

akutz commented Jul 17, 2019

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.

@fabriziopandini
Copy link
Member

@neolit123 @kacole2, if I'm not wrong, this issue should be set to tracked yes
/kind feature

@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Jul 30, 2019
@neolit123 neolit123 added tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team and removed tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team labels Jul 30, 2019
@neolit123
Copy link
Member

updated -> tracked/yes.

@mrbobbytables
Copy link
Member

@akutz @neolit123 @fabriziopandini -- One of the 1.16 enhancement shadows here -- Just as a friendly reminder that the KEP itself must be in an Implementable state by EOD today. It'd also be helpful to update the original issue with links to the KEP directly now that it has been merged.

Thanks!

@neolit123 neolit123 mentioned this issue Jul 30, 2019
Closed
@neolit123
Copy link
Member

thanks for the heads up @mrbobbytables

One of the 1.16 enhancement shadows here -- Just as a friendly reminder that the KEP itself must be in an Implementable

sent PR for that:
#1188

It'd also be helpful to update the original issue with links to the KEP directly now that it has been merged.

updated.

@neolit123 neolit123 added this to the v1.16 milestone Jul 30, 2019
@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 2, 2020
@fabriziopandini
Copy link
Member

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 3, 2020
@kikisdeliveryservice
Copy link
Member

Hi @neolit123

Enhancements Lead here. Any plans for this in 1.20?

Thanks!
Kirsten

@neolit123
Copy link
Member

neolit123 commented Sep 14, 2020 via email

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 13, 2020
@fabriziopandini
Copy link
Member

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 14, 2020
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 14, 2021
@wilmardo
Copy link

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 15, 2021
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 13, 2021
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jul 13, 2021
@wilmardo
Copy link

/remove-lifecycle rotten

@k8s-ci-robot k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Jul 13, 2021
@k8s-triage-robot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 11, 2021
@fabriziopandini
Copy link
Member

/remove-lifecycle stale
As far as I know @neolit123 is reviving part of this work (or at least improving some implementation details)

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 11, 2021
@k8s-triage-robot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 9, 2022
@neolit123 neolit123 added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 10, 2022
@neolit123
Copy link
Member

tracking issue following the new format is here:
#2504

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@neolit123 neolit123

@bart0sh bart0sh

Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests