meta updates

2026-09-27 05:28:22 +00:00 · 2019-12-30 14:48:33 -07:00
parent 4ad1e13933
commit 3a9cf5d0bb
43 changed files with 297 additions and 34 deletions
@@ -1,5 +1,7 @@
 ---
 title: Rancher 2.x
 shortTitle: Rancher 2.x
 description: Rancher adds significant value on top of Kubernetes, managing hundreds of clusters from one interface, centralizing RBAC, enabling monitoring and alerting. Read more.
 insertOneSix: true
 weight: 1
 ctaBanner: intro-k8s-rancher-online-training
@@ -1,5 +1,6 @@
 ---
 title: Configuring Keycloak (SAML)
 description: Create a Keycloack SAML client and configure Rancher to work with Keycloak. By the end your users will be able to sign into Rancher using their Keycloak logins
 weight: 1200
 ---
 _Available as of v2.1.0_
@@ -1,5 +1,6 @@
 ---
-title: Catalogs and Apps
+title: Catalogs, Helm Charts and Apps
 description: Rancher enables the use of catalogs to repeatedly deploy applications easily. Catalogs are GitHub or Helm Chart repositories filled with deployment-ready apps.
 weight: 4000
 aliases:
  - /rancher/v2.x/en/concepts/global-configuration/catalog/
@@ -1,5 +1,6 @@
 ---
-title: CLI
+title: Using the Rancher Command Line Interface 
 description: The Rancher CLI is a unified tool that you can use to interact with Rancher. With it, you can operate Rancher using a command line interface rather than the GUI
 weight: 6000
 aliases:
  - /rancher/v2.x/en/concepts/cli-configuration/
@@ -1,5 +1,6 @@
 ---
-title: Cleaning up Clusters
+title: Removing Kubernetes Components from Nodes
 description: Learn about cluster cleanup when removing nodes from your Rancher-launched Kubernetes cluster. What is removed, how to do it manually
 weight: 2055
 aliases:
  - /rancher/v2.x/en/faq/cleaning-cluster-nodes/
@@ -1,5 +1,6 @@
 ---
-title: Kubeconfig File
+title: Configuring Access to Kubernetes Using A Kubeconfig File
 description: A kubeconfig file is used to configure access to Kubernetes. When you create a cluster with Rancher, it automatically creates a kubeconfig for your cluster
 weight: 2010
 aliases:
  - /rancher/v2.x/en/concepts/clusters/kubeconfig-files/
@@ -1,5 +1,6 @@
 ---
-title: Using kubectl to Access a Cluster
+title: Access a Cluster with Kubectl Shell or Kubectl CLI
 description: Learn how you can access and manage your Kubernetes clusters using kubectl in two ways, with the kubectl shell or with the kubectl CLI and a kubeconfig file
 weight: 2015
 aliases:
  - /rancher/v2.x/en/tasks/clusters/using-kubectl-to-access-a-cluster/
@@ -1,5 +1,6 @@
 ---
-title: Projects and Namespaces
+title: Projects and Kubernetes Namespaces with Rancher
 description: Rancher Projects ease the administrative burden of your cluster and support multi-tenancy. Learn to create projects and divide projects into Kubernetes namespaces
 weight: 2032
 aliases:
  - /rancher/v2.x/en/concepts/projects/
@@ -1,5 +1,6 @@
 ---
-title: Logging
+title: Rancher Integration with Logging Services
 description: Rancher integrates with popular logging services. Learn the requirements and benefits of integrating with logging services, and enable logging on your cluster.
 weight: 3
 aliases:
  - /rancher/v2.x/en/tasks/logging/
@@ -1,5 +1,6 @@
 ---
-title: Monitoring
+title: Integrating Rancher and Prometheus for Cluster Monitoring
 description: Prometheus lets you view metrics from your different Rancher and Kubernetes objects. Lern about the scope of monitoring and how to enable cluster monitoring
 weight: 4
 ---
