diff --git a/content/rancher/v2.x/en/admin-settings/authentication/openldap/_index.md b/content/rancher/v2.x/en/admin-settings/authentication/openldap/_index.md index 5163f93a630..c577e9a2131 100644 --- a/content/rancher/v2.x/en/admin-settings/authentication/openldap/_index.md +++ b/content/rancher/v2.x/en/admin-settings/authentication/openldap/_index.md @@ -2,7 +2,7 @@ title: Configuring OpenLDAP weight: 1113 aliases: - - /rancher/v2.x/en/tasks/global-configuration/authentication/openLDAP/ + - /rancher/v2.x/en/tasks/global-configuration/authentication/openldap/ --- _Available as of v2.0.5_ diff --git a/content/rancher/v2.x/en/admin-settings/pod-security-policies/_index.md b/content/rancher/v2.x/en/admin-settings/pod-security-policies/_index.md index f2fcc4ccd6d..19cfb8fc34f 100644 --- a/content/rancher/v2.x/en/admin-settings/pod-security-policies/_index.md +++ b/content/rancher/v2.x/en/admin-settings/pod-security-policies/_index.md @@ -2,8 +2,9 @@ title: Managing Pod Security Policies weight: 1135 aliases: - - /rancher/v2.x/en/concepts/global-configuration/pod-security-policies - - /rancher/v2.x/en/tasks/global-configuration/pod-security-policies + - /rancher/v2.x/en/concepts/global-configuration/pod-security-policies/ + - /rancher/v2.x/en/tasks/global-configuration/pod-security-policies/ + - /rancher/v2.x/en/tasks/clusters/adding-a-pod-security-policy/ --- _Pod Security Policies_ (or PSPs) are objects that control security-sensitive aspects of pod specification (like root privileges). If a pod does not meet the conditions specified in the PSP, Kubernetes will not allow it to start, and Rancher will display an error message of `Pod is forbidden: unable to validate...`. diff --git a/content/rancher/v2.x/en/kubernetes-in-rancher/certificates/_index.md b/content/rancher/v2.x/en/kubernetes-in-rancher/certificates/_index.md index aa076321b99..6f744cae023 100644 --- a/content/rancher/v2.x/en/kubernetes-in-rancher/certificates/_index.md +++ b/content/rancher/v2.x/en/kubernetes-in-rancher/certificates/_index.md @@ -2,7 +2,7 @@ title: SSL Certificates weight: 3060 aliases: - - /rancher/v2.x/en/tasks/projects/add-ssl-certificate/ + - /rancher/v2.x/en/tasks/projects/add-ssl-certificates/ --- When you create an ingress within Rancher/Kubernetes, you must provide it with a secret that includes a TLS private key and certificate, which are used to encrypt and decrypt communications that come through the ingress. You can make certificates available for ingress use by navigating to its project or namespace, and then uploading the certificate. You can then add the certificate to the ingress deployment. diff --git a/content/rancher/v2.x/en/kubernetes-in-rancher/load-balancing-and-ingress/ingress/_index.md b/content/rancher/v2.x/en/kubernetes-in-rancher/load-balancing-and-ingress/ingress/_index.md index 61e7ebda9dc..96b7e71d37b 100644 --- a/content/rancher/v2.x/en/kubernetes-in-rancher/load-balancing-and-ingress/ingress/_index.md +++ b/content/rancher/v2.x/en/kubernetes-in-rancher/load-balancing-and-ingress/ingress/_index.md @@ -1,6 +1,8 @@ --- title: Ingress weight: 3042 +aliases: + - /rancher/v2.x/en/tasks/workloads/add-ingress/ --- Ingress can be added for workloads to provide load balancing, SSL termination and host/path based routing. diff --git a/content/rancher/v2.x/en/kubernetes-in-rancher/projects-and-namespaces/_index.md b/content/rancher/v2.x/en/kubernetes-in-rancher/projects-and-namespaces/_index.md index e94a22b0ed5..316621fed6e 100644 --- a/content/rancher/v2.x/en/kubernetes-in-rancher/projects-and-namespaces/_index.md +++ b/content/rancher/v2.x/en/kubernetes-in-rancher/projects-and-namespaces/_index.md @@ -3,6 +3,8 @@ title: Projects and Namespaces weight: 3020 aliases: - /rancher/v2.x/en/concepts/projects/ + - /rancher/v2.x/en/tasks/projects/ + - /rancher/v2.x/en/tasks/projects/create-project/ --- _Projects_ are a new concept introduced by Rancher. They are not a native Kubernetes construct. A project captures a set of policies for a set of namespaces. A user can be assigned a specific role in a project. A role can be owner, member, read-only, or [custom]({{< baseurl >}}/rancher/v2.x/en/admin-settings/rbac/default-custom-roles/). Policies include Kubernetes Role-Based Access Control (RBAC) policies and pod security policies. Rancher 2.0 also implements a canned network policy that isolates containers in different projects. Future versions of Rancher will implement more flexible network policies. diff --git a/content/rancher/v2.x/en/kubernetes-in-rancher/workloads/add-a-sidecar/_index.md b/content/rancher/v2.x/en/kubernetes-in-rancher/workloads/add-a-sidecar/_index.md index 9ff53474a61..e5c6c4f503e 100644 --- a/content/rancher/v2.x/en/kubernetes-in-rancher/workloads/add-a-sidecar/_index.md +++ b/content/rancher/v2.x/en/kubernetes-in-rancher/workloads/add-a-sidecar/_index.md @@ -2,7 +2,7 @@ title: Adding a Sidecar weight: 3029 aliases: - - /rancher/v2.x/en/concepts/workloads/add-a-sidecar/ + - /rancher/v2.x/en/tasks/workloads/add-a-sidecar/ --- A _sidecar_ is a container that extends or enhances the main container in a pod. The main container and the sidecar share a pod, and therefore share the same network space and storage. You can add sidecars to existing workloads by using the **Add a Sidecar** option. diff --git a/content/rancher/v2.x/en/kubernetes-in-rancher/workloads/deploy-workloads/_index.md b/content/rancher/v2.x/en/kubernetes-in-rancher/workloads/deploy-workloads/_index.md index dacbb0616ed..8cf3dfd3ea9 100644 --- a/content/rancher/v2.x/en/kubernetes-in-rancher/workloads/deploy-workloads/_index.md +++ b/content/rancher/v2.x/en/kubernetes-in-rancher/workloads/deploy-workloads/_index.md @@ -2,7 +2,7 @@ title: Deploying Workloads weight: 3026 aliases: - - /rancher/v2.x/en/concepts/workloads/deploy-workloads/ + - /rancher/v2.x/en/tasks/workloads/deploy-workloads/ --- Deploy a workload to run an application in one or more containers. diff --git a/content/rancher/v2.x/en/kubernetes-in-rancher/workloads/rollback-workloads/_index.md b/content/rancher/v2.x/en/kubernetes-in-rancher/workloads/rollback-workloads/_index.md index 431711c16f8..a10bcea6ebd 100644 --- a/content/rancher/v2.x/en/kubernetes-in-rancher/workloads/rollback-workloads/_index.md +++ b/content/rancher/v2.x/en/kubernetes-in-rancher/workloads/rollback-workloads/_index.md @@ -2,7 +2,7 @@ title: Rolling Back Workloads weight: 3027 aliases: - - /rancher/v2.x/en/concepts/workloads/rollback-workloads/ + - /rancher/v2.x/en/tasks/workloads/rollback-workloads/ --- Sometimes there is a need to rollback to the previous version of the application, either for debugging purposes or because an upgrade did not go as planned. diff --git a/content/rancher/v2.x/en/kubernetes-in-rancher/workloads/upgrade-workloads/_index.md b/content/rancher/v2.x/en/kubernetes-in-rancher/workloads/upgrade-workloads/_index.md index ef46dfc6bb1..c00c15e0a97 100644 --- a/content/rancher/v2.x/en/kubernetes-in-rancher/workloads/upgrade-workloads/_index.md +++ b/content/rancher/v2.x/en/kubernetes-in-rancher/workloads/upgrade-workloads/_index.md @@ -2,7 +2,7 @@ title: Upgrading Workloads weight: 3028 aliases: - - /rancher/v2.x/en/concepts/workloads/upgrade-workloads/ + - /rancher/v2.x/en/tasks/workloads/upgrade-workloads/ --- When a new version of an application image is released on Docker Hub, you can upgrade any workloads running a previous version of the application to the new one.