From f2bc026f101ed83b14747aa062049971d4ac3514 Mon Sep 17 00:00:00 2001 From: Filinto Duran Date: Mon, 3 Jun 2024 07:31:46 -0500 Subject: [PATCH] minor refactor, try to avoid collission with chart resource name Signed-off-by: Filinto Duran --- .../en/operations/hosting/kubernetes/kubernetes-production.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/daprdocs/content/en/operations/hosting/kubernetes/kubernetes-production.md b/daprdocs/content/en/operations/hosting/kubernetes/kubernetes-production.md index 41764208a88..88855219c1f 100644 --- a/daprdocs/content/en/operations/hosting/kubernetes/kubernetes-production.md +++ b/daprdocs/content/en/operations/hosting/kubernetes/kubernetes-production.md @@ -116,7 +116,7 @@ using the helm `--set global.priorityClassName=system-cluster-critical` argument #### Dapr version < 1.14 -For versions of Dapr < 1.14, it is recommended that you add a `ResourceQuota` to the `dapr-system` namespace to prevent +For versions of Dapr < 1.14, it is recommended that you add a `ResourceQuota` to the dapr control plane namespace to prevent problems scheduling pods [if the cluster has been configured](https://kubernetes.io/docs/concepts/policy/resource-quotas/#limit-priority-class-consumption-by-default ) with limitations on which pods can be assigned these high priority classes. @@ -126,7 +126,7 @@ If you have dapr installed in namespace `dapr-system`, you can create a `Resourc apiVersion: v1 kind: ResourceQuota metadata: - name: system-critical-quota + name: dapr-system-critical-quota namespace: dapr-system spec: scopeSelector: