Separate kubectl user preferences from cluster configs

[eddiezane]

Enhancement Description

• One-line enhancement description (can be used as a release note): Implement a .kuberc file to separate user preferences from cluster configs.
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/blob/master/keps/sig-cli/3104-introduce-kuberc/README.md
• Discussion Link: https://groups.google.com/g/kubernetes-dev/c/y4Q20V3dyOk/m/ozSUR3dJDQAJ
• Primary contact (assignee): @ardaguclu @soltysh
• Responsible SIGs: cli
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.33
  • Beta release target (x.y): 1.34
  • Stable release target (x.y):
• Alpha
  • KEP (k/enhancements) update PR(s):
    • KEP-3104: Introduce kuberc #3392
    • KEP-3104: Introduce kuberc - update for 1.31 #4705
    • KEP-3104: Update latest milestone to 1.32 #4860
    • Update kuberc example with finalized version #4925
  • Code (k/k) update PR(s): Introduce kuberc as new flag to customize defaulting and define aliases in kubectl kubernetes#125230
  • Docs (k/website) update PR(s):
    • Add KUBECTL_KUBERC environment variable description website#49722
• Beta
  • KEP (k/enhancements) update PR(s): KEP-3104: promote kuberc to beta #5300
  • Code (k/k) update PR(s):
    • Continue alias creation when __completion is used to enable completion kubernetes#131586
    • Manually read verbosity before kubectl command construction kubernetes#131668
    • Promote kuberc to beta kubernetes#131619 replaced with Promote kuberc to beta kubernetes#131818
    • Deprecate kubeconfig's preference field in favor of kuberc kubernetes#131741
    • Add e2e tests for kuberc kubernetes#131757
    • kuberc: add tests for DefaultGetPreferences kubernetes#132055
    • kuberc: additional tests kubernetes#132347
  • Docs (k/website) update(s):
    • Add config API for kuberc v1alpha1 website#50961
    • Add documents for kuberc website#50913
    • [KEP-3104] Kuberc beta website#51351
    • Add config API for kuberc v1beta1 kubernetes-sigs/reference-docs#396

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

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

/milestone v1.25
/stage alpha

[jasonbraganza]

Hello @eddiezane 👋, 1.25 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PST on Thursday June 23, 2022.

For note, This enhancement is targeting for stage alpha for 1.25 (correct me, if otherwise)

Here's where this enhancement currently stands:

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

Looks like for this one, we would need to update the following in the open PR #3392:

• Please update the status from provisional to implementable in the kep.yaml file
• Add a PRR approval file for stage alpha
• Please update the Test Plan and the Graduation Criteria sections in the README.md with details as appropriate.

For note, the status of this enhancement is marked as at risk. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

[jasonbraganza]

Hello @eddiezane 👋🏿 Just checking in, as we are four days away from the enhancements freeze on Thursday, June 23, 2022 at 18:00 PM PT.

Please get the open PR #3392 merged with the suggestions in the previous comment

Please note: the current status of the enhancement is at-risk.
Thank you.