kubectl binary plugins

[fabianofranz]

Feature Description

• One-line feature description (can be used as a release note): Plugins to allow extending the set of commands provided by the main kubectl binary.
• Primary contact (assignee): @fabianofranz
• Responsible SIGs: @kubernetes/sig-cli-feature-requests
• Design proposal link (community repo):
  • Initial Proposal
  • Detailed proposal with milestones
• Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred: @monopole @pwittrock @adohe @droot @deads2k @soltysh @smarterclayton
• Approver (likely from SIG/area to which feature belongs): @fabianofranz
• Feature target (which target equals to which milestone):
  • Alpha release target (1.8)
  • Beta release target (1.9)
  • Stable release target (1.10)

[fabianofranz]

Initial support already added in 1.7 by kubernetes/kubernetes#37499, and a couple subsequent PR's that fixed issues and added other minor features.

[fabianofranz]

/sig cli

[fabianofranz]

Discussed and agreed by the SIG-CLI group on July 19.

[pwittrock]

@fabianofranz Is there anything worth adding to the release notes for 1.8 on this?

[fabianofranz]

@pwittrock not for 1.8 since the most important things already got release notes in prior releases. We'll likely have more notes for upcoming releases, while plugins progresses from alpha.

[idvoretskyi]

@fabianofranz should this feature still be on track for 1.8?

[fabianofranz]

@idvoretskyi yes, it's still on track and all code PR's merged before code freeze. I just opened a docs PR.

[pwittrock]

@fabianofranz Excellent. Once those are merged should we mark this as closed, and open a new one for 1.9?

[fabianofranz]

Docs PR merged for this feature.

@idvoretskyi what's the process here, do we just close this issue since it's all done (PR merged before code freeze, docs merged, release notes updated)?

[idvoretskyi]

@fabianofranz if you are expecting to make a progress with the feature for the next releases, please keep it open.

Only the milestone (and stage/* label) should be updated after the next release train will go.

[fabianofranz]

@idvoretskyi thanks!

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

Prevent issues from auto-closing with an /lifecycle frozen comment.

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

[fejta-bot]

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-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

[tamalsaha]

@fabianofranz @pwittrock what are the plans for graduating kubectl plugin to beta? Is there an issue to follow?

[fabiand]

One thing I noticed creating a plugin for KubeVirt is that it would be handy to get the cluster credentials and additional stuff (i.e. cluster api sevrer uri) passed as env variables. Is this being done today?

[deads2k]

@fabianofranz @pwittrock what are the plans for graduating kubectl plugin to beta? Is there an issue to follow?

@soltysh @adohe it may be worth considering experiences here. I've seen pulls going by that make the registration process look a little weird. I suspect the attempt was to "make it easy", but may have accidentally produces additional, unnecessary work for implementors

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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