From ad0b8fe39467f297772b4df03bcbf846593a9f90 Mon Sep 17 00:00:00 2001 From: Mark Bishop Date: Wed, 1 Aug 2018 23:06:01 -0700 Subject: [PATCH 1/5] initial draft of project quotas --- .../project-quotas/_index.md | 58 +++++++++++++++++++ 1 file changed, 58 insertions(+) create mode 100644 content/rancher/v2.x/en/k8s-in-rancher/projects-and-namespaces/project-quotas/_index.md diff --git a/content/rancher/v2.x/en/k8s-in-rancher/projects-and-namespaces/project-quotas/_index.md b/content/rancher/v2.x/en/k8s-in-rancher/projects-and-namespaces/project-quotas/_index.md new file mode 100644 index 00000000000..04202695404 --- /dev/null +++ b/content/rancher/v2.x/en/k8s-in-rancher/projects-and-namespaces/project-quotas/_index.md @@ -0,0 +1,58 @@ +--- +title: Project Quotas +weight: 5000 +--- +_Project quotas_ are a Rancher feature that limits the resources available to a project. + +In situations where several teams share a cluster, one team may overconsume the resources available. To prevent this overconsumption, you can apply a _project quota_, which creates a pool of resources that the project's namespaces can use, resources being things like data or processing power. + +## Project Quotas vs. Resource Quotas + +Project quotas, a feature exclusive to Rancher, work similarly to the Kubernetes feature, [Resource Quotas](https://kubernetes.io/docs/concepts/policy/resource-quotas/). The following table explains the key differences between the two quota types. + + +Project Quotas | Resource Quotas +---------|---------- + Applied to projects. | Applied to namespaces. + Creates resource pool for all namespaces in project. | Applies static resource limits to individual namespaces. + Applies resource quotas to namespaces through inheritance. | Apply only to the assigned namespace. + +## Project Quota Resource Pool + +When you create a project quota, you are configuring the pool of resources available to the project. You can set limits on resources like: + +- Memory +- CPU +- Storage +- Kubernetes Resources (i.e., Secrets) + +>**Note:** In the quota, if you set CPU or Memory limit, all containers you create in the namespace must explicitly satisfy the quota. See the [Kubernetes documentation](https://kubernetes.io/docs/concepts/policy/resource-quotas/#requests-vs-limits) for more details. + +## Quota Templates + +When a project quota is in effect, the project assigns each namespace a _quota template_, which is a profile that describes what resources are available to the namespace. + +When you create a project, you have the option of assigning each namespace one of three quota templates: + +- **Small:** the namespace can access minimal resources. +- **Medium:** the namespace can access adequate resources. +- **Large:** the namespace can access performance resources. + +When a project quota is in effect, each namespace must have a quota template assigned to it. You can assign quota templates one of two ways: + +- **Inheritance**: Have Rancher apply a quota template automatically. +- **Direct assignment**: Apply the quota template yourself. + +## Quota Inheritance + +When setting up your project quota, you'll choose a default quota template for the project. Each namespace inherits this quota unless you assign it one directly, which overrides the default. We recommend assigning most quota templates this way. + +>**Note:** When you apply a project quota, any resource quotas already applied to the project namespaces are replaced with the default quota template. + +## Advantages of Project Quotas + +Setting up project quotas instead of resource quotas has benefits: + +- **Fewer Resource Quota Applications:** Instead of applying resource quotas to multiple namespaces, you can apply a single project quota to the entire project. +- **Resource Flexibility:** Quota templates allow you to quickly change the resources available for each namespace rather creating a resource quota from scratch. +- **Quota Template Inheritance:** Resource limits are automatically enforced when the namespace inherits a quote template from the project. Additionally, as new namespaces are created and deleted, the default quota template is automatically applied. From 842efaace32d1cba8b4de8ce702028db5d39ec2a Mon Sep 17 00:00:00 2001 From: MBishop17 Date: Wed, 12 Sep 2018 17:47:19 -0700 Subject: [PATCH 2/5] adding diagrams to help explain resource quotas. --- src/diagrams/kubernetes-resource-quota.xml | 1 + src/diagrams/rancher-resource-quota.xml | 1 + src/img/rancher/kubernetes-resource-quota.svg | 2 ++ src/img/rancher/rancher-resource-quota.svg | 2 ++ 4 files changed, 6 insertions(+) create mode 100644 src/diagrams/kubernetes-resource-quota.xml create mode 100644 src/diagrams/rancher-resource-quota.xml create mode 100644 src/img/rancher/kubernetes-resource-quota.svg create mode 100644 src/img/rancher/rancher-resource-quota.svg diff --git a/src/diagrams/kubernetes-resource-quota.xml b/src/diagrams/kubernetes-resource-quota.xml new file mode 100644 index 00000000000..be4fedb4059 --- /dev/null +++ b/src/diagrams/kubernetes-resource-quota.xml @@ -0,0 +1 @@ +7VjbcpswEP0aHtMBZMf4MSaXzrTppM1k+iyDDJoIRIWwnX59VyBxMZAwqZukM44fwGd3Je3qnN2MLeQn+xuBs/iWh4RZrh3uLXRpua67QB48FPJUIZ5zXgGRoGEFOQ1wT38TDdoaLWhI8o6j5JxJmnXBgKcpCWQHw0LwXddtw1l31wxHpAfcB5j10Z80lLHOYm43+GdCo9js7NjassbBYyR4ker9LBdtyr/KnGCzlvbPYxzyXQtCVxbyBeeyekv2PmGqtqZsVdz1iLU+tyCpnBLgVgFbzApiTnzOIHQV0q06n3zSNTn/VahDrSTZyzPMaJRa6EJdAexEBLyArSx1Ks/y8kKV1fGyfRMLb5F+lnso5/IWGRedTaBsKFSffuw3LOmWQNSXYk1ESiTwxLV9VuTlMaqFIeFq7e5+AJdpGdTtZOiW90ZUZRww72IqyX2GA2XdAc8Bi2XCtLm+OfUl4AkN4F0VIZeCPxK/zgktPH/pX9cWQyhXFYAy1vK07cX8wgNc1/dSFxettkRICvy80AbJM12/a5xQpmSW8SyjKRB/xfCasFXNRLNBylNIZcUhJSpVBLLrKrQZo0mktiT7FqQZdEN4QqR4AhetbqTJvGukMl9qLG7JBBnWYy3PqF6qoSi8aJaOUNwboOzBRaq8s5Es6qaB18bdHqlBP2G9kOkDOn9noACQbb8AzjEKMJR/W07TJUaCjb1xhiSWkLwkPgj4BUmtxYDIuo7PquwfKwrNZsv51aFUBF9zyTXa9nbUZ0h/kcAhJY2z1tIAcbwR3o2qZ9YnjzMbUI93BO4sXuDOQL8/bOj2hIb+ylV+kJwXoqTdd7Dg0neMZn1k6sRiZCPHUwDipwbz7x7A/ytNqKxC52rO28AiRtXQuXvIW6xvR45NnGe1dPwEbknCS65VOajCuzN43NLVqw5+nBMO9owpZfpo81o30KndxfSiidP9r5qLsdoD3WVoNC2OMZqX7z+aoYF/mr/jdDZrvNF4dl9oKafxPMizDp+WH2Y81/96n+bzaT6f5vN/MZ9f2V3eYD7D1+aHpNLW+rUOXf0B \ No newline at end of file diff --git a/src/diagrams/rancher-resource-quota.xml b/src/diagrams/rancher-resource-quota.xml new file mode 100644 index 00000000000..6c87a44b6f5 --- /dev/null +++ b/src/diagrams/rancher-resource-quota.xml @@ -0,0 +1 @@ +7VpLc+MoEP41Ps6UBJYtHWMn2T1splKTmtrZI5awzAwSWoxjZ379gADJ6BFrHDuPKtsHoYYGuvvjo8EewXm2+4ujYnXHEkxHwEt2I3g9AgBMYSgfSvKkJX7kT7Qk5SQxslrwQH5hI/SMdEMSvHYaCsaoIIUrjFme41g4MsQ527rNloy6oxYoxS3BQ4xoW/ovScRKS8PAq+V/Y5Ku7Mi+Z2oWKP6ZcrbJzXgjAJflR1dnyPZl2q9XKGHbPRG8GcE5Z0zoUrabY6qca92m9W57aqt5c5yLIQpAKzwiusF2xhMqVWcJeVTzE0/GJ5P/N2pSM4F34hOiJM1H8EqFQI6EuSzIutLVufi0LgOqav2w2NW6spSaZzmGalxGkTLuDCLdBhP1bet+RXm8Kgec0826HFp3Jo3U/bljSHFpipUCxypQxgorb/iyersiAj8UKFa1WwluKVuJjJrqKlrqJWYZiWVZGb4WnP3E88oOOA3n0fy2qrEgAspoQuleS8+bBlehlBufXhuHwtkj5oJITF6ZCsEK47NblBGq1lbBioLkEuwzihaYzir02QFylktTZkyaRITSgF7lBdU/3vUCx6/gKNc5ZhkW/Ek22dbrIYgMild7a2FslwIyazCtdGscyoKBYjcs4QeG5T1nPxQnXWD5mrA0CjDQGmbjsYS9D1rQAVoITgDaaS9oDaDaqG3C0h8AyyN7+YIyvC4hpGzVPS64rb3GS7Shqvt/SEbEuuyp2ahfMnRVUrwU/QbK6eVWNr//ZiejVQPFK54EGCWK+++/rfeW0r5m3wp7djme3oA7nLESmdoGGRYPjOXjjsyOmvhpZtgO3UA3vTd+wvHSW/pN4uFswQQz0r3WcDyOgpvhbHYCJgqnDhMBMGlRkT/uoKLwBExk02iHihoRlEEpVHFJ8e5KpcxuzBrujiIEUdjhWF99pRzviPhudFX5PxXiz4F6y+Xsv5uIly91nYOM/kiaA4IP/hAzKUcJwfWEzbajfYGT1hmgEVvpL7bhMXboXSCeYhurwylSR4StjGOKBHl0J9EVdjPCPSPlBmCPWeOxi7BJAzl68kZr/wzQ7ChqdOQ3OtImtzoqUViZPQyY/gWYrwHM6E2BCRvUN50cB0xo+dFeI4TB2YDZlbw1gKlS2KJ3ZzBXEWhhm1d3BYNzV+iaKwPS3jJC0I6b7zX8csyeER3IXocfkczW/GwGCg7kY515yh9kJGfOPqp8Ylj2YbmolX08ywOH0o9pN5osejrAc7Z8IzgCPEccS84Mmg+cxr4IMUYjaiPGJrFdu8SLABO+P7qt7nBfhW67HHA+uvUvdPtiuu1J9t+CbicXuv0IdNuDmDeg20PJ3eVq8nI1ebmafGckc7arycg9n/s++Hy+3Uu+1j9n65N5/acBePMb \ No newline at end of file diff --git a/src/img/rancher/kubernetes-resource-quota.svg b/src/img/rancher/kubernetes-resource-quota.svg new file mode 100644 index 00000000000..4b5c4c34434 --- /dev/null +++ b/src/img/rancher/kubernetes-resource-quota.svg @@ -0,0 +1,2 @@ + +
Native Kubernetes Cluster
[Not supported by viewer]
Namespace 1
[Not supported by viewer]
Resource Quota:

