Enhancements: Immutable Fields API

[apelisse]

Enhancement Description

• One-line enhancement description (can be used as a release note): Ability to mark fields as immutable in APIs with automatic verification.
• Kubernetes Enhancement Proposal: (link to kubernetes/enhancements file, if none yet, link to PR): https://github.com/kubernetes/enhancements/pull/1265
• 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) 1.18
  
  

[apelisse]

/sig api-machinery

[kacole2]

@apelisse is this going to go straight to Beta in 1.16?

/milestone v1.16
/stage beta

[kacole2]

@apelisse this is a reminder that Enhancement Freeze is tomorrow and this KEP #1099 needs to be merged by EOD. If not, it will be removed from the milestone. Thanks

[apelisse]

Thanks for the reminder Kendrick, work is actually going-on (https://github.com/apelisse/enhancements/pull/1) and mostly driven by @sttts
We'll try to mark it implementable before tomorrow!

[kacole2]

@apelisse @sttts

Enhancement Freeze has passed for 1.16. The KEP at #1099 was never merged and now this is being removed from the 1.16 milestone. If this would like to be re-added, please file an exception and it will require approval from the release lead.

/milestone clear

[apelisse]

Thanks Kendrick, we've decided to take our time and do it well! We're planning to do it for the next release

[palnabarun]

Hey there @apelisse , 1.17 Enhancements shadow here. I wanted to check in and see if you think this Enhancement will be graduating to alpha/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, I'll add it to the 1.17 tracking sheet (https://bit.ly/k8s117-enhancement-tracking). Once coding begins please list all relevant k/k PRs in this issue so they can be tracked properly. 👍

Thanks!

[sttts]

Yes, please add it to the tracking sheet. We are on it.

[palnabarun]

Awesome. :tada:

Just FYI, for the enhancement to be accepted into the release:

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

/milestone v1.17

[palnabarun]

Hi @sttts @apelisse , 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.

[palnabarun]

@sttts @apelisse -- Unfortunately the deadline for the 1.17 Enhancement freeze has passed and the KEP is still not merged and in the provisional state. 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.

[palnabarun]

/milestone clear

[palnabarun]

@stts @apelisse Since, the exception request filed here was accepted, I'm adding back the enhancement to the tracking sheet.

[palnabarun]

/milestone v1.17

[palnabarun]

@apelisse I see that #1099 has been succeeded by #1265. Can you please update the issue description? :)

PS: I have updated the same information in the tracking sheet.

[apelisse]

Done!

[daminisatya]

Hello, @apelisse, I'm 1.17 docs lead.

Does this enhancement (or the work planned for v1.17) require any new docs (or modifications to existing docs)? If not, can you please update the 1.17 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.17) due by Friday, November 8th, it can just be a placeholder PR at this time. Let me know if you have any questions!

[apelisse]

Yeah, we'll have to document that, I've created an empty PR: https://github.com/kubernetes/website/pull/17316

[daminisatya]

Thank you @apelisse

[palnabarun]

Hi @apelisse

I am one of the Enhancements Shadow for the 1.17 Release Team. We are very near to the Code Freeze (Nov 14th) for this release cycle. Just checking in about the progress of this enhancement. Can you please link the PR's related to this enhancement here?

Thank you in advance :smile:

[palnabarun]

/cc @sttts (as per offline discussion with @apelisse)

[palnabarun]

/assign @sttts @apelisse

[palnabarun]

Hi @apelisse @sttts , tomorrow is code freeze for the 1.17 release cycle. Can you please link the k/k PR's related to this enhancement? We're flagging as the enhancement as At Risk in the 1.17 Enhancement Tracking Sheet.

Do you think they will be merged by the EoD of the 14th (Thursday)? After that point, only release-blocking issues and PRs will be allowed in the milestone with an exception.

[palnabarun]

Hi @apelisse @stts, Code Freeze is into effect now. I am Removing this enhancement from the 1.17 milestone.

Please feel free to raise an exception if you want to get it into this milestone.

[palnabarun]

/milestone clear

[jeremyrickard]

Hi @apelisse @sttts ,

1.18 enhancements team reaching out 👋

It looks like the PR that didn't make code freeze for 1.17 has merged. Are you planning on including this in the 1.18 release?

Thanks!

[apelisse]

I think we do. We need to talk about what's left to be done. I think you can track it for now, we'll let you know if we can't make it.

[jeremyrickard]

/milestone v1.18

[apelisse]

No plan for 1.18, you can stop tracking and move it to 1.19 :-/

[jeremyrickard]

Thanks for the update @apelisse

[jeremyrickard]

/milestone v1.19

[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

[palnabarun]

/remove-lifecycle stale

[palnabarun]

Hi @apelisse -- 1.19 Enhancements Lead here, I wanted to check in if you think this enhancement would graduate in 1.19?

---

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

[apelisse]

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

[palnabarun]

Thank you @apelisse for the update. I will update the tracking sheet accordingly. :+1:

[palnabarun]

/milestone clear

[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

[sttts]

/remove-lifecycle stale

[kikisdeliveryservice]

Hi @apelisse

Enhancements Lead here. Any plans for this in 1.20?

Thanks!
Kirsten

[apelisse]

Hopefully next release