Resource name constraints (4) (#19121)

xref: #17969, #19099, #18746
2020-03-05 11:28:38 -08:00
parent 066b9f3b8c
commit 6635262bbc
10 changed files with 36 additions and 7 deletions
@@ -37,6 +37,9 @@ Resource quotas work like this:
  the `LimitRanger` admission controller to force defaults for pods that make no compute resource requirements.
  See the [walkthrough](/docs/tasks/administer-cluster/quota-memory-cpu-namespace/) for an example of how to avoid this problem.

+The name of a `ResourceQuota` object must be a valid
+[DNS subdomain name](/docs/concepts/overview/working-with-objects/names#dns-subdomain-names).
+
 Examples of policies that could be created using namespaces and quotas are:

 - In a cluster with a capacity of 32 GiB RAM, and 16 cores, let team A use 20 GiB and 10 cores,