#420 - Canonical links for manage-projects (#810)

* canonicized manage-project-resource-quotas * canonicized manage-projects
rancher · Aug 25, 2023 · f7557d8 · f7557d8
1 parent ac655e3
commit f7557d8
Show file tree

Hide file tree

Showing 25 changed files with 100 additions and 0 deletions.
diff --git a/...-to-guides/advanced-user-guides/manage-projects/manage-pod-security-policies.md b/...-to-guides/advanced-user-guides/manage-projects/manage-pod-security-policies.md
@@ -2,6 +2,10 @@
 title: Pod Security Policies
 ---
 
+<head>
+  <link rel="canonical" href="https://ranchermanager.docs.rancher.com/how-to-guides/advanced-user-guides/manage-projects/manage-pod-security-policies"/>
+</head>
+
 :::note
 
 These cluster options are only available for [clusters in which Rancher has launched Kubernetes](../../../pages-for-subheaders/launch-kubernetes-with-rancher.md).

diff --git a/...manage-projects/manage-project-resource-quotas/about-project-resource-quotas.md b/...manage-projects/manage-project-resource-quotas/about-project-resource-quotas.md
@@ -2,6 +2,10 @@
 title: How Resource Quotas Work in Rancher Projects
 ---
 
+<head>
+  <link rel="canonical" href="https://ranchermanager.docs.rancher.com/how-to-guides/advanced-user-guides/manage-projects/manage-project-resource-quotas/about-project-resource-quotas"/>
+</head>
+
 Resource quotas in Rancher include the same functionality as the [native version of Kubernetes](https://kubernetes.io/docs/concepts/policy/resource-quotas/). However, in Rancher, resource quotas have been extended so that you can apply them to projects.
 
 In a standard Kubernetes deployment, resource quotas are applied to individual namespaces. However, you cannot apply the quota to your namespaces simultaneously with a single action. Instead, the resource quota must be applied multiple times.

diff --git a/...projects/manage-project-resource-quotas/override-default-limit-in-namespaces.md b/...projects/manage-project-resource-quotas/override-default-limit-in-namespaces.md
@@ -2,6 +2,10 @@
 title: Overriding the Default Limit for a Namespace
 ---
 
+<head>
+  <link rel="canonical" href="https://ranchermanager.docs.rancher.com/how-to-guides/advanced-user-guides/manage-projects/manage-project-resource-quotas/override-default-limit-in-namespaces"/>
+</head>
+
 Although the **Namespace Default Limit** propagates from the project to each namespace when created, in some cases, you may need to increase (or decrease) the quotas for a specific namespace. In this situation, you can override the default limits by editing the namespace.
 
 In the diagram below, the Rancher administrator has a resource quota in effect for their project. However, the administrator wants to override the namespace limits for `Namespace 3` so that it has more resources available. Therefore, the administrator [raises the namespace limits](../../../new-user-guides/manage-clusters/projects-and-namespaces.md) for `Namespace 3` so that the namespace can access more resources.

diff --git a/...r-guides/manage-projects/manage-project-resource-quotas/resource-quota-types.md b/...r-guides/manage-projects/manage-project-resource-quotas/resource-quota-types.md
@@ -2,6 +2,10 @@
 title: Resource Quota Type Reference
 ---
 
+<head>
+  <link rel="canonical" href="https://ranchermanager.docs.rancher.com/how-to-guides/advanced-user-guides/manage-projects/manage-project-resource-quotas/resource-quota-types"/>
+</head>
+
 When you create a resource quota, you are configuring the pool of resources available to the project. You can set the following resource limits for the following resource types.
 
 | Resource Type            | Description                                                                                                                                                                                       |

diff --git a/...rojects/manage-project-resource-quotas/set-container-default-resource-limits.md b/...rojects/manage-project-resource-quotas/set-container-default-resource-limits.md
@@ -2,6 +2,10 @@
 title: Setting Container Default Resource Limits
 ---
 
+<head>
+  <link rel="canonical" href="https://ranchermanager.docs.rancher.com/how-to-guides/advanced-user-guides/manage-projects/manage-project-resource-quotas/set-container-default-resource-limits"/>
+</head>
+
 When setting resource quotas, if you set anything related to CPU or Memory (i.e. limits or reservations) on a project / namespace, all containers will require a respective CPU or Memory field set during creation. See the [Kubernetes documentation](https://kubernetes.io/docs/concepts/policy/resource-quotas/#requests-vs-limits) for more details on why this is required.
 
 To avoid setting these limits on each and every container during workload creation, a default container resource limit can be specified on the namespace.

diff --git a/...-to-guides/advanced-user-guides/manage-projects/manage-pod-security-policies.md b/...-to-guides/advanced-user-guides/manage-projects/manage-pod-security-policies.md
@@ -2,6 +2,10 @@
 title: Pod Security Policies
 ---
 
+<head>
+  <link rel="canonical" href="https://ranchermanager.docs.rancher.com/how-to-guides/advanced-user-guides/manage-projects/manage-pod-security-policies"/>
+</head>
+
 > These cluster options are only available for [clusters in which Rancher has launched Kubernetes](../../../pages-for-subheaders/launch-kubernetes-with-rancher.md).
 
 You can always assign a pod security policy (PSP) to an existing project if you didn't assign one during creation.

diff --git a/...manage-projects/manage-project-resource-quotas/about-project-resource-quotas.md b/...manage-projects/manage-project-resource-quotas/about-project-resource-quotas.md
@@ -2,6 +2,10 @@
 title: How Resource Quotas Work in Rancher Projects
 ---
 
+<head>
+  <link rel="canonical" href="https://ranchermanager.docs.rancher.com/how-to-guides/advanced-user-guides/manage-projects/manage-project-resource-quotas/about-project-resource-quotas"/>
+</head>
+
 Resource quotas in Rancher include the same functionality as the [native version of Kubernetes](https://kubernetes.io/docs/concepts/policy/resource-quotas/). However, in Rancher, resource quotas have been extended so that you can apply them to projects.
 
 In a standard Kubernetes deployment, resource quotas are applied to individual namespaces. However, you cannot apply the quota to your namespaces simultaneously with a single action. Instead, the resource quota must be applied multiple times.

diff --git a/...projects/manage-project-resource-quotas/override-default-limit-in-namespaces.md b/...projects/manage-project-resource-quotas/override-default-limit-in-namespaces.md
@@ -2,6 +2,10 @@
 title: Overriding the Default Limit for a Namespace
 ---
 
+<head>
+  <link rel="canonical" href="https://ranchermanager.docs.rancher.com/how-to-guides/advanced-user-guides/manage-projects/manage-project-resource-quotas/override-default-limit-in-namespaces"/>
+</head>
+
 Although the **Namespace Default Limit** propagates from the project to each namespace when created, in some cases, you may need to increase (or decrease) the quotas for a specific namespace. In this situation, you can override the default limits by editing the namespace.
 
 In the diagram below, the Rancher administrator has a resource quota in effect for their project. However, the administrator wants to override the namespace limits for `Namespace 3` so that it has more resources available. Therefore, the administrator [raises the namespace limits](../../manage-clusters/projects-and-namespaces.md) for `Namespace 3` so that the namespace can access more resources.

diff --git a/...r-guides/manage-projects/manage-project-resource-quotas/resource-quota-types.md b/...r-guides/manage-projects/manage-project-resource-quotas/resource-quota-types.md
@@ -2,6 +2,10 @@
 title: Resource Quota Type Reference
 ---
 
+<head>
+  <link rel="canonical" href="https://ranchermanager.docs.rancher.com/how-to-guides/advanced-user-guides/manage-projects/manage-project-resource-quotas/resource-quota-types"/>
+</head>
+
 When you create a resource quota, you are configuring the pool of resources available to the project. You can set the following resource limits for the following resource types.
 
 | Resource Type            | Description                                                                                                                                                                                       |

diff --git a/...rojects/manage-project-resource-quotas/set-container-default-resource-limits.md b/...rojects/manage-project-resource-quotas/set-container-default-resource-limits.md
@@ -2,6 +2,10 @@
 title: Setting Container Default Resource Limits
 ---
 
+<head>
+  <link rel="canonical" href="https://ranchermanager.docs.rancher.com/how-to-guides/advanced-user-guides/manage-projects/manage-project-resource-quotas/set-container-default-resource-limits"/>
+</head>
+
 _Available as of v2.2.0_
 
 When setting resource quotas, if you set anything related to CPU or Memory (i.e. limits or reservations) on a project / namespace, all containers will require a respective CPU or Memory field set during creation. See the [Kubernetes documentation](https://kubernetes.io/docs/concepts/policy/resource-quotas/#requests-vs-limits) for more details on why this is required.

diff --git a/...-to-guides/advanced-user-guides/manage-projects/manage-pod-security-policies.md b/...-to-guides/advanced-user-guides/manage-projects/manage-pod-security-policies.md
@@ -2,6 +2,10 @@
 title: Pod Security Policies
 ---
 
+<head>
+  <link rel="canonical" href="https://ranchermanager.docs.rancher.com/how-to-guides/advanced-user-guides/manage-projects/manage-pod-security-policies"/>
+</head>
+
 > These cluster options are only available for [clusters in which Rancher has launched Kubernetes](../../../pages-for-subheaders/launch-kubernetes-with-rancher.md).
 
 You can always assign a pod security policy (PSP) to an existing project if you didn't assign one during creation.

diff --git a/...manage-projects/manage-project-resource-quotas/about-project-resource-quotas.md b/...manage-projects/manage-project-resource-quotas/about-project-resource-quotas.md
@@ -2,6 +2,10 @@
 title: How Resource Quotas Work in Rancher Projects
 ---
 
+<head>
+  <link rel="canonical" href="https://ranchermanager.docs.rancher.com/how-to-guides/advanced-user-guides/manage-projects/manage-project-resource-quotas/about-project-resource-quotas"/>
+</head>
+
 Resource quotas in Rancher include the same functionality as the [native version of Kubernetes](https://kubernetes.io/docs/concepts/policy/resource-quotas/). However, in Rancher, resource quotas have been extended so that you can apply them to projects.
 
 In a standard Kubernetes deployment, resource quotas are applied to individual namespaces. However, you cannot apply the quota to your namespaces simultaneously with a single action. Instead, the resource quota must be applied multiple times.

diff --git a/...projects/manage-project-resource-quotas/override-default-limit-in-namespaces.md b/...projects/manage-project-resource-quotas/override-default-limit-in-namespaces.md
@@ -2,6 +2,10 @@
 title: Overriding the Default Limit for a Namespace
 ---
 
+<head>
+  <link rel="canonical" href="https://ranchermanager.docs.rancher.com/how-to-guides/advanced-user-guides/manage-projects/manage-project-resource-quotas/override-default-limit-in-namespaces"/>
+</head>
+
 Although the **Namespace Default Limit** propagates from the project to each namespace when created, in some cases, you may need to increase (or decrease) the quotas for a specific namespace. In this situation, you can override the default limits by editing the namespace.
 
 In the diagram below, the Rancher administrator has a resource quota in effect for their project. However, the administrator wants to override the namespace limits for `Namespace 3` so that it has more resources available. Therefore, the administrator [raises the namespace limits](../../manage-clusters/projects-and-namespaces.md) for `Namespace 3` so that the namespace can access more resources.

diff --git a/...r-guides/manage-projects/manage-project-resource-quotas/resource-quota-types.md b/...r-guides/manage-projects/manage-project-resource-quotas/resource-quota-types.md
@@ -2,6 +2,10 @@
 title: Resource Quota Type Reference
 ---
 
+<head>
+  <link rel="canonical" href="https://ranchermanager.docs.rancher.com/how-to-guides/advanced-user-guides/manage-projects/manage-project-resource-quotas/resource-quota-types"/>
+</head>
+
 When you create a resource quota, you are configuring the pool of resources available to the project. You can set the following resource limits for the following resource types.
 
 | Resource Type            | Description                                                                                                                                                                                       |

diff --git a/...rojects/manage-project-resource-quotas/set-container-default-resource-limits.md b/...rojects/manage-project-resource-quotas/set-container-default-resource-limits.md
@@ -2,6 +2,10 @@
 title: Setting Container Default Resource Limits
 ---
 
+<head>
+  <link rel="canonical" href="https://ranchermanager.docs.rancher.com/how-to-guides/advanced-user-guides/manage-projects/manage-project-resource-quotas/set-container-default-resource-limits"/>
+</head>
+
 When setting resource quotas, if you set anything related to CPU or Memory (i.e. limits or reservations) on a project / namespace, all containers will require a respective CPU or Memory field set during creation. See the [Kubernetes documentation](https://kubernetes.io/docs/concepts/policy/resource-quotas/#requests-vs-limits) for more details on why this is required.
 
 To avoid setting these limits on each and every container during workload creation, a default container resource limit can be specified on the namespace.

diff --git a/...-to-guides/advanced-user-guides/manage-projects/manage-pod-security-policies.md b/...-to-guides/advanced-user-guides/manage-projects/manage-pod-security-policies.md
@@ -2,6 +2,10 @@
 title: Pod Security Policies
 ---
 
+<head>
+  <link rel="canonical" href="https://ranchermanager.docs.rancher.com/how-to-guides/advanced-user-guides/manage-projects/manage-pod-security-policies"/>
+</head>
+
 :::note
 
 These cluster options are only available for [clusters in which Rancher has launched Kubernetes](../../../pages-for-subheaders/launch-kubernetes-with-rancher.md).

diff --git a/...manage-projects/manage-project-resource-quotas/about-project-resource-quotas.md b/...manage-projects/manage-project-resource-quotas/about-project-resource-quotas.md
@@ -2,6 +2,10 @@
 title: How Resource Quotas Work in Rancher Projects
 ---
 
+<head>
+  <link rel="canonical" href="https://ranchermanager.docs.rancher.com/how-to-guides/advanced-user-guides/manage-projects/manage-project-resource-quotas/about-project-resource-quotas"/>
+</head>
+
 Resource quotas in Rancher include the same functionality as the [native version of Kubernetes](https://kubernetes.io/docs/concepts/policy/resource-quotas/). However, in Rancher, resource quotas have been extended so that you can apply them to projects.
 
 In a standard Kubernetes deployment, resource quotas are applied to individual namespaces. However, you cannot apply the quota to your namespaces simultaneously with a single action. Instead, the resource quota must be applied multiple times.

diff --git a/...projects/manage-project-resource-quotas/override-default-limit-in-namespaces.md b/...projects/manage-project-resource-quotas/override-default-limit-in-namespaces.md
@@ -2,6 +2,10 @@
 title: Overriding the Default Limit for a Namespace
 ---
 
+<head>
+  <link rel="canonical" href="https://ranchermanager.docs.rancher.com/how-to-guides/advanced-user-guides/manage-projects/manage-project-resource-quotas/override-default-limit-in-namespaces"/>
+</head>
+
 Although the **Namespace Default Limit** propagates from the project to each namespace when created, in some cases, you may need to increase (or decrease) the quotas for a specific namespace. In this situation, you can override the default limits by editing the namespace.
 
 In the diagram below, the Rancher administrator has a resource quota in effect for their project. However, the administrator wants to override the namespace limits for `Namespace 3` so that it has more resources available. Therefore, the administrator [raises the namespace limits](../../../new-user-guides/manage-clusters/projects-and-namespaces.md) for `Namespace 3` so that the namespace can access more resources.

diff --git a/...r-guides/manage-projects/manage-project-resource-quotas/resource-quota-types.md b/...r-guides/manage-projects/manage-project-resource-quotas/resource-quota-types.md
@@ -2,6 +2,10 @@
 title: Resource Quota Type Reference
 ---
 
+<head>
+  <link rel="canonical" href="https://ranchermanager.docs.rancher.com/how-to-guides/advanced-user-guides/manage-projects/manage-project-resource-quotas/resource-quota-types"/>
+</head>
+
 When you create a resource quota, you are configuring the pool of resources available to the project. You can set the following resource limits for the following resource types.
 
 | Resource Type            | Description                                                                                                                                                                                       |

diff --git a/...rojects/manage-project-resource-quotas/set-container-default-resource-limits.md b/...rojects/manage-project-resource-quotas/set-container-default-resource-limits.md
@@ -2,6 +2,10 @@
 title: Setting Container Default Resource Limits
 ---
 
+<head>
+  <link rel="canonical" href="https://ranchermanager.docs.rancher.com/how-to-guides/advanced-user-guides/manage-projects/manage-project-resource-quotas/set-container-default-resource-limits"/>
+</head>
+
 When setting resource quotas, if you set anything related to CPU or Memory (i.e. limits or reservations) on a project / namespace, all containers will require a respective CPU or Memory field set during creation. See the [Kubernetes documentation](https://kubernetes.io/docs/concepts/policy/resource-quotas/#requests-vs-limits) for more details on why this is required.
 
 To avoid setting these limits on each and every container during workload creation, a default container resource limit can be specified on the namespace.

diff --git a/...-to-guides/advanced-user-guides/manage-projects/manage-pod-security-policies.md b/...-to-guides/advanced-user-guides/manage-projects/manage-pod-security-policies.md
@@ -2,6 +2,10 @@
 title: Pod Security Policies
 ---
 
+<head>
+  <link rel="canonical" href="https://ranchermanager.docs.rancher.com/how-to-guides/advanced-user-guides/manage-projects/manage-pod-security-policies"/>
+</head>
+
 :::note
 
 These cluster options are only available for [clusters in which Rancher has launched Kubernetes](../../../pages-for-subheaders/launch-kubernetes-with-rancher.md).

diff --git a/...manage-projects/manage-project-resource-quotas/about-project-resource-quotas.md b/...manage-projects/manage-project-resource-quotas/about-project-resource-quotas.md
@@ -2,6 +2,10 @@
 title: How Resource Quotas Work in Rancher Projects
 ---
 
+<head>
+  <link rel="canonical" href="https://ranchermanager.docs.rancher.com/how-to-guides/advanced-user-guides/manage-projects/manage-project-resource-quotas/about-project-resource-quotas"/>
+</head>
+
 Resource quotas in Rancher include the same functionality as the [native version of Kubernetes](https://kubernetes.io/docs/concepts/policy/resource-quotas/). However, in Rancher, resource quotas have been extended so that you can apply them to projects.
 
 In a standard Kubernetes deployment, resource quotas are applied to individual namespaces. However, you cannot apply the quota to your namespaces simultaneously with a single action. Instead, the resource quota must be applied multiple times.

diff --git a/...projects/manage-project-resource-quotas/override-default-limit-in-namespaces.md b/...projects/manage-project-resource-quotas/override-default-limit-in-namespaces.md
@@ -2,6 +2,10 @@
 title: Overriding the Default Limit for a Namespace
 ---
 
+<head>
+  <link rel="canonical" href="https://ranchermanager.docs.rancher.com/how-to-guides/advanced-user-guides/manage-projects/manage-project-resource-quotas/override-default-limit-in-namespaces"/>
+</head>
+
 Although the **Namespace Default Limit** propagates from the project to each namespace when created, in some cases, you may need to increase (or decrease) the quotas for a specific namespace. In this situation, you can override the default limits by editing the namespace.
 
 In the diagram below, the Rancher administrator has a resource quota in effect for their project. However, the administrator wants to override the namespace limits for `Namespace 3` so that it has more resources available. Therefore, the administrator [raises the namespace limits](../../../new-user-guides/manage-clusters/projects-and-namespaces.md) for `Namespace 3` so that the namespace can access more resources.

diff --git a/...r-guides/manage-projects/manage-project-resource-quotas/resource-quota-types.md b/...r-guides/manage-projects/manage-project-resource-quotas/resource-quota-types.md
@@ -2,6 +2,10 @@
 title: Resource Quota Type Reference
 ---
 
+<head>
+  <link rel="canonical" href="https://ranchermanager.docs.rancher.com/how-to-guides/advanced-user-guides/manage-projects/manage-project-resource-quotas/resource-quota-types"/>
+</head>
+
 When you create a resource quota, you are configuring the pool of resources available to the project. You can set the following resource limits for the following resource types.
 
 | Resource Type            | Description                                                                                                                                                                                       |

diff --git a/...rojects/manage-project-resource-quotas/set-container-default-resource-limits.md b/...rojects/manage-project-resource-quotas/set-container-default-resource-limits.md
@@ -2,6 +2,10 @@
 title: Setting Container Default Resource Limits
 ---
 
+<head>
+  <link rel="canonical" href="https://ranchermanager.docs.rancher.com/how-to-guides/advanced-user-guides/manage-projects/manage-project-resource-quotas/set-container-default-resource-limits"/>
+</head>
+
 When setting resource quotas, if you set anything related to CPU or Memory (i.e. limits or reservations) on a project / namespace, all containers will require a respective CPU or Memory field set during creation. See the [Kubernetes documentation](https://kubernetes.io/docs/concepts/policy/resource-quotas/#requests-vs-limits) for more details on why this is required.
 
 To avoid setting these limits on each and every container during workload creation, a default container resource limit can be specified on the namespace.
-Original file line number
+Diff line change
@@ Expand Up / @@ -2,6 +2,10 @@ @@
     title: Pod Security Policies
     ---
+    <head>
+      <link rel="canonical" href="https://ranchermanager.docs.rancher.com/how-to-guides/advanced-user-guides/manage-projects/manage-pod-security-policies"/>
+    </head>
     :::note
     These cluster options are only available for [clusters in which Rancher has launched Kubernetes](../../../pages-for-subheaders/launch-kubernetes-with-rancher.md).
@@ Expand Down @@