1.6 KiB
reviewers | title | content_template | |||
---|---|---|---|---|---|
|
Enabling Service Topology | templates/task |
{{% capture overview %}} This page provides an overview of enabling Service Topology in Kubernetes. {{% /capture %}}
{{% capture prerequisites %}} {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} {{% /capture %}}
{{% capture steps %}}
Introduction
Service Topology enables a service to route traffic based upon the Node topology of the cluster. For example, a service can specify that traffic be preferentially routed to endpoints that are on the same Node as the client, or in the same availability zone.
Prerequisites
The following prerequisites are needed in order to enable topology aware service routing:
- Kubernetes 1.17 or later
- {{< glossary_tooltip text="Kube-proxy" term_id="kube-proxy" >}} running in iptables mode or IPVS mode
- Enable Endpoint Slices
Enable Service Topology
{{< feature-state for_k8s_version="v1.17" state="alpha" >}}
To enable service topology, enable the ServiceTopology
and EndpointSlice
feature gate for all Kubernetes components:
--feature-gates="ServiceTopology=true,EndpointSlice=true"
{{% capture whatsnext %}}
- Read about the Service Topology concept
- Read about Endpoint Slices
- Read Connecting Applications with Services
{{% /capture %}}