Publish CRD OpenAPI Schema

[roycaihw]

Enhancement Description

• One-line enhancement description (can be used as a release note): Serve validation schema for Custom Resources from kube-apiserver
• Primary contact (assignee): @roycaihw
• Responsible SIGs: SIG API Machinery
• Design proposal link (community repo):
• Link to e2e and/or unit tests:
• Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred:
  • @liggitt
  • @mbohlool
  • @sttts
• Approver (likely from SIG/area to which enhancement belongs):
  • @smarterclayton
• Enhancement target (which target equals to which milestone):
  • Alpha release target (1.14)
  • Beta release target (1.15)
  • Stable release target (1.16)

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

/sig api-machinery

1.14
KEP: https://github.com/kubernetes/enhancements/blob/master/keps/sig-api-machinery/00xx-publish-crd-openapi.md
Documentation: kubernetes/website#12910
Implementation: kubernetes/kubernetes#71192
Testing-related: kubernetes/test-infra#11618, kubernetes/kubernetes#74832

1.15
Promotion to beta: kubernetes/kubernetes#77825
Documentation: kubernetes/website#14583

1.16
Promotion to GA: kubernetes/kubernetes#81965
Documentation: kubernetes/website#15982
Bug fixes:

• DO NOT publish openapi specs containing bad types kubernetes#79587
• Fixes missing path parameter to CRD restful container kubernetes#80074
• apiextensions: ignore path conflict and resolve definition conflict when merging openapi spec kubernetes#81436

Metrics: kubernetes/kubernetes#81786

[claurence]

@liggitt @roycaihw - I see y'all are hoping to target 1.14 for this milestone - I don't see a KEP associated with this issue - was one merged already?

[spiffxp]

/milestone clear
If this is proven to have a merged KEP prior to Feb 4 we can add this back

[liggitt]

this is ongoing work described in https://github.com/kubernetes/community/blob/master/contributors/design-proposals/api-machinery/customresources-validation.md#client-side-validation

what is the desired granularity for copying that document into a KEP to unblock work on one aspect of it in this release?

[spiffxp]

I need enough to understand what the implications are from a testing and upgrade/downgrade perspective

[spiffxp]

My desire is not to expect copy-pasta from that doc into a KEP, I am OK with linking out where it makes sense.

[roycaihw]

KEP sent out at #821. It's still a draft but comments are welcome

[claurence]

@roycaihw @liggitt thanks - since we have passed enhancement freeze and want all issues targeting 1.14 to have a KEP merged by enhancements freeze this issue will require an exception for the 1.14 milestone - please submit one https://github.com/kubernetes/sig-release/blob/master/releases/EXCEPTIONS.md

[liggitt]

KEP is now implementable, exception requested at https://groups.google.com/forum/#!msg/kubernetes-milestone-burndown/QKSQVXBPeAQ/dv9Y3qsyAQAJ and acked by sig lead