Custom Resource Definition Versioning

[mbohlool]

Feature Description

• One-line feature description (can be used as a release note):

Versioning for Custom Resources including a way to plug conversion for different versions

• Primary contact (assignee):
  @mbohlool
• Responsible SIGs:
  /sig api-machinery
• Design proposal link (community repo): https://github.com/kubernetes/community/blob/master/contributors/design-proposals/api-machinery/customresources-versioning.md
  (will send a PR to community repo for this after a round of review in docs)
  (join api machinery mailing list to access)
• Link to e2e and/or unit tests: https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/apiextensions-apiserver/test/integration/versioning_test.go
• Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred:
  @sttts @nikhita
• Approver (likely from SIG/area to which feature belongs):
  @lavalamp @liggitt
• Feature target (which target equals to which milestone):
  • Alpha release target (1.12: webhooks)
  • Beta release target (1.11: only NoConversion, 1.13+ webhooks)
  • Stable release target (TBD)

[cmluciano]

@mbohlool Can you link the design doc for this when ready?

[mbohlool]

Sure, will do soon.

[sttts]

Removed the milestone. We cannot talk about realistic milestones without having a proposal out and agreed on. IMO 1.10 is not very realistic anymore.

[mbohlool]

I am going to send the proposal soon. I still hope that we can make it to 1.10.

[nikhita]

/cc @enisoc @deads2k @liggitt

[mbohlool]

The proposal is out. please take a look.

[0xmichalis]

I need permissions to read the gdoc. Why not a PR?

[idvoretskyi]

@mbohlool @k8s-mirror-api-machinery-feature-rqusts what are the feature plans for 1.11?

cc @justaugustus

[sttts]

Updated the description.

[mbohlool]

I need permissions to read the gdoc. Why not a PR?

You need to be subscribed to sig-api-machinery mailing list to see the doc but the PR is out:

kubernetes/community#2026

It only has main/approved part of the design though. If you want the history and discussion please join sig-api-machinery mailing list.

[nikhita]

This needs to be added to the v1.11 milestone.

[mdlinville]

@mbohlool please fill out the appropriate line item of the
1.11 feature tracking spreadsheet
and open a placeholder docs PR against the
release-1.11 branch
by 5/25/2018 (tomorrow as I write this) if new docs or docs changes are
needed and a relevant PR has not yet been opened.

[zparnold]

Looks like we still need some docs to get this feature ready for release @mbohlool
Could I please get some help with that? If there’s anything I can do to assist please let me know

[mbohlool]

@mistyhacks Sorry just saw your comment. Created placeholder doc PR: kubernetes/website#8834

Note that there is a documentation there but it is not finished yet.

[justaugustus]

@mbohlool I've updated the docs section of the Features spreadsheet

[mbohlool]

Main implementation PR: kubernetes/kubernetes#63830

[kacole2]

@mbohlool This feature was worked on in the previous milestone, so we'd like to check in and see if there are any plans for this to graduate stages in Kubernetes 1.12 as mentioned in your original post. This still has the 1.11 milestone as well so we need to update it accordingly.

If there are any updates, please explicitly ping @justaugustus, @kacole2, @robertsandoval, @rajendar38 to note that it is ready to be included in the Features Tracking Spreadsheet for Kubernetes 1.12.

---

Please note that the Features Freeze is July 31st, after which any incomplete Feature issues will require an Exception request to be accepted into the milestone.

In addition, please be aware of the following relevant deadlines:

• Docs deadline (open placeholder PRs): 8/21
• Test case freeze: 8/28

Please make sure all PRs for features have relevant release notes included as well.

Happy shipping!

[sttts]

@kacole2 updated the description with the 1.12 milestone. A KEP for the alpha webhook feature is being written.

[deads2k]

Let's create a dedicated issue so that we'll get the stage right. I've opened #598 to track this aspect.

[mbohlool]

Thanks @deads2k closing this one.