Enhancements: API Unions

[apelisse]

Enhancement Description

• One-line enhancement description (can be used as a release note): Allow unions/oneof semantics in API types
• Kubernetes Enhancement Proposal: (link to kubernetes/enhancements file, if none yet, link to PR): https://github.com/kubernetes/enhancements/blob/master/keps/sig-api-machinery/20190325-unions.md
• Primary contact (assignee): @apelisse
• Responsible SIGs: sig-api-machinery
• Enhancement target (which target equals to which milestone):
  
  
  
  • Alpha release target (x.y) N/A
  
  
  • Beta release target (x.y) 1.16
  
  
  • Stable release target (x.y) TBD
  
  

[apelisse]

/sig api-machinery

[kacole2]

/stage alpha
/milestone v1.15

[apelisse]

@kacole2 We're planning to release this in beta, since it's mostly a sub-feature of server-side apply (#555). Do you mind updating the label? Thanks!

[kacole2]

/stage beta

[apelisse]

Awesome thanks, I'll update the kep now to add the missing sections!

[sttts]

New sections lgtm.

[makoscafee]

Hey, @apelisse 👋 I'm the v1.15 docs Lead.
Does this enhancement require any new docs (or modifications)?

Just a friendly reminder we're looking for a PR against k/website (branch dev-1.15) due by Thursday, May 30th. It would be great if it's the start of the full documentation, but even a placeholder PR is acceptable. Let me know if you have any questions!

[apelisse]

We definitely want to add some docs, I'll open the PR soon!

[kacole2]

Hi @apelisse . Code Freeze is Thursday, May 30th 2019 @ EOD PST. All enhancements going into the release must be code-complete, including tests, and have docs PRs open.

Please list all current k/k PRs so they can be tracked going into freeze. If the PRs aren't merged by freeze, this feature will slip for the 1.15 release cycle. Only release-blocking issues and PRs will be allowed in the milestone.

If you know this will slip, please reply back and let us know. Thanks!

[apelisse]

This feature depends on server-side apply (#555) which is slipping, you can mark this for 1.16 and stop tracking :-/

[kacole2]

/milestone clear

[evillgenius75]

Hi @apelisse , I'm a 1.16 Enhancement Shadow. Is this feature going to be released in beta stage in 1.16? Please let me know so it can be added to the 1.16 Tracking Spreadsheet. If not's graduating, I will remove it from the milestone and change the tracked label.

Once coding begins or if it already has, please list all relevant k/k PRs in this issue so they can be tracked properly.

Milestone dates are Enhancement Freeze 7/30 and Code Freeze 8/29.

Thank you.

[apelisse]

I'm hoping it will, I'll let you know if we end-up falling short on this, thanks!

[kacole2]

/milestone v1.16

[sethmccombs]

Hey @apelisse

I'm one of the v1.16 docs shadows.
Does this enhancement (or the work planned for v1.16) require any new docs (or modifications to existing docs)? If not, can you please update the 1.16 Enhancement Tracker Sheet (or let me know and I’ll do so)

If so, just a friendly reminder we're looking for a PR against k/website (branch dev-1.16) due by Friday, August 23rd, it can just be a placeholder PR at this time. Let me know if you have any questions!

[apelisse]

We're dropping this for now ...
/milestone v1.17

[k8s-ci-robot]

@apelisse: You must be a member of the kubernetes/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your and have them propose you as an additional delegate for this responsibility.

In response to this:

We're dropping this for now ...
/milestone v1.17

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.

[kacole2]

/milestone v1.17

[mrbobbytables]

Hey there @apelisse -- 1.17 Enhancements lead here. I wanted to check in and see if you think this Enhancement will be graduating to beta in 1.17?

The current release schedule is:

• Monday, September 23 - Release Cycle Begins
• Tuesday, October 15, EOD PST - Enhancements Freeze
• Thursday, November 14, EOD PST - Code Freeze
• Tuesday, November 19 - Docs must be completed and reviewed
• Monday, December 9 - Kubernetes 1.17.0 Released

If you do, once coding begins please list all relevant k/k PRs in this issue so they can be tracked properly. 👍

Thanks!

[apelisse]

Thanks, I don't know yet, shrug

[palnabarun]

Hi @apelisse @shturec, just a friendly reminder. We are just 5 days away from the Enhancements Freeze.

I see that the KEP PR is still not merged and is in the provisional state.

For the KEP to be considered for 1.17,

1. KEP PR must be merged
2. KEP should be in an implementable state
3. KEP should have test plans and graduation criteria.

[mrbobbytables]

@apelisse @shturec -- Unfortunately the deadline for the 1.17 Enhancement freeze has passed. For now this is being removed from the milestone and 1.17 tracking sheet. If there is a need to get this in, please file an enhancement exception.

Thanks!

/milestone clear

[palnabarun]

Hey there @apelisse -- 1.18 Enhancements shadow here. I wanted to check in and see if you think this Enhancement will be graduating to beta in 1.18 or having a major change in its current level?

The current release schedule is:

• Monday, January 6th - Release Cycle Begins
• Tuesday, January 28th EOD PST - Enhancements Freeze
• Thursday, March 5th, EOD PST - Code Freeze
• Monday, March 16th - Docs must be completed and reviewed
• Tuesday, March 24th - Kubernetes 1.18.0 Released

If you would like to include this enhancement, once coding begins please list all relevant k/k PRs in this issue so they can be tracked properly. 👍

We'll be tracking enhancements here: http://bit.ly/k8s-1-18-enhancements

Thanks! :)

[apelisse]

Forget about this one, it's not going to happen this release :-/

[palnabarun]

Okay.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[yue9944882]

/remove-lifecycle stale

[msedzins]

Hey there @apelisse -- 1.19 Enhancements shadow here. I wanted to check in and see if you think this Enhancement will be graduating in 1.19?

In order to have this part of the release:

1. The KEP PR must be merged in an implementable state
2. The KEP must have test plans
3. The KEP must have graduation criteria.

The current release schedule is:

• Monday, April 13: Week 1 - Release cycle begins
• Tuesday, May 19: Week 6 - Enhancements Freeze
• Thursday, June 25: Week 11 - Code Freeze
• Thursday, July 9: Week 14 - Docs must be completed and reviewed
• Tuesday, August 4: Week 17 - Kubernetes v1.19.0 released

If you do, I'll add it to the 1.19 tracking sheet (http://bit.ly/k8s-1-19-enhancements). Once coding begins please list all relevant k/k PRs in this issue so they can be tracked properly. 👍

Thanks!

[apelisse]

Hi there, we're not planning on promoting this feature this cycle, thank you!

[msedzins]

Thank you for letting me know @apelisse

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[apelisse]

/remove-lifecycle stale

[kikisdeliveryservice]

Hi @apelisse

Enhancements Lead here. Any plans for this in 1.20?

Thanks!
Kirsten

[apelisse]

Nope :-/