kubectl return code normalization

[rikatz]

Enhancement Description

• One-line enhancement description (can be used as a release note): Normalize the return codes issued by kubectl when an error occurs (and also when we have success)
• Kubernetes Enhancement Proposal: NONE YET
• Discussion Link: Discussed on sig-cli bug scrub of 3rd of March of 2021 https://www.youtube.com/watch?v=EWxJiZXZD08 49:39
• Primary contact (assignee): @rikatz
• Responsible SIGs: CLI
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.22
  • Beta release target (x.y): 1.23
  • Stable release target (x.y): 1.24
• [ ] Alpha
  • [ ] KEP (k/enhancements) update PR(s):
  • [ ] Code (k/k) update PR(s):
  • [ ] Docs (k/website) update PR(s):

[rikatz]

/assign @rikatz /sig cli

[JamesLaverack]

/stage alpha /milestone v1.22

[soltysh]

@JamesLaverack this isn't something SIG-CLI is planning to track for 1.22, we will be working on it, but we're more in the gather input phase than closer to alpha implementation.

[supriya-premkumar]

/milestone remove

[k8s-ci-robot]

@supriya-premkumar: The provided milestone is not valid for this repository. Milestones in this repository: [keps-beta, keps-ga, v1.17, v1.18, v1.19, v1.20, v1.21, v1.22, v1.23, v1.25]

Use /milestone clear to clear the milestone.

In response to [this](https://github.com/kubernetes/enhancements/issues/2551#issuecomment-838806217): >/milestone remove Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[supriya-premkumar]

/milestone clear

[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

[rikatz]

/remove-lifecycle stale /lifecycle active

[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

[soltysh]

/remove-lifecycle stale /lifecycle frozen

[rikatz]

@eddiezane @soltysh let me see if someone here at company wants to help me on this, so I can sort of mentor/help/whatever but someone can do the heavy job!

Maybe we can get an alpha proposal for this in v1.24

[hosseinsalahi]

Hello @rikatz

v1.24 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00pm PT on Thursday Feb 3rd, 2022. This enhancement is targeting alpha for v1.24,

Here’s where this enhancement currently stands:

• [X] Updated KEP file using the latest template has been merged into the k/enhancements repo.
• [X] KEP status is marked as implementable for this release
• [X] KEP has a test plan section filled out.
• [X] KEP has up to date graduation criteria.
• [X] KEP has a production readiness review that has been completed and merged into k/enhancements.

The status of this enhancement is marked as tracked. Please keep the issue description and the targeted stage up-to-date for release v1.24. Thanks!

[johnbelamaric]

Any updates here? Any PR?

nm, I see it

[soltysh]

/reopen this is still worked on

[k8s-ci-robot]

@soltysh: Reopened this issue.

In response to [this](https://github.com/kubernetes/enhancements/issues/2551#issuecomment-1028915526): >/reopen >this is still worked on Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[chrisnegus]

Hi @rikatz 👋 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!

[soltysh]

Hey @chrisnegus I must have marked this feature prematurely as needs docs, since we're still very early and not much of this work will be visible to users. Is there a way we could remove that needs docs for now?

[chrisnegus]

Thanks @soltysh ! I've moved the KEP to our "No Docs Required" column.

[hosseinsalahi]

Hello @rikatz

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:

• [X] All PRs to the Kubernetes repo that are related to your enhancement are merged by the code freeze deadline.
• [X] Have a documentation placeholder PR open by 18:00 PDT, Thursday, March 31, 2022.

For note, the status of this enhancement is currently marked as tracked. Thank you!

[katcosgrove]

Hey y'all! We're approaching last call for feature blogs, as the freeze is Wednesday, March 23. If you would like to have a feature blog for this, please add it to the tracking sheet and reach out to me if you have any questions. Thank you!

[ah8ad3]

I've read the kep and i'm interested on starting this, but i need some sort of help/mentoring. @rikatz @soltysh