@@ -1,5 +1,6 @@
 ---
-title: Volumes and Storage
+title: Kubernetes Persistent Storage, Volumes, and Storage Classes
 description: Learn about creating persistent storage in Kubernetes with persistent volumes and storage classes
 weight: 2031
 aliases:
  - /rancher/v2.x/en/concepts/volumes-and-storage/
@@ -1,5 +1,6 @@
 ---
 title: Provisioning Kubernetes Clusters
 description: Read about Kubernetes clusters, what they are, the different node types, and how to create clusters in Rancher
 weight: 2000
 aliases:
  - /rancher/v2.x/en/concepts/clusters/
@@ -1,5 +1,6 @@
 ---
-title: Importing Kubernetes Clusters
+title: Import an Existing Cluster to Create a Cluster in Rancher
 description: Learn how you can create a cluster in Rancher by importing an existing Kubernetes cluster. Then, you can manage it using Rancher
 weight: 2300
 aliases:
  - /rancher/v2.x/en/tasks/clusters/import-cluster/
@@ -1,5 +1,6 @@
 ---
 title: Creating a Cluster with Custom Nodes
 description: To create a cluster with custom nodes, you’ll need to access servers in your cluster and provision them according to Rancher requirements 
 shortTitle: Custom Nodes
 weight: 2225
 aliases:
@@ -1,6 +1,7 @@
 ---
 title: Creating an Amazon EC2 Cluster
 shortTitle: Amazon EC2
 description: Learn the prerequisites and steps required in order for you to create an Amazon EC2 cluster using Rancher
 weight: 2210
 aliases:
  - /rancher/v2.x/en/tasks/clusters/creating-a-cluster/create-cluster-amazon-ec2/
@@ -199,4 +200,4 @@ Use {{< product >}} to create a Kubernetes cluster in Amazon EC2.
    }
  ]
 }
-```
+```
@@ -1,6 +1,7 @@
 ---
 title: Creating a vSphere Cluster
 shortTitle: vSphere
 description: Use Rancher to create a vSphere cluster. It may consist of groups of VMs with distinct properties which allow for fine-grained control over the sizing of nodes. 
 weight: 2225
 aliases:
  - /rancher/v2.x/en/tasks/clusters/creating-a-cluster/create-cluster-vsphere/
@@ -1,5 +1,6 @@
 ---
-title: CNI Providers
+title: Container Network Interface (CNI) Providers
 description: Learn about Container Network Interface (CNI), the CNI providers Rancher provides, the features they offer, and how to choose a provider for you
 weight: 2300
 ---
@@ -1,5 +1,6 @@
 ---
-title: Installation
+title: Overview of Installation Options
 description: Learn how to install Rancher in development and production environments. Read about single node and high availability installation
 weight: 50
 ---
@@ -1,6 +1,7 @@
 ---
 title: How to Install Rancher on a High-availability Kubernetes Cluster
 weight: 3
 description: For production environments, install Rancher in a high-availability configuration. Read the guide for setting up a 3-node cluster and still install Rancher using a Helm chart.
 ---
 For production environments, we recommend installing Rancher in a high-availability configuration so that your user base can always access Rancher Server. When installed in a Kubernetes cluster, Rancher will integrate with the cluster's etcd database and take advantage of Kubernetes scheduling for high-availability.
@@ -1,5 +1,6 @@
 ---
-title: '3.  Install Rancher'
+title: 3. Installing Rancher Using the Helm Kubernetes Package Manager
 description: Rancher installation is managed using the Helm Kubernetes package manager. Use Helm to install the prerequisites and charts to install Rancher
 weight: 200
 ---
@@ -1,5 +1,6 @@
 ---
-title: '2. Install Kubernetes with RKE'
+title: 2. Install Kubernetes with RKE
 description: Learn how to use Rancher Kubernetes Engine (RKE) to install Kubernetes with a high availability etcd configuration.
 weight: 190
 ---
