kubeadm: machine readable output

[shekhar-rajak]

Enhancement Description

• One-line enhancement description (can be used as a release note): kubeadm-machine-output
• Kubernetes Enhancement Proposal:

https://github.com/kubernetes/enhancements/tree/master/keps/sig-cluster-lifecycle/kubeadm/2504-kubeadm-machine-output

Summary

Kubeadm should support structured output, such as JSON, YAML, or a Go template.

Motivation

While Kubernetes may be deployed manually, the de facto, if not de jure, means of turning up a Kubernetes cluster is kubeadm. Popular systems management software, such as Terraform, rely on kubeadm in order to deploy Kubernetes. Planned enhancements to the Cluster API project include a composable package for bootstrapping Kubernetes with kubeadm and cloud-init.

Without structured output, even the most seemingly innocuous changes could break Terraform, Cluster API, or other software that relies on the results of kubeadm.

• Discussion Link:
• Primary contact (assignee): @bart0sh
• Responsible SIGs:
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.17
  • Beta release target (x.y): TODO
  • Stable release target (x.y): TODO
• Alpha
  • Code (k/k) update PR(s):
    • Structured output for 'kubeadm token list' kubernetes#78764
    • Kubeadm upgrade plan support json/yaml output kubernetes#108447
      • Replace fmt.Print with printer in upgrade plan code and fix configVersions are not printed when output is json or yaml kubernetes#123492
      • fix bug kubeadm: fix upgrade plan json/yaml output. introduce v1alpha3 changes kubernetes#123461
    • kubeadm certs check-expiration support json/yaml output kubernetes#123372

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

k/kubeadm tracking issue:
kubernetes/kubeadm#494

[shekhar-rajak]

Migrating all the old template keps to new template : #2499

[fejta-bot]

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

[neolit123]

/remove-lifecycle stale

[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

[neolit123]

/remove-lifecycle stale

[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

[k8s-triage-robot]

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:

• 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 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 rotten

[neolit123]

/remove-lifecycle rotten

[pacoxu]

If this is still needed, I may help to pick kubernetes/kubernetes#83941 up.

[neolit123]

Let me know if you have any Qs. 'Upgrade plan' output was desired, but i haven't looked at this for a while.

…

On Feb 17, 2022 07:18, "Paco Xu" ***@***.***> wrote: If this is still needed, I may help to pick kubernetes/kubernetes#83941 <kubernetes/kubernetes#83941> up. — Reply to this email directly, view it on GitHub <#2504 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACRATDMTX7SER5J7DW2HKLU3SAJVANCNFSM4XREIJHA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you commented.Message ID: ***@***.***>

[pacoxu]

/assign
I will have a try this week or next.

[pacoxu]

kubernetes/kubernetes#108447 was merged in v1.25