Unknown Version Interoperability Proxy

[richabanker]

Enhancement Description

• One-line enhancement description (can be used as a release note): Allow a resource request to be served by the correct apiserver in the case when there are multiple apiservers at varied versions
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/4020-unknown-version-interoperability-proxy
• Discussion Link: https://docs.google.com/document/d/1x9RNaaysyO0gXHIr1y50QFbiL1x8OWnk2v3XnrdkT5Y/edit#bookmark=id.zh5gxrgo2ufp
• Primary contact (assignee): richabanker
• Responsible SIGs: api-machinery
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.28
  • Beta release target (x.y):
  • Stable release target (x.y):
• Alpha
  • KEP (k/enhancements) update PR(s):
    • KEP-4020: Unknown Version Interoperability Proxy #4015
    • KEP-4020: Unknown Version Interoperability Proxy : Remove uvip acronym from metrics/headers #4074
    • KEP-4020: Unknown Version Interoperability Proxy : Update KEP status as 'implementable' #4091
  • Code (k/k) update PR(s):
    • Add servedVersions info in StorageVersion API kubernetes#118386
    • add list of served versions to storage version kubernetes#119272
    • Unknown Version Interoperability Proxy Impl kubernetes#117740
  • Docs (k/website) update PR(s):
    • Add MVP documentation website#42147
    • Add post-release blog article about MVP website#41723

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

[richabanker]

/sig api-machinery

[deads2k]

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

[Atharva-Shinde]

/stage alpha

[ruheenaansari34]

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:

• KEP readme using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for latest-milestone: 1.28
• KEP readme has a updated detailed test plan section filled out
• KEP readme has up to date graduation criteria
• KEP has a production readiness review that has been completed and merged into k/enhancements.

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

• Merging KEP-4020: Unknown Version Interoperability Proxy #4015

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!