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!!

[salaxander]

/milestone v1.24
/stage beta

[salaxander]

Hi @Jefftree!. Just checking in as we approach 1.24 enhancements freeze on Thursday 02/03. 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.

I see #3167 address all of the items that aren't complete, so once that merges we're all good.
Thanks!

[gracenng]

All good for 1.24 Enhancements Release

[mehabhalodiya]

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

[gracenng]

Hi @Jefftree 1.24 Enhancements Team here,

With Code Freeze approaching on 18:00 PDT Tuesday March 29th 2022, the enhancement status is at risk as there is no linked k/k PR. Kindly list them in this issue. Thanks!

[mehabhalodiya]

Hi, @Jefftree, since this KEP now made the code freeze, please open a docs placeholder PR. Thank you!

[deads2k]

/milestone v1.27
/label lead-opted-in
/stage stable

[Atharva-Shinde]

Hello @Jefftree 👋, Enhancements team here.

Just checking in as we approach Enhancements freeze on 18:00 PDT Thursday 9th February 2023.

This enhancement is targeting for stage stable for 1.27 (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.27
• 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 update the following:

• Update it's test plan section to be in compliance with the latest KEP readme template
• Add response for this question in the Scalability questionnaire of the KEP readme

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!

[Jefftree]

@Atharva-Shinde Updated the missing parts from the latest KEP template. PTAL thanks!

[Atharva-Shinde]

Thanks @Jefftree, with all the KEP requirements in place and merged into k/enhancements, this enhancement is all good for the upcoming enhancements freeze. 🚀

The status of this enhancement is marked as tracked. Please keep the issue description up-to-date with appropriate stages as well :)

[taniaduggal]

Hi @Jefftree 👋 , I’m reaching out from the 1.27 Release Docs team. This enhancement is marked as ‘Needs Docs’ for the 1.27 release.
Please follow the steps detailed in the documentation to open a PR against dev-1.27 branch in the k/website repo. This PR can be just a placeholder at this time, and must be created by March 16. For more information, please take a look at Documenting for a release to familiarize yourself with the documentation requirements for the release.
Please feel free to reach out with any questions. Thanks!

[Atharva-Shinde]

Hey again @Jefftree 👋 Enhancements team here,
Just checking in as we approach 1.27 code freeze at 17:00 PDT on Tuesday 14th March 2023.

Here's where this enhancement currently stands:

• All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• All PR/s are fully merged by the code freeze deadline.
  • 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

Also please let me know if there are other PRs in k/k we should be tracking for this KEP.
As always, we are here to help if any questions come up. Thanks!

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.