[EV-4372] Rename EXT_NODE_PORT for load-balancer.

check-spelling-sandbox · Nov 14, 2023 · 5e2255d · 5e2255d
1 parent e628384
commit 5e2255d
Show file tree

Hide file tree

Showing 4 changed files with 22 additions and 22 deletions.
diff --git a/.../set-up-multi-cluster-management/helm-install/create-a-managed-cluster-helm.mdx b/.../set-up-multi-cluster-management/helm-install/create-a-managed-cluster-helm.mdx
@@ -45,7 +45,7 @@ If you are installing on a cluster installed by EKS, GKE, AKS or Mirantis Kubern
 1. If you are installing on a cluster installed by EKS, GKE, AKS or Mirantis Kubernetes Engine (MKE), set the `kubernetesProvider` as described in the [Installation reference](../../../reference/installation/api.mdx#operator.tigera.io/v1.Provider). For example:
 
   ```bash
-  echo '{ installation: {kubernetesProvider: EKS }}' > values.yaml
+  echo '{ installation: { kubernetesProvider: EKS }}' > values.yaml
   ```
 
    For Azure AKS cluster with no Kubernetes CNI pre-installed, create `values.yaml` with the following command:

diff --git a/...t-up-multi-cluster-management/helm-install/create-a-management-cluster-helm.mdx b/...t-up-multi-cluster-management/helm-install/create-a-management-cluster-helm.mdx
@@ -160,13 +160,13 @@ To install a {{prodname}} [management](create-a-management-cluster-helm#value) c
 
 To install a {{prodname}} [management](create-a-management-cluster-helm#value) cluster with Helm, using a LoadBalancer service:
 
-#### Meet cloud provider requirements.
+#### Meet cloud provider requirements
 
-You must ensure that you have met the requirements for your cloud provider to provision a load balancer in your environment.
+Ensure that you have met the requirements for your cloud provider to provision a load balancer in your environment.
 
 For example, if you are using EKS, you must meet the requirements defined in [create a network load balancer for AWS](https://docs.aws.amazon.com/eks/latest/userguide/network-load-balancing.html)
 
-#### Install the management cluster.
+#### Install the management cluster
 
 1. [Configure a storage class for Calico Enterprise](../../../operations/logstorage/create-storage).
 
@@ -209,15 +209,15 @@ For example, if you are using EKS, you must meet the requirements defined in [cr
   ```
 
   If you are using EKS, make sure your management cluster has the following annotations:
-  ```bash
+  ```yaml
   managementCluster:
     service:
       annotations:
       - key: service.beta.kubernetes.io/aws-load-balancer-type
         value: "external"
-        key: service.beta.kubernetes.io/aws-load-balancer-nlb-target-type
+      - key: service.beta.kubernetes.io/aws-load-balancer-nlb-target-type
         value: "instance"
-        key: service.beta.kubernetes.io/aws-load-balancer-scheme
+      - key: service.beta.kubernetes.io/aws-load-balancer-scheme
         value: "internet-facing"
   ```
 
@@ -241,18 +241,18 @@ For example, if you are using EKS, you must meet the requirements defined in [cr
   watch kubectl get tigerastatus
   ```
 
-#### Update the ManagementCluster address.
+#### Update the ManagementCluster address
 
 1. Export the service port number
 
   ```bash
-  export EXT_NODE_PORT=<your-external-load-balancer-port>
+  export EXT_LB_PORT=<your-external-load-balancer-port>
   ```
 
   Export the public address or host of the management cluster, in this case the load-balancer's external IP (Ex. "example.com:1234" or "10.0.0.10:1234".)
 
   ```bash
-  export MANAGEMENT_CLUSTER_ADDR=<your-load-balancer-external-addr>:$EXT_NODE_PORT
+  export MANAGEMENT_CLUSTER_ADDR=<your-load-balancer-external-addr>:$EXT_LB_PORT
   ```
 
   Replace the `address` field in the ManagementCluster resource.
@@ -265,7 +265,7 @@ For example, if you are using EKS, you must meet the requirements defined in [cr
 </Tabs>
 
 
-#### Create an admin user and verify management cluster connection.
+#### Create an admin user and verify management cluster connection
 
 To access resources in a managed cluster from the {{prodname}} Manager within the management cluster, the logged-in user must have appropriate permissions defined in that managed cluster (clusterrole bindings).
 

diff --git a/.../set-up-multi-cluster-management/helm-install/create-a-managed-cluster-helm.mdx b/.../set-up-multi-cluster-management/helm-install/create-a-managed-cluster-helm.mdx
@@ -45,7 +45,7 @@ If you are installing on a cluster installed by EKS, GKE, AKS or Mirantis Kubern
 1. If you are installing on a cluster installed by EKS, GKE, AKS or Mirantis Kubernetes Engine (MKE), set the `kubernetesProvider` as described in the [Installation reference](../../../reference/installation/api.mdx#operator.tigera.io/v1.Provider). For example:
 
   ```bash
-  echo '{ installation: {kubernetesProvider: EKS }}' > values.yaml
+  echo '{ installation: { kubernetesProvider: EKS }}' > values.yaml
   ```
 
    For Azure AKS cluster with no Kubernetes CNI pre-installed, create `values.yaml` with the following command:

diff --git a/...t-up-multi-cluster-management/helm-install/create-a-management-cluster-helm.mdx b/...t-up-multi-cluster-management/helm-install/create-a-management-cluster-helm.mdx
@@ -160,13 +160,13 @@ To install a {{prodname}} [management](create-a-management-cluster-helm#value) c
 
 To install a {{prodname}} [management](create-a-management-cluster-helm#value) cluster with Helm, using a LoadBalancer service:
 
-#### Meet cloud provider requirements.
+#### Meet cloud provider requirements
 
-You must ensure that you have met the requirements for your cloud provider to provision a load balancer in your environment.
+Ensure that you have met the requirements for your cloud provider to provision a load balancer in your environment.
 
 For example, if you are using EKS, you must meet the requirements defined in [create a network load balancer for AWS](https://docs.aws.amazon.com/eks/latest/userguide/network-load-balancing.html)
 
-#### Install the management cluster.
+#### Install the management cluster
 
 1. [Configure a storage class for Calico Enterprise](../../../operations/logstorage/create-storage).
 
@@ -209,15 +209,15 @@ For example, if you are using EKS, you must meet the requirements defined in [cr
   ```
 
   If you are using EKS, make sure your management cluster has the following annotations:
-  ```bash
+  ```yaml
   managementCluster:
     service:
       annotations:
       - key: service.beta.kubernetes.io/aws-load-balancer-type
         value: "external"
-        key: service.beta.kubernetes.io/aws-load-balancer-nlb-target-type
+      - key: service.beta.kubernetes.io/aws-load-balancer-nlb-target-type
         value: "instance"
-        key: service.beta.kubernetes.io/aws-load-balancer-scheme
+      - key: service.beta.kubernetes.io/aws-load-balancer-scheme
         value: "internet-facing"
   ```
 
@@ -241,18 +241,18 @@ For example, if you are using EKS, you must meet the requirements defined in [cr
   watch kubectl get tigerastatus
   ```
 
-#### Update the ManagementCluster address.
+#### Update the ManagementCluster address
 
 1. Export the service port number
 
   ```bash
-  export EXT_NODE_PORT=<your-external-load-balancer-port>
+  export EXT_LB_PORT=<your-external-load-balancer-port>
   ```
 
   Export the public address or host of the management cluster, in this case the load-balancer's external IP (Ex. "example.com:1234" or "10.0.0.10:1234".)
 
   ```bash
-  export MANAGEMENT_CLUSTER_ADDR=<your-load-balancer-external-addr>:$EXT_NODE_PORT
+  export MANAGEMENT_CLUSTER_ADDR=<your-load-balancer-external-addr>:$EXT_LB_PORT
   ```
 
   Replace the `address` field in the ManagementCluster resource.
@@ -265,7 +265,7 @@ For example, if you are using EKS, you must meet the requirements defined in [cr
 </Tabs>
 
 
-#### Create an admin user and verify management cluster connection.
+#### Create an admin user and verify management cluster connection
 
 To access resources in a managed cluster from the {{prodname}} Manager within the management cluster, the logged-in user must have appropriate permissions defined in that managed cluster (clusterrole bindings).