OpenAPI v3 for kubectl explain

[alexzielenski]

Enhancement Description

• One-line enhancement description (can be used as a release note): Changes kubectl explain to use OpenAPI v3 data instead of OpenAPI v2.
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-cli/3515-kubectl-explain-openapiv3
• Discussion Link: https://youtu.be/3Xnb0R_ios4?t=1512
• Primary contact (assignee): @soltysh @alexzielenski
• Responsible SIGs: sig-cli
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.26
  • Beta release target (x.y): 1.27
  • Stable release target (x.y):
• Alpha
  • KEP (k/enhancements) update PR(s): KEP-3515: add new kep kubectl explain openapi v3 upgrade #3516
  • Code (k/k) update PR(s):
    1. kubectl explain openapiv3 template foundations kubernetes#113024
    2. kubectl explain --output plaintext kubernetes#113146
  • Docs (k/website) update PR(s): document kubectl explain openapi v3 website#37788
• Beta
  • KEP (k/enhancements) update PR(s):
    • KEP-3515: kubectl explain openapiv3 - beta graduation criteria #3748
  • Code (k/k) update PR(s):
    • kubectl-explain: add --output plaintext-openapiv2 fallback kubernetes#115480
    • kubectl explain: use openapiv3 by default kubernetes#116390
  • Docs (k/website) update(s):
    • Update kubectl docs/Explain beta docs website#40068

[kikisdeliveryservice]

@alexzielenski please provide a Discussion Link. It is required that you "link to SIG mailing list thread, meeting, or recording where the Enhancement was discussed before KEP creation"

[rhockenbury]

/milestone v1.26
/label tracked/yes

[rhockenbury]

Hello @alexzielenski 👋, 1.26 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PDT on Thursday 6th October 2022.

This enhancement is targeting for stage alpha for 1.26 (correct me, if otherwise)

Here's where this enhancement currently stands:

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

For this KEP, we would just need to get #3516 merged up to meet the requirements.

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!

[alexzielenski]

@rhockenbury The PR has been merged with PRR and I think satisfies the checklist. Please let me know if there is anything left to do!