From a15ea2178ef1ad04b883d93c8adc232a6d87f1c6 Mon Sep 17 00:00:00 2001 From: Rob Scott Date: Fri, 24 Jan 2020 10:18:26 -0800 Subject: [PATCH] Updating Service Topology KEP to include EndpointSlice Controller Changes The EndpointSlice controller needs to be updated to use the new TopologyKeys field on Services when populating topology data. --- keps/sig-network/20181024-service-topology.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/keps/sig-network/20181024-service-topology.md b/keps/sig-network/20181024-service-topology.md index b49b9191ad6..2e003304ce0 100644 --- a/keps/sig-network/20181024-service-topology.md +++ b/keps/sig-network/20181024-service-topology.md @@ -31,6 +31,7 @@ status: implementable - [Service Topology Scalability](#service-topology-scalability) - [New PodLocator resource](#new-podlocator-resource) - [New PodLocator controller](#new-podlocator-controller) + - [EndpointSlice controller changes](#endpointslice-controller-changes) - [Kube-proxy changes](#kube-proxy-changes) - [DNS server changes (in beta stage)](#dns-server-changes-in-beta-stage) - [Test Plan](#test-plan) @@ -175,6 +176,12 @@ When a Node is updated, PodLocator controller will first check if its labels are When a Node is deleted, PodLocator controller will reset the NodeName and NodeLabels of all the PodLocators whose corresponding Pods running on it. +### EndpointSlice controller changes + +The EndpointSlice controller will be updated to set values corresponding to the +TopologyKeys field on Services. All topology values will be derived from labels +on the Node a Pod is running on. + ### Kube-proxy changes Kube-proxy will respect topology keys for each service, so kube-proxy on different nodes may create different proxy rules.