Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom Resource Definition Versioning #544

Closed
mbohlool opened this issue Jan 19, 2018 · 20 comments
Closed

Custom Resource Definition Versioning #544

mbohlool opened this issue Jan 19, 2018 · 20 comments
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. stage/beta Denotes an issue tracking an enhancement targeted for Beta status
Milestone

Comments

@mbohlool
Copy link
Contributor

mbohlool commented Jan 19, 2018

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

@mbohlool mbohlool self-assigned this Jan 19, 2018
@k8s-ci-robot k8s-ci-robot added the sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. label Jan 19, 2018
@mbohlool mbohlool added the kind/feature Categorizes issue or PR as related to a new feature. label Jan 19, 2018
@idvoretskyi idvoretskyi added this to the v1.10 milestone Jan 22, 2018
@idvoretskyi idvoretskyi added the stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status label Jan 22, 2018
@cmluciano
Copy link

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

@mbohlool
Copy link
Contributor Author

Sure, will do soon.

@sttts sttts removed this from the v1.10 milestone Jan 23, 2018
@sttts
Copy link
Contributor

sttts commented Jan 23, 2018

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
Copy link
Contributor Author

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

@nikhita
Copy link
Member

nikhita commented Jan 24, 2018

/cc @enisoc @deads2k @liggitt

@mbohlool
Copy link
Contributor Author

The proposal is out. please take a look.

@0xmichalis
Copy link

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

@idvoretskyi
Copy link
Member

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

cc @justaugustus

@sttts
Copy link
Contributor

sttts commented Apr 12, 2018

Updated the description.

@mbohlool
Copy link
Contributor Author

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
Copy link
Member

nikhita commented Apr 17, 2018

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

@mdlinville
Copy link

@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
Copy link
Member

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
Copy link
Contributor Author

@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
Copy link
Member

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

@mbohlool
Copy link
Contributor Author

mbohlool commented Jun 7, 2018

Main implementation PR: kubernetes/kubernetes#63830

@justaugustus justaugustus added stage/beta Denotes an issue tracking an enhancement targeted for Beta status and removed stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status labels Jun 8, 2018
@justaugustus justaugustus removed the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Jul 18, 2018
@kacole2
Copy link

kacole2 commented Jul 23, 2018

@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
Copy link
Contributor

sttts commented Jul 24, 2018

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

@deads2k
Copy link
Contributor

deads2k commented Jul 30, 2018

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

@mbohlool
Copy link
Contributor Author

Thanks @deads2k closing this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. stage/beta Denotes an issue tracking an enhancement targeted for Beta status
Projects
None yet
Development

No branches or pull requests