moved file

Author: abrennan89

docs/README.md

@@ -85,6 +85,7 @@ Follow the links below to learn more about Knative.
 - [Using a custom domain](./serving/using-a-custom-domain.md)
 - [Assigning a static IP address for Knative on Google Kubernetes Engine](./serving/gke-assigning-static-ip-address.md)
 - [Configuring HTTPS with a custom certificate](./serving/using-a-tls-cert.md)
+- [Configuring high availability](./config-ha.md)
 
 ### Samples and demos
 

docs/install/config-ha.md renamed to docs/config-ha.md

@@ -1,7 +1,7 @@
 ---
 title: "Configuring high-availability components"
 linkTitle: "Configuring high-availability components"
-weight: 50
+weight: 20
 type: "docs"
 ---
 
@@ -11,13 +11,13 @@ Active/passive HA in Knative is available through leader election, which is enab
 
 When using a leader election HA pattern, instances of controllers are already scheduled and running inside the cluster before they are required. These controller instances compete to use a shared resource, known as the leader election lock. The instance of the controller that has access to the leader election lock resource at any given time is referred to as the leader.
 
-HA functionality is available on Knative for the `autoscaler-hpa`, `controller`, `activator` , `kourier-control`, `kourier-gateway`, `istio-pilot`, and `istio-gateway` components.
+HA functionality is available on Knative for the `autoscaler-hpa`, `controller` and `activator` components.
 
 ## Enabling leader election
 
 1. Enable leader election for the control plane controllers:
 ```
-kubectl patch configmap/config-leader-election \
+$ kubectl patch configmap/config-leader-election \
   --namespace knative-serving \
   --type merge \
   --patch '{"data":{"enabledComponents": "controller,hpaautoscaler,certcontroller,istiocontroller,nscontroller"}}'
@@ -28,7 +28,7 @@ kubectl patch configmap/config-leader-election \
 Note: you will take a brief amount of control plane downtime during this step.
 
 ```
-kubectl rollout restart deployment -n knative-serving
+$ kubectl rollout restart deployment -n knative-serving
 ```
 When your controllers come back up, they should be running leader-elected.
 At this point, we've configured the controllers to use leader election and we
@@ -37,7 +37,7 @@ can scale the control plane up!
 1. Now, you can scale the control plane up.
 
 ```
-kubectl rollouts restart deployment -n knative-serving controller
+$ kubectl rollouts restart deployment -n knative-serving controller
 ```
 
 ## Scaling the control plane
@@ -51,5 +51,5 @@ The following serving controller deployments can be scaled up once leader electi
 - `networking-ns-cert`
 
 ```
-kubectl scale --replicas=2 <deployment-name>
+$ kubectl scale --replicas=2 <deployment-name>
 ```