Skip to content

KEP-1645: Fix typo in Upgrade / Downgrade Strategy section #5973

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.

Sign up for GitHub

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

Open
AnupamGhosh wants to merge 3 commits into
base: master
Choose a base branch
from
+5 −9
Open

KEP-1645: Fix typo in Upgrade / Downgrade Strategy section #5973

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
489381f
Fix typo in Upgrade / Downgrade Strategy section
AnupamGhosh Mar 23, 2026
d4fe137
Update README with MCS upgrade and version skew details
AnupamGhosh Apr 3, 2026
af44584
use terms "MCS DNS component" & "mcs-controller component"
AnupamGhosh Apr 16, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 5 additions & 9 deletions keps/sig-multicluster/1645-multi-cluster-services-api/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1183,12 +1183,9 @@ in back-to-back releases.

### Upgrade / Downgrade Strategy

Kube-proxy and must be updated to a supported version before MCS services may be
used. To take advantage of MCS DNS, the DNS provider must be upgraded to a
version that implements the MCS spec. Kube-proxy MCS support will be guarded by
a `MultiClusterServices` feature gate. When enabled, kube-proxy will watch the
`serviceimports.multicluster.k8s.io` CRD. MCS support will be dynamically
enabled and disabled as the CRD is created and deleted.
The MCS API is defined as a set of CRDs (`ServiceExport` and `ServiceImport`) that are installed and managed independently of core Kubernetes components. As such, the upgrade and downgrade strategy is the responsibility of each MCS implementation. The two key components of the implementations are:
- mcs-controller component: responsible for watching `ServiceExport` resources and managing the lifecycle of `ServiceImport` objects and their associated `EndpointSlice` resources.
- MCS DNS component: responsible for serving the `<svc>.<ns>.svc.clusterset.local` domain, conforming to the multicluster DNS specification as defined in this KEP's [specification.md](specification.md).
<!--
If applicable, how will the component be upgraded and downgraded? Make sure
this is in the test plan.
Expand All @@ -1203,9 +1200,8 @@ enhancement:

### Version Skew Strategy

Kube-proxy and DNS must be upgraded before new MCS API versions may be used.
Backwards compatibility will be maintained in accordance with the [deprecation
policy](https://kubernetes.io/docs/reference/using-api/deprecation-policy/).
- mcs-controller component <-> MCS CRD versions: The mcs-controller component must support the installed version of the `ServiceExport` and `ServiceImport` CRDs. Backwards compatibility will be maintained in accordance with the [deprecation policy](https://kubernetes.io/docs/reference/using-api/deprecation-policy/).
- MCS DNS component <-> MCS DNS spec: The MCS DNS component must conform to the multicluster DNS specification as defined in this KEP's [specification.md](specification.md).
<!--
If applicable, how will the component handle version skew with other
components? What are the guarantees? Make sure this is in the test plan.
Expand Down