@@ -1,5 +1,6 @@
 ---
-title: "3. Initialize Helm (Install Tiller)"
+title: Initialize Helm: Install the Tiller Service
 description: With Helm, you can create configurable deployments instead of using static files. In order to use Helm, the Tiller service needs to be installed on your cluster.
 weight: 195
 ---
@@ -1,5 +1,6 @@
 ---
-title: Adding TLS Secrets
+title: Adding Kubernetes TLS Secrets
 description: Read about how to populate the Kubernetes TLS secret for a Rancher installation 
 weight: 276
 ---
@@ -1,5 +1,6 @@
 ---
 title: Installation Requirements
 description: Learn the node requirements for each node running Rancher server when you’re configuring  Rancher to run either in a single-node or high-availability setup
 weight: 1
 aliases:
  - /rancher/v2.x/en/installation/references
@@ -1,5 +1,6 @@
 ---
 title: Port Requirements
 description: Read about port requirements needed in order for Rancher to operate properly, both for Rancher nodes and Kubernetes cluster nodes
 weight: 300
 ---
@@ -0,0 +1,221 @@
 ---
 title: Single Node Install
 description: For development and testing environments, use a single node install. Install Docker on a single Linux host, and deploy Rancher with a single Docker container.
 weight: 250
 aliases:
  - /rancher/v2.x/en/installation/single-node-install/
 ---
 For development and testing environments, we recommend installing Rancher by running a single Docker container. In this installation scenario, you'll install Docker on a single Linux host, and then deploy Rancher on your host using a single Docker container.
 >**Want to use an external load balancer?**
 > See [Single Node Install with an External Load Balancer]({{< baseurl >}}/rancher/v2.x/en/installation/single-node/single-node-install-external-lb) instead.
 ## 1. Provision Linux Host
 Provision a single Linux host according to our [Requirements]({{< baseurl >}}/rancher/v2.x/en/installation/requirements) to launch your {{< product >}} Server.
 ## 2. Choose an SSL Option and Install Rancher
 For security purposes, SSL (Secure Sockets Layer) is required when using Rancher. SSL secures all Rancher network communication, like when you login or interact with a cluster.
 >**Do you want to...**
 >
 >- Use a proxy? See [HTTP Proxy Configuration]({{< baseurl >}}/rancher/v2.x/en/installation/single-node/proxy/)
 >- Configure custom CA root certificate to access your services? See [Custom CA root certificate]({{< baseurl >}}/rancher/v2.x/en/admin-settings/custom-ca-root-certificate/)
 >- Complete an Air Gap Installation? See [Air Gap: Single Node Install]({{< baseurl >}}/rancher/v2.x/en/installation/air-gap-single-node/)
 >- Record all transactions with the Rancher API? See [API Auditing](#api-audit-log)
 >
 Choose from the following options:
 {{% accordion id="option-a" label="Option A-Default Self-Signed Certificate" %}}
 If you are installing Rancher in a development or testing environment where identity verification isn't a concern, install Rancher using the self-signed certificate that it generates. This installation option omits the hassle of generating a certificate yourself.
 Log into your Linux host, and then run the minimum installation command below.
 	docker run -d --restart=unless-stopped \
 	-p 80:80 -p 443:443 \
 	rancher/rancher:latest
 {{% /accordion %}}
 {{% accordion id="option-b" label="Option B-Bring Your Own Certificate: Self-Signed" %}}
 In development or testing environments where your team will access your Rancher server, create a self-signed certificate for use with your install so that your team can verify they're connecting to your instance of Rancher.
 >**Prerequisites:**
 >Create a self-signed certificate using [OpenSSL](https://www.openssl.org/) or another method of your choice.
 >
 >- The certificate files must be in [PEM format](#pem).
 >- In your certificate file, include all intermediate certificates in the chain. Order your certificates with your certificate first, followed by the intermediates. For an example, see [SSL FAQ / Troubleshooting](#cert-order).
 After creating your certificate, run the Docker command below to install Rancher. Use the `-v` flag and provide the path to your certificates to mount them in your container.
 Placeholder | Description
 ------------|-------------
 `<CERT_DIRECTORY>` | The path to the directory containing your certificate files.
 `<FULL_CHAIN.pem>` | The path to your full certificate chain.
 `<PRIVATE_KEY.pem>` | The path to the private key for your certificate.
 `<CA_CERTS>` | The path to the certificate authority's private key.
 ```
 docker run -d --restart=unless-stopped \
 	-p 80:80 -p 443:443 \
 	-v /<CERT_DIRECTORY>/<FULL_CHAIN.pem>:/etc/rancher/ssl/cert.pem \
 	-v /<CERT_DIRECTORY>/<PRIVATE_KEY.pem>:/etc/rancher/ssl/key.pem \
 	-v /<CERT_DIRECTORY>/<CA_CERTS.pem>:/etc/rancher/ssl/cacerts.pem \
 	rancher/rancher:latest
 ```
 {{% /accordion %}}
 {{% accordion id="option-c" label="Option C-Bring Your Own Certificate: Signed by Recognized CA" %}}
 In production environments where you're exposing an app publicly, use a certificate signed by a recognized CA so that your user base doesn't encounter security warnings.
 >**Prerequisites:**
 >
 >- The certificate files must be in [PEM format](#pem).
 >- In your certificate file, include all intermediate certificates provided by the recognized CA. Order your certificates with your certificate first, followed by the intermediates. For an example, see [SSL FAQ / Troubleshooting](#cert-order).
 After obtaining your certificate, run the Docker command below.
 - Use the `-v` flag and provide the path to your certificates to mount them in your container. Because your certificate is signed by a recognized CA, mounting an additional CA certificate file is unnecessary.
 - Use the `--no-cacerts` as argument to the container to disable the default CA certificate generated by Rancher.
 Placeholder | Description
 ------------|-------------
 `<CERT_DIRECTORY>` | The path to the directory containing your certificate files.
 `<FULL_CHAIN.pem>` | The path to your full certificate chain.
 `<PRIVATE_KEY.pem>` | The path to the private key for your certificate.
 ```
 docker run -d --restart=unless-stopped \
 	-p 80:80 -p 443:443 \
 	-v /<CERT_DIRECTORY>/<FULL_CHAIN.pem>:/etc/rancher/ssl/cert.pem \
 	-v /<CERT_DIRECTORY>/<PRIVATE_KEY.pem>:/etc/rancher/ssl/key.pem \
 	rancher/rancher:latest \
  --no-cacerts
 ```
 {{% /accordion %}}
 {{% accordion id="option-d" label="Option D-Let's Encrypt Certificate" %}}
 >**Remember:** Let's Encrypt provides rate limits for requesting new certificates. Therefore, limit how often you create or destroy the container. For more information, see [Let's Encrypt documentation on rate limits](https://letsencrypt.org/docs/rate-limits/).
 For production environments, you also have the option of using [Let's Encrypt](https://letsencrypt.org/) certificates. Let's Encrypt uses an http-01 challenge to verify that you have control over your domain. You can confirm that you control the domain by pointing the hostname that you want to use for Rancher access (for example, `rancher.mydomain.com`) to the IP of the machine it is running on. You can bind the hostname to the IP address by creating an A record in DNS.
 >**Prerequisites:**
 >
 >- Let's Encrypt is an Internet service. Therefore, this option cannot be used in an internal/air gapped network.
 >- Create a record in your DNS that binds your Linux host IP address to the hostname that you want to use for Rancher access (`rancher.mydomain.com` for example).
 >- Open port `TCP/80` on your Linux host. The Let's Encrypt http-01 challenge can come from any source IP address, so port `TCP/80` must be open to all IP addresses.
 After you fulfill the prerequisites, you can install Rancher using a Let's Encrypt certificate by running the following command.
 Placeholder | Description
 ------------|-------------
 `<YOUR.DNS.NAME>` | Your domain address
 ```
 docker run -d --restart=unless-stopped \
  -p 80:80 -p 443:443 \
  rancher/rancher:latest \
  --acme-domain <YOUR.DNS.NAME>
 ```
 {{% /accordion %}}
 ## What's Next?
 - **Recommended:** Review [Single Node Backup and Restoration]({{< baseurl >}}/rancher/v2.x/en/installation/backups-and-restoration/single-node-backup-and-restoration/). Although you don't have any data you need to back up right now, we recommend creating backups after regular Rancher use.
 - Create a Kubernetes cluster: [Provisioning Kubernetes Clusters]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/).
 <br/>
 ## Advanced Options
 When installing Rancher, there are several [advanced options]({{< baseurl >}}/rancher/v2.x/en/installation/options/) that can be enabled.
 ### Custom CA Certificate
 If you want to configure Rancher to use a CA root certificate to be used when validating services, you would start the Rancher container sharing the directory that contains the CA root certificate.
 Use the command example to start a Rancher container with your private CA certificates mounted.
 - The volume option (`-v`) should specify the host directory containing the CA root certificates.
 - The `e` flag in combination with `SSL_CERT_DIR` declares an environment variable that specifies the mounted CA root certificates directory location inside the container.
 	- Passing environment variables to the Rancher container can be done using `-e KEY=VALUE` or `--env KEY=VALUE`.
 	- Mounting a host directory inside the container can be done using `-v host-source-directory:container-destination-directory` or `--volume host-source-directory:container-destination-directory`.
 The example below is based on having the CA root certificates in the `/host/certs` directory on the host and mounting this directory on `/container/certs` inside the Rancher container.
 ```
 docker run -d --restart=unless-stopped \
  -p 80:80 -p 443:443 \
  -v /host/certs:/container/certs \
  -e SSL_CERT_DIR="/container/certs" \
  rancher/rancher:latest
 ```
 ### API Audit Log
 The API Audit Log records all the user and system transactions made through Rancher server.
 The API Audit Log writes to `/var/log/auditlog` inside the rancher container by default. Share that directory as a volume and set your `AUDIT_LEVEL` to enable the log.
 See [API Audit Log]({{< baseurl >}}/rancher/v2.x/en/installation/api-auditing) for more information and options.
 ```
 docker run -d --restart=unless-stopped \
  -p 80:80 -p 443:443 \
  -v /var/log/rancher/auditlog:/var/log/auditlog \
  -e AUDIT_LEVEL=1 \
  rancher/rancher:latest
 ```
 ### TLS settings
 _Available as of v2.1.7_
 To set a different TLS configuration, you can use the `CATTLE_TLS_MIN_VERSION` and `CATTLE_TLS_CIPHERS` environment variables. For example, to configure TLS 1.0 as minimum accepted TLS version:
 ```
 docker run -d --restart=unless-stopped \
  -p 80:80 -p 443:443 \
  -e CATTLE_TLS_MIN_VERSION="1.0" \
  rancher/rancher:latest
 ```
 See [TLS settings]({{< baseurl >}}/rancher/v2.x/en/admin-settings/tls-settings) for more information and options.
 ### Air Gap
 If you are visiting this page to complete an air gap installation, you must pre-pend your private registry URL to the server tag when running the installation command in the option that you choose. Add `<REGISTRY.DOMAIN.COM:PORT>` with your private registry URL in front of `rancher/rancher:latest`.
 **Example:**
 	 <REGISTRY.DOMAIN.COM:PORT>/rancher/rancher:latest
 ### Persistent Data
 {{< persistentdata >}}
 ### Running `rancher/rancher` and `rancher/rancher-agent` on the Same Node
 In the situation where you want to use a single node to run Rancher and to be able to add the same node to a cluster, you have to adjust the host ports mapped for the `rancher/rancher` container.
 If a node is added to a cluster, it deploys the nginx ingress controller which will use port 80 and 443. This will conflict with the default ports we advise to expose for the `rancher/rancher` container.
 Please note that this setup is not recommended for production use, but can be convenient for development/demo purposes.
 To change the host ports mapping, replace the following part `-p 80:80 -p 443:443` with `-p 8080:80 -p 8443:443`:
 ```
 docker run -d --restart=unless-stopped \
  -p 8080:80 -p 8443:443 \
  rancher/rancher:latest
 ```
 ## FAQ and Troubleshooting
 {{< ssl_faq_single >}}
@@ -1,5 +1,6 @@
 ---
-title: SSL Certificates
+title: Secure Sockets Layer Certificate
 description: Learn how to add a secure sockets layer (SSL) certificate to either a project, a namespace, or both, so that you can add it to deployments
 weight: 3060
 aliases:
  - /rancher/v2.x/en/tasks/projects/add-ssl-certificates/
@@ -1,5 +1,6 @@
 ---
-title: Horizontal Pod Autoscaler
+title: The Horizontal Pod Autoscaler
 description: Learn about the horizontal pod autoscaler (HPA). How to manage HPAs and how to test them with a service deployment
 weight: 3026
 ---
@@ -31,4 +32,4 @@ You might have additional HPA installation steps if you are using an older versi
 In Rancher v2.3.x+, you can see your HPA's current number of replicas by going to your project and clicking **Resources > HPA.** For more information, refer to [Get HPA Metrics and Status]({{< baseurl >}}/rancher/v2.x/en/k8s-in-rancher/horitzontal-pod-autoscaler/manage-hpa-with-rancher-ui/).
 You can also use `kubectl` to get the status of HPAs that you test with your load testing tool. For more information, refer to [Testing HPAs with kubectl]
-({{< baseurl >}}/rancher/v2.x/en/k8s-in-rancher/horitzontal-pod-autoscaler/testing-hpa/).
+({{< baseurl >}}/rancher/v2.x/en/k8s-in-rancher/horitzontal-pod-autoscaler/testing-hpa/).
@@ -1,5 +1,6 @@
 ---
-title: Load Balancing and Ingresses
+title: Set Up Load Balancer and Ingress Controller within Rancher
 description: Learn how you can set up load balancers and ingress controllers to redirect service requests within Rancher, and learn about the limitations of load balancers
 weight: 3040
 ---
@@ -1,5 +1,6 @@
 ---
-title: Ingress
+title: Adding Ingresses to Your Project
 description: Ingresses can be added for workloads to provide load balancing, SSL termination and host/path-based routing. Learn how to add Rancher ingress to your project
 weight: 3042
 aliases:
  - /rancher/v2.x/en/tasks/workloads/add-ingress/
@@ -1,5 +1,6 @@
 ---
-title: Load Balancers
+title: Layer 4 and Layer 7 Load Balancing
 description: Kubernetes supports load balancing with Layer-4 Load Balancing and Layer-7 Load Balancing. Learn about the support for each way in different deployments
 weight: 3041
 aliases:
  - /rancher/v2.x/en/concepts/load-balancing/
@@ -1,5 +1,6 @@
 ---
-title: Registries
+title: Kubernetes Registry and Docker Registry
 description: Learn about the Docker registry and Kubernetes registry, their use cases and how to use a private registry with the Rancher UI
 weight: 3063
 aliases:
  - /rancher/v2.x/en/tasks/projects/add-registries/
@@ -112,4 +113,4 @@ The result should look like this:
 10s         Normal    Pulled             Pod    Successfully pulled image "quay.io/<Profile name>/<image name>"
 ```
-For more information, refer to the Kubernetes documentation on [creating a pod that uses your secret.](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/#create-a-pod-that-uses-your-secret)
+For more information, refer to the Kubernetes documentation on [creating a pod that uses your secret.](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/#create-a-pod-that-uses-your-secret)
@@ -1,5 +1,6 @@
 ---
-title: Workloads
+title: Kubernetes Workloads and Pods
 description: Learn about the two constructs with which you can build any complex containerized application in Kubernetes, Kubernetes workloads and pods
 weight: 3025
 aliases:
  - /rancher/v2.x/en/concepts/workloads/
@@ -1,5 +1,6 @@
 ---
 title: Deploying Workloads
 description: Read this step by step guide for deploying workloads. Deploy a workload to run an application in one or more containers.
 weight: 3026
 aliases:
  - /rancher/v2.x/en/tasks/workloads/deploy-workloads/
@@ -1,5 +1,6 @@
 ---
-title:  Pipelines
+title:  Rancher's CI/CD Pipelines
 description: Use Rancher’s CI/CD pipeline to automatically checkout code, run builds or scripts, publish Docker images, and deploy software to users
 weight: 2529
 aliases:
  - /rancher/v2.x/en/concepts/ci-cd-pipelines/
@@ -1,6 +1,6 @@
 ---
-title: Quick Start Guides
+title: Rancher Deployment Quick Start Guides
-short title: Quick Start Index
+short title: Use this section to jump start your Rancher deployment and testing. It contains instructions for a simple Rancher setup and some common use cases. 
 weight: 25
 ---
 >**Note:** The intent of these guides is to quickly launch a sandbox that you can use to evaluate Rancher. These guides are not intended for production environments. For comprehensive setup instructions, see [Installation]({{< baseurl >}}/rancher/v2.x/en/installation/).
@@ -1,5 +1,6 @@
 ---
-title: Amazon AWS Quick Start
+title: Rancher AWS Quick Start Guide
 description: Read this step by step Rancher AWS guide to quickly deploy a Rancher Server with a single node cluster attached.
 weight: 100
 ---
 The following steps will quickly deploy a Rancher Server with a single node cluster attached.
@@ -1,6 +1,7 @@
 ---
 title: Overview of RKE
 shortTitle: RKE
 description: RKE solves Kubernetes installation complexity. With RKE, Kubernetes installation is simplified, regardless of what OSs and platforms you’re running.
 weight: 1
 ---
@@ -1,5 +1,6 @@
 ---
-title: Config Options
+title: Kubernetes Configuration Options
 description: There are a lot of different Kubernetes Configuration options you can choose from when setting up your cluster.yml for RKE
 weight: 200
 ---
@@ -1,5 +1,6 @@
 ---
-title: Ingress Controllers
+title: K8s Ingress Controllers
 description: By default, RKE deploys the NGINX ingress controller. Learn how to schedule and disable default k8s ingress controllers, and how to configure NGINX controller
 weight: 262
 ---
@@ -1,5 +1,6 @@
 ---
-title: Kubernetes Default Services
+title: Default Kubernetes Services
 description: To deploy Kubernetes, RKE deploys several default Kubernetes services. Read about etcd, kube-api server, kubelet, kube-proxy and more
 weight: 230
 ---
@@ -1,5 +1,6 @@
 ---
-title: Installation
+title: RKE Kubernetes Installation
 description: RKE is a fast, versatile Kubernetes installer you can use to install Kubernetes on your Linux hosts. Learn the simple steps for an RKE Kubernetes installation
 weight: 50
 ---
@@ -1,5 +1,6 @@
 ---
 title: Adding and Removing Nodes
 description: RKE supports adding/removing nodes for worker and controlplane hosts. Learn about the changes you need to make to the cluster.yml in order to add/remove nodes
 weight: 175
 aliases:
  - /rke/latest/en/installation/managing-clusters/