Skip to content
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

WIP for userns KEP #4

Closed
wants to merge 4 commits into from
Closed

WIP for userns KEP #4

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
2c890ef
Update graduation criteria based on 5/11 SIG-MC discussions
lauralorenz Jul 13, 2021
3df4dd2
add a note to make it clear implementation details vary and to explic…
lauralorenz Nov 30, 2021
267d78d
Merge pull request #2821 from lauralorenz/patch-1
k8s-ci-robot Nov 30, 2021
54b72ea
Add KEP for user namespaces support
rata Nov 29, 2021
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
10 changes: 5 additions & 5 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 @@ -285,8 +285,8 @@ be recognized as a single combined service. For example, if 5 clusters export
all exporting clusters. Properties of the `ServiceImport` (e.g. ports, topology)
will be derived from a merger of component `Service` properties.

Existing implementations of Kubernetes Service API (e.g. kube-proxy) can be
extended to present `ServiceImports` alongside traditional `Services`.
This specification is not prescriptive on exact implementation details. Existing implementations of Kubernetes Service API (e.g. kube-proxy) can be
extended to present `ServiceImports` alongside traditional `Services`. One often discussed implementation requiring no changes to kube-proxy is to have the mcs-controller maintain ServiceImports and create "dummy" or "shadow" Service objects, named after a mcs-controller managed EndpointSlice that aggregates all cross-cluster backend IPs, so that kube-proxy programs those endpoints like a regular Service. Other implementations are encouraged as long as the properties of the API described in this document are maintained.

### User Stories

Expand Down Expand Up @@ -791,6 +791,7 @@ cluster name and `multicluster.kubernetes.io/source-cluster` label may be used
to find and remove all `EndpointSlices` containing endpoints from the
unreachable cluster.


## Constraints and Conflict Resolution

Exported services are derived from the properties of each component service and
Expand Down Expand Up @@ -870,19 +871,18 @@ when drafting this test plan.
- A detailed DNS spec for multi-cluster services.
- NetworkPolicy either solved or explicitly ruled out.
- API group chosen and approved.
- Implementation strategy defined and approved.
- Kube-proxy can consume ServiceImport and EndpointSlice.
- E2E tests exist for MCS services.
- Beta -> GA Graduation criteria defined.
- At least one MCS DNS implementation.
- A formal plan for a standard Cluster ID.
- Finalize a name for the "supercluster" concept.
- [Cluster ID KEP](https://github.com/kubernetes/enhancements/tree/master/keps/sig-multicluster/2149-clusterid) is in beta

#### Beta -> GA Graduation

- Scalability/performance testing, understanding impact on cluster-local service
scalability.
- Cluster ID defined, with at least one other multi-cluster use case.
- [Cluster ID KEP](https://github.com/kubernetes/enhancements/tree/master/keps/sig-multicluster/2149-clusterid) is GA, with at least one other multi-cluster use case.

<!--
**Note:** *Not required until targeted at a release.*
Expand Down
Loading