From 0b95b70bdeddf981104a5940860ef2f8ca38ff4d Mon Sep 17 00:00:00 2001 From: Karen Bradshaw Date: Tue, 7 Apr 2020 17:09:33 -0400 Subject: [PATCH] fix page formatting --- .../cluster-administration/flow-control.md | 8 ++--- .../setup-konnectivity/setup-konnectivity.md | 33 ++++++++++++++----- 2 files changed, 28 insertions(+), 13 deletions(-) diff --git a/content/en/docs/concepts/cluster-administration/flow-control.md b/content/en/docs/concepts/cluster-administration/flow-control.md index fd8227bfa0..6540a05e8f 100644 --- a/content/en/docs/concepts/cluster-administration/flow-control.md +++ b/content/en/docs/concepts/cluster-administration/flow-control.md @@ -18,12 +18,12 @@ potentially crashing the API server, but these flags are not enough to ensure that the most important requests get through in a period of high traffic. The API Priority and Fairness feature (APF) is an alternative that improves upon -aforementioned max-inflight limitations. APF classifies -and isolates requests in a more fine-grained way. It also introduces +aforementioned max-inflight limitations. APF classifies +and isolates requests in a more fine-grained way. It also introduces a limited amount of queuing, so that no requests are rejected in cases of very brief bursts. Requests are dispatched from queues using a -fair queuing technique so that, for example, a poorly-behaved {{< -glossary_tooltip text="controller" term_id="controller" >}}) need not +fair queuing technique so that, for example, a poorly-behaved +{{< glossary_tooltip text="controller" term_id="controller" >}} need not starve others (even at the same priority level). {{< caution >}} diff --git a/content/en/docs/tasks/setup-konnectivity/setup-konnectivity.md b/content/en/docs/tasks/setup-konnectivity/setup-konnectivity.md index 0fdbd0127d..b5dbd05215 100644 --- a/content/en/docs/tasks/setup-konnectivity/setup-konnectivity.md +++ b/content/en/docs/tasks/setup-konnectivity/setup-konnectivity.md @@ -1,30 +1,43 @@ --- -title: Setup Konnectivity Service +title: Set up Konnectivity service content_template: templates/task -weight: 110 +weight: 70 --- +{{% capture overview %}} + The Konnectivity service provides TCP level proxy for the Master → Cluster communication. -You can set it up with the following steps. +{{% /capture %}} + +{{% capture prerequisites %}} + +{{< include "task-tutorial-prereqs.md" >}} + +{{% /capture %}} + +{{% capture steps %}} + +## Configure the Konnectivity service First, you need to configure the API Server to use the Konnectivity service to direct its network traffic to cluster nodes: + 1. Set the `--egress-selector-config-file` flag of the API Server, it is the path to the API Server egress configuration file. -2. At the path, create a configuration file. For example, +1. At the path, create a configuration file. For example, {{< codenew file="admin/konnectivity/egress-selector-configuration.yaml" >}} -Next, you need to deploy the Konnectivity service server and agents. +Next, you need to deploy the Konnectivity server and agents. [kubernetes-sigs/apiserver-network-proxy](https://github.com/kubernetes-sigs/apiserver-network-proxy) is a reference implementation. -Deploy the Konnectivity server on your master node. The provided yaml assuming -Kubernetes components are deployed as {{< glossary_tooltip text="static pod" -term_id="static-pod" >}} in your cluster. If not , you can deploy it as a -Daemonset to be reliable. +Deploy the Konnectivity server on your master node. The provided yaml assumes +that the Kubernetes components are deployed as a {{< glossary_tooltip text="static Pod" +term_id="static-pod" >}} in your cluster. If not, you can deploy the Konnectivity +server as a DaemonSet. {{< codenew file="admin/konnectivity/konnectivity-server.yaml" >}} @@ -35,3 +48,5 @@ Then deploy the Konnectivity agents in your cluster: Last, if RBAC is enabled in your cluster, create the relevant RBAC rules: {{< codenew file="admin/konnectivity/konnectivity-rbac.yaml" >}} + +{{% /capture %}} \ No newline at end of file