CPU Limit: 500 milli CPUs
Memory Limit 1024 MiB

[Not supported by viewer]
Namespace 2
[Not supported by viewer]
Resource Quota:

CPU Limit: 500 milli CPUs
Memory Limit 1024 MiB

[Not supported by viewer] \ No newline at end of file diff --git a/src/img/rancher/rancher-resource-quota.svg b/src/img/rancher/rancher-resource-quota.svg new file mode 100644 index 00000000000..9c191ebb748 --- /dev/null +++ b/src/img/rancher/rancher-resource-quota.svg @@ -0,0 +1,2 @@ + +
Rancher Cluster
[Not supported by viewer]
Rancher Project
[Not supported by viewer]
Resource Quota:



[Not supported by viewer]
Project Limits:

CPU Limit: 2000 milli CPUs
Memory Limit: 2048 MiB
[Not supported by viewer]
Namespace
Default Limits:

CPU Limit: 500 milli CPUs
Memory Limit 1024 MiB

[Not supported by viewer]
Namespace 2
[Not supported by viewer]
Namespace
Default Limit
[Not supported by viewer]
Namespace 1
[Not supported by viewer]
Namespace
Default Limit
[Not supported by viewer] \ No newline at end of file From 31e90784294fbe6267ef99a8565f7e0075f49065 Mon Sep 17 00:00:00 2001 From: MBishop17 Date: Wed, 12 Sep 2018 18:08:00 -0700 Subject: [PATCH 3/5] adding more content --- .../project-quotas/_index.md | 51 +++++++++++++++++++ 1 file changed, 51 insertions(+) diff --git a/content/rancher/v2.x/en/k8s-in-rancher/projects-and-namespaces/project-quotas/_index.md b/content/rancher/v2.x/en/k8s-in-rancher/projects-and-namespaces/project-quotas/_index.md index 04202695404..c3012b81bbf 100644 --- a/content/rancher/v2.x/en/k8s-in-rancher/projects-and-namespaces/project-quotas/_index.md +++ b/content/rancher/v2.x/en/k8s-in-rancher/projects-and-namespaces/project-quotas/_index.md @@ -2,13 +2,52 @@ title: Project Quotas weight: 5000 --- +<<<<<<< HEAD _Project quotas_ are a Rancher feature that limits the resources available to a project. +======= +When you are creating or editing a project, you can configure a _resource quotas_, which is a Rancher feature that limits the resources available to a project and the namespaces within it. +>>>>>>> 9cf3cfa... adding more content In situations where several teams share a cluster, one team may overconsume the resources available. To prevent this overconsumption, you can apply a _project quota_, which creates a pool of resources that the project's namespaces can use, resources being things like data or processing power. ## Project Quotas vs. Resource Quotas +<<<<<<< HEAD Project quotas, a feature exclusive to Rancher, work similarly to the Kubernetes feature, [Resource Quotas](https://kubernetes.io/docs/concepts/policy/resource-quotas/). The following table explains the key differences between the two quota types. +======= +Resource quotas in Rancher work similarly to how they do in the [native version of Kubernetes](https://kubernetes.io/docs/concepts/policy/resource-quotas/). However, Rancher's version of resource quotas have a few key differences from the Kubernetes version. + +In a standard Kubernetes deployment, resource quotas are applied to individual namespaces. However, you cannot apply the quota to multiple namespaces with a single action. Instead, the resource quota must be applied each namespace, which can be tedious. The following diagram depict resource quotas in a native Kubernetes deployment. Notice that: + +- Resource quotas apply only to namespaces they are directly assigned to. +- Quotas are applied to individual namespaces, rather than collectively. + +Native Kubernetes Resource Quota Implementation Example +![Native Kubernetes Resource Quota Implementation]({{< baseurl >}}/img/rancher/kubernetes-resource-quota.svg) + +In Rancher's implementation of resource quotas, the quota is applied to a [project]({{< baseurl >}}/rancher/v2.x/en/k8s-in-rancher/projects-and-namespaces/#projects) instead. The resource quota includes two limits: + +- **Project Limits:** + + This set of values is the overall limit for the project. When the overall limit for the project is exceeded, Kubernetes uses logic to determine which namespaces to stop to get back under the quota. + +- **Namespace Default Limits:** + + This value is the default resource limit that an individual namespace inherits from the project. If an individual namespace exceeds its namespace limit, Kubernetes stops anything objects in the namespace from operating. + + Each namespace inherits this default limit unless you [override it](#namespace-default-limit-overrides). + +The following diagram depict resource quotas in a native Kubernetes deployment. Notice that: + +- The resource quota is applied to the entire project. +- The project limit sets what resources are available for the entire project. +- Each namespace in the project inherits namespace default limit, which sets the cap for resources available for each individual namespace. You don't have to apply it to each namespace. + +Rancher Resource Quota Implementation Example +![Rancher Resource Quota Implementation]({{< baseurl >}}/img/rancher/rancher-resource-quota.svg) + +The following table explains the key differences between the two quota types. +>>>>>>> 9cf3cfa... adding more content Project Quotas | Resource Quotas @@ -19,6 +58,7 @@ Project Quotas | Resource Quotas ## Project Quota Resource Pool +<<<<<<< HEAD When you create a project quota, you are configuring the pool of resources available to the project. You can set limits on resources like: - Memory @@ -27,11 +67,16 @@ When you create a project quota, you are configuring the pool of resources avail - Kubernetes Resources (i.e., Secrets) >**Note:** In the quota, if you set CPU or Memory limit, all containers you create in the namespace must explicitly satisfy the quota. See the [Kubernetes documentation](https://kubernetes.io/docs/concepts/policy/resource-quotas/#requests-vs-limits) for more details. +======= +When you create a resource quota, you are configuring the pool of resources available to the project. You can set limits for a variety of different resources, for both your project and your namespaces. + +>>>>>>> 9cf3cfa... adding more content ## Quota Templates When a project quota is in effect, the project assigns each namespace a _quota template_, which is a profile that describes what resources are available to the namespace. +<<<<<<< HEAD When you create a project, you have the option of assigning each namespace one of three quota templates: - **Small:** the namespace can access minimal resources. @@ -56,3 +101,9 @@ Setting up project quotas instead of resource quotas has benefits: - **Fewer Resource Quota Applications:** Instead of applying resource quotas to multiple namespaces, you can apply a single project quota to the entire project. - **Resource Flexibility:** Quota templates allow you to quickly change the resources available for each namespace rather creating a resource quota from scratch. - **Quota Template Inheritance:** Resource limits are automatically enforced when the namespace inherits a quote template from the project. Additionally, as new namespaces are created and deleted, the default quota template is automatically applied. +======= + +### Namespace Default Limit Overrides + +Although each namespace in a project inherits the **Namespace Default Limit**, you can also override this setting for specific namespaces that require additional (or fewer) resources. +>>>>>>> 9cf3cfa... adding more content From 880ab2c3c025561a7f89c8b060cf0bc527d2bf24 Mon Sep 17 00:00:00 2001 From: Mark Bishop Date: Thu, 13 Sep 2018 10:55:43 -0700 Subject: [PATCH 4/5] clean up --- .../projects-and-namespaces/editing-projects/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rancher/v2.x/en/k8s-in-rancher/projects-and-namespaces/editing-projects/_index.md b/content/rancher/v2.x/en/k8s-in-rancher/projects-and-namespaces/editing-projects/_index.md index a536452b1dd..c2550566348 100644 --- a/content/rancher/v2.x/en/k8s-in-rancher/projects-and-namespaces/editing-projects/_index.md +++ b/content/rancher/v2.x/en/k8s-in-rancher/projects-and-namespaces/editing-projects/_index.md @@ -11,7 +11,7 @@ After projects are created, there are certain aspects that can be changed later. Following project creation, you can add users as project members so that they can access its resources. ->**Ping and MS FS Caveats:** +>**SAML Caveats:** > >- IdP does not support search or lookup. When adding users to projects, the exact IDs must be entered correctly. >- When adding users to a project, group IDs are not supported unless the admin who turned on access control is a member of the group. From 97bafe4eb7884bcd27e26cd85aede8680890102e Mon Sep 17 00:00:00 2001 From: Mark Bishop Date: Thu, 13 Sep 2018 11:16:57 -0700 Subject: [PATCH 5/5] change per denise --- .../editing-projects/_index.md | 2 +- .../project-quotas/_index.md | 60 ++----------------- 2 files changed, 7 insertions(+), 55 deletions(-) diff --git a/content/rancher/v2.x/en/k8s-in-rancher/projects-and-namespaces/editing-projects/_index.md b/content/rancher/v2.x/en/k8s-in-rancher/projects-and-namespaces/editing-projects/_index.md index c2550566348..7050abbbf7b 100644 --- a/content/rancher/v2.x/en/k8s-in-rancher/projects-and-namespaces/editing-projects/_index.md +++ b/content/rancher/v2.x/en/k8s-in-rancher/projects-and-namespaces/editing-projects/_index.md @@ -11,7 +11,7 @@ After projects are created, there are certain aspects that can be changed later. Following project creation, you can add users as project members so that they can access its resources. ->**SAML Caveats:** +>**Ping, Keycloak, and MS FS Caveats:** > >- IdP does not support search or lookup. When adding users to projects, the exact IDs must be entered correctly. >- When adding users to a project, group IDs are not supported unless the admin who turned on access control is a member of the group. diff --git a/content/rancher/v2.x/en/k8s-in-rancher/projects-and-namespaces/project-quotas/_index.md b/content/rancher/v2.x/en/k8s-in-rancher/projects-and-namespaces/project-quotas/_index.md index c3012b81bbf..6d7344b71cd 100644 --- a/content/rancher/v2.x/en/k8s-in-rancher/projects-and-namespaces/project-quotas/_index.md +++ b/content/rancher/v2.x/en/k8s-in-rancher/projects-and-namespaces/project-quotas/_index.md @@ -1,20 +1,17 @@ --- title: Project Quotas weight: 5000 +draft: true --- -<<<<<<< HEAD -_Project quotas_ are a Rancher feature that limits the resources available to a project. -======= + +_Available as of v2.1.0_ + When you are creating or editing a project, you can configure a _resource quotas_, which is a Rancher feature that limits the resources available to a project and the namespaces within it. ->>>>>>> 9cf3cfa... adding more content In situations where several teams share a cluster, one team may overconsume the resources available. To prevent this overconsumption, you can apply a _project quota_, which creates a pool of resources that the project's namespaces can use, resources being things like data or processing power. ## Project Quotas vs. Resource Quotas -<<<<<<< HEAD -Project quotas, a feature exclusive to Rancher, work similarly to the Kubernetes feature, [Resource Quotas](https://kubernetes.io/docs/concepts/policy/resource-quotas/). The following table explains the key differences between the two quota types. -======= Resource quotas in Rancher work similarly to how they do in the [native version of Kubernetes](https://kubernetes.io/docs/concepts/policy/resource-quotas/). However, Rancher's version of resource quotas have a few key differences from the Kubernetes version. In a standard Kubernetes deployment, resource quotas are applied to individual namespaces. However, you cannot apply the quota to multiple namespaces with a single action. Instead, the resource quota must be applied each namespace, which can be tedious. The following diagram depict resource quotas in a native Kubernetes deployment. Notice that: @@ -47,63 +44,18 @@ The following diagram depict resource quotas in a native Kubernetes deployment. ![Rancher Resource Quota Implementation]({{< baseurl >}}/img/rancher/rancher-resource-quota.svg) The following table explains the key differences between the two quota types. ->>>>>>> 9cf3cfa... adding more content - -Project Quotas | Resource Quotas +Rancher Resource Quotas | Native Kubernetes Resource Quotas ---------|---------- Applied to projects. | Applied to namespaces. - Creates resource pool for all namespaces in project. | Applies static resource limits to individual namespaces. + Applies resource limits to the project and all its namespaces. | Applies resource limits to individual namespaces. Applies resource quotas to namespaces through inheritance. | Apply only to the assigned namespace. ## Project Quota Resource Pool -<<<<<<< HEAD -When you create a project quota, you are configuring the pool of resources available to the project. You can set limits on resources like: - -- Memory -- CPU -- Storage -- Kubernetes Resources (i.e., Secrets) - ->**Note:** In the quota, if you set CPU or Memory limit, all containers you create in the namespace must explicitly satisfy the quota. See the [Kubernetes documentation](https://kubernetes.io/docs/concepts/policy/resource-quotas/#requests-vs-limits) for more details. -======= When you create a resource quota, you are configuring the pool of resources available to the project. You can set limits for a variety of different resources, for both your project and your namespaces. ->>>>>>> 9cf3cfa... adding more content - -## Quota Templates - -When a project quota is in effect, the project assigns each namespace a _quota template_, which is a profile that describes what resources are available to the namespace. - -<<<<<<< HEAD -When you create a project, you have the option of assigning each namespace one of three quota templates: - -- **Small:** the namespace can access minimal resources. -- **Medium:** the namespace can access adequate resources. -- **Large:** the namespace can access performance resources. - -When a project quota is in effect, each namespace must have a quota template assigned to it. You can assign quota templates one of two ways: - -- **Inheritance**: Have Rancher apply a quota template automatically. -- **Direct assignment**: Apply the quota template yourself. - -## Quota Inheritance - -When setting up your project quota, you'll choose a default quota template for the project. Each namespace inherits this quota unless you assign it one directly, which overrides the default. We recommend assigning most quota templates this way. - ->**Note:** When you apply a project quota, any resource quotas already applied to the project namespaces are replaced with the default quota template. - -## Advantages of Project Quotas - -Setting up project quotas instead of resource quotas has benefits: - -- **Fewer Resource Quota Applications:** Instead of applying resource quotas to multiple namespaces, you can apply a single project quota to the entire project. -- **Resource Flexibility:** Quota templates allow you to quickly change the resources available for each namespace rather creating a resource quota from scratch. -- **Quota Template Inheritance:** Resource limits are automatically enforced when the namespace inherits a quote template from the project. Additionally, as new namespaces are created and deleted, the default quota template is automatically applied. -======= ### Namespace Default Limit Overrides Although each namespace in a project inherits the **Namespace Default Limit**, you can also override this setting for specific namespaces that require additional (or fewer) resources. ->>>>>>> 9cf3cfa... adding more content