OpenAPI v3

[Jefftree]

Enhancement Description

• One-line enhancement description (can be used as a release note): Publish OpenAPI v3 spec for both built-ins, CRDs, and APIService types.
• Kubernetes Enhancement Proposal: TBD
• Discussion Link:
• Primary contact (assignee): @Jefftree
• Responsible SIGs: api-machinery
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.23
  • Beta release target (x.y): 1.24
  • Stable release target (x.y): 1.27
• Alpha
  • KEP (k/enhancements) update PR(s): KEP-2896: OpenAPI V3 #2898
  • Code (k/k) update PR(s): Support for OpenAPI v3 kube-openapi#247 OpenAPI v3 kubernetes#105945
  • Docs (k/website) update PR(s): Docs for OpenAPI v3 website#30534
• Beta
  • KEP (k/enhancements) update PR(s):
  • Code (k/k) update PR(s):
  • Docs (k/website) update(s):
• Stable
  • KEP (k/enhancements) update PR(s): KEP-2896: OpenAPI V3 to GA #3773
  • Code (k/k) update PR(s):
    • remove mime AddExtensionType in discovery test kubernetes#114290
    • Add OpenAPI V3 E2E Tests kubernetes#116200
    • Promote OpenAPI V3 to GA kubernetes#116235
    • Update kube-openapi to afdc3dddf62d31f5e3868d699379c571a6007920 kubernetes#116162
    • update SSA to use OpenAPIV3 for builtin and CRD models kubernetes#115324
  • Docs (k/website) update(s): Doc update for KEP-2896 OpenAPIV3 website#40027
  • Blog: Blog post for KEP-2896 and KEP-2885 website#39844

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

[Jefftree]

/sig api-machinery

[kevindelgado]

Hi @Jefftree! 1.23 Enhancements team here. Just checking in as we approach enhancements freeze on Thursday 09/09. 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 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 just need the KEP & the PRR file to merge by enhancements freeze :)

All good now!

Thanks!

[kevindelgado]

/milestone v1.23
/stage alpha

[kevindelgado]

Hi @Jefftree

Ping! As a reminder your PR (#2898) needs to merge by EOD PST tomorrow September 9th to be included in the 1.23 Release. After that time you will need to request an exception.

Lmk if you need anything,
Kevin

[mehabhalodiya]

Hi @Jefftree 👋 1.23 Docs shadow here.

This enhancement is marked as 'Needs Docs' for the 1.23 release.

Please follow the steps detailed in the documentation to open a PR against the dev-1.23 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thu November 18, 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!

[kevindelgado]

Hi @Jefftree 👋

Checking in once more as we approach 1.23 code freeze at 6:00 pm PST on Tuesday, November 16.

Please ensure the following items are completed:

• All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• All PRs are fully merged by the code freeze deadline.
• Have a documentation placeholder PR open by Thursday, November 18.

As always, we are here to help should questions come up.

Thanks!!