search

kubernetes / enhancements

Enhancements tracking repo for Kubernetes
Apache License 2.0
3.44k stars 1.49k forks source link

Unknown Version Interoperability Proxy #4020

Open richabanker opened 1 year ago

richabanker commented 1 year ago

Enhancement Description

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

richabanker commented 1 year ago

/sig api-machinery

deads2k commented 1 year ago

/milestone v1.28 /label lead-opted-in

Atharva-Shinde commented 1 year ago

/stage alpha

ruheenaansari34 commented 1 year ago

Hello @Richabanker šŸ‘‹, 1.28 Enhancements team here.

Just checking in as we approach enhancements freeze on 1:00 UTC on Friday 16th June 2023.

This enhancement is targeting for stage alpha for 1.28 (correct me, if otherwise)

Here's where this enhancement currently stands:

For this KEP, we would need to take care of:

The status of this enhancement is marked as at risk. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

Atharva-Shinde commented 1 year ago

Hey @Richabanker With all the KEP requirements in place and merged into k/enhancements, this enhancement is all good for the upcoming enhancements freeze. šŸš€

The status of this enhancement is marked as tracked. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

AdminTurnedDevOps commented 1 year ago

Hey @Richabanker

1.28 Docs Shadow here.

Does this enhancement work planned for 1.28 require any new docs or modification to existing docs?

If so, please follows the steps here to open a PR against dev-1.28 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday 20th July 2023.

Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.

Thank you!

richabanker commented 1 year ago

Thanks @AdminTurnedDevOps, added a placeholder PR https://github.com/kubernetes/website/pull/41723

Edit: modified above PR to a blog PR, and created a new documentation PR here https://github.com/kubernetes/website/pull/42147

ruheenaansari34 commented 1 year ago

Hey again @Richabanker šŸ‘‹ Just checking in as we approach Code freeze at 01:00 UTC Friday, 19th July 2023.

I don't see any code (k/k) update PR(s) in the issue description so if there are any k/k related PR(s) that we should be tracking for this KEP please link them in the issue description above.

As always, we are here to help if any questions come up. Thanks!

richabanker commented 1 year ago

Hi @ruheenaansari34, thanks for the reminder. Updated the issue description.

richabanker commented 1 year ago

All code update PRs are merged for this feature.

Atharva-Shinde commented 1 year ago

Hey @Richabanker šŸ‘‹ Enhancements Lead here, With https://github.com/kubernetes/kubernetes/pull/118386, https://github.com/kubernetes/kubernetes/pull/119272 and https://github.com/kubernetes/kubernetes/pull/117740 merged as per the issue description, this enhancement is now tracked for v1.28 Code Freeze! Thanks

Rishit-dagli commented 1 year ago

Hello @Richabanker wave: please take a look at Documenting for a release - PR Ready for Review to get your docs PR ready for review before Tuesday 25th July 2023. Thank you!

Ref: https://github.com/kubernetes/website/pull/41723

Ritikaa96 commented 1 year ago

I get the name was changed as per discussion here Will the feature gate: UnknownVersionInteroperabilityProxy be renamed as well?

richabanker commented 1 year ago

I get the name was changed as per discussion here Will the feature gate: UnknownVersionInteroperabilityProxy be renamed as well?

I would prefer consistency across docs and code, so I think we should change the feature gate name as well. But since its code freeze right now, that change can happen after the freeze is lifted. @jpbetz what are your thoughts on this?

jpbetz commented 1 year ago

I get the name was changed as per discussion here Will the feature gate: UnknownVersionInteroperabilityProxy be renamed as well?

I would prefer consistency across docs and code, so I think we should change the feature gate name as well. But since its code freeze right now, that change can happen after the freeze is lifted. Joe Betz what are your thoughts on this?

I would also prefer the consistency.

But once 1.28.0 is published, we're forever stuck with the name for the 1.28 minor version. I'm also not convinced that renaming it to a more consistent name in 1.29 is a net benefit to users.

This ship may have already sailed.

Ritikaa96 commented 1 year ago

I get the name was changed as per discussion here Will the feature gate: UnknownVersionInteroperabilityProxy be renamed as well?

I would prefer consistency across docs and code, so I think we should change the feature gate name as well. But since its code freeze right now, that change can happen after the freeze is lifted. Joe Betz what are your thoughts on this?

I would also prefer consistency.

But once 1.28.0 is published, we're forever stuck with the name for the 1.28 minor version. I'm also not convinced that renaming it to a more consistent name in 1.29 is a net benefit to users.

This ship may have already sailed.

Noted. FWIW if the feature gate and feature name are the same, it will be easier for a user to remember (and not confused in some rare cases) which feature gate they needed to enable when kube - apiserver is started. It might be a matter of user convenience. Though I understand the reasoning behind leaving it as is due to the code freeze.

npolshakova commented 1 year ago

/remove-label lead-opted-in

salehsedghpour commented 10 months ago

Hello šŸ‘‹ 1.30 Enhancements Lead here,

I'm closing milestone 1.28 now, If you wish to progress this enhancement in v1.30, please follow the instructions here to opt in the enhancement and make sure the lead-opted-in label is set so it can get added to the tracking board and finally add /milestone v1.30. Thanks!

/milestone clear

k8s-triage-robot commented 7 months ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

jpbetz commented 7 months ago

/remove-lifecycle stale

k8s-triage-robot commented 1 month ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

BenTheElder commented 1 month ago

/remove-lifecycle stale