#Updating Namespaces

#Updating Quotas

Resource Quota

#Updating a Resource Quota by using web console

1. Project Management, and navigate to Namespaces > Namespace List in the left sidebar.

2. Click the target namespace name.

3. Click Actions > Update Quota.

4. Adjust resource quotas (CPU, Memory, Pods, etc.) and click Update.

#Updating a Resource Quota by using new web console

Use the Applications view when you are adjusting namespace governance inside the current project scope.

Entry path and action order:

• Open the current project, then go to Applications > Namespaces.
• Click the target namespace.
• Use Actions to choose Update Quota.

When you update the namespace quota from this view, confirm that:

• the change belongs to a namespace already associated with the current project
• the action order is namespace selection first, then the specific governance action, because cluster and namespace identity stay fixed during update
• the cluster and namespace identity remain fixed while quota values are updated
• the change still fits the project's intended resource governance model

#Updating a Resource Quota by using CLI

Resource Quota YAML file example

# Step 1: Edit the namespace quota
kubectl edit resourcequota <quota-name> -n <namespace-name>

# Step 2: Verify changes
kubectl get resourcequota <quota-name> -n <namespace-name> -o yaml

When you update namespace quota, review whether the remaining project or cluster capacity still supports later workload creation, scheduling, and scaling. Tighter quotas often affect the next rollout or scale-out attempt before they affect already running Pods.

#Updating Container LimitRanges

Limit Range

#Updating a LimitRange by using web console

1. Project Management view, and navigate to Namespaces > Namespace List in the left sidebar.

2. Click the target namespace name.

3. Click Actions > Update Container LimitRange.

4. Adjust container limit range (defaultRequest, default, max) and click Update.

#Updating a LimitRange by using new web console

Use the Applications view when you are adjusting namespace governance inside the current project scope.

Entry path and action order:

• Open the current project, then go to Applications > Namespaces.
• Click the target namespace.
• Use Actions to choose Update Container LimitRange.

When you update the namespace limit range from this view, confirm that:

• the change belongs to a namespace already associated with the current project
• the action order is namespace selection first, then the specific governance action, because cluster and namespace identity stay fixed during update
• the cluster and namespace identity remain fixed while limit range values are updated
• the change still fits the project's intended resource governance model

#Updating a LimitRange by using CLI

Limit Range YAML file example

# Step 1: Edit the LimitRange
kubectl edit limitrange <limitrange-name> -n <namespace-name>

# Step 2: Verify changes
kubectl get limitrange <limitrange-name> -n <namespace-name> -o yaml

Container limit range changes usually matter most for workloads created or recreated after the update. Review how new default requests, default limits, and maximum values will affect later workload forms and admission behavior.

#Updating Pod Security Admission

Pod Security Admission

#Updating a Pod Security Admission by using web console

1. Project Management view, and navigate to Namespaces > Namespace List in the left sidebar.

2. Click the target namespace name.

3. Click Actions > Update Pod Security Admission.

4. Adjust security standard (enforce, audit, warn) and click Update.

#Updating a Pod Security Admission by using new web console

Use the Applications view when you are adjusting namespace governance inside the current project scope.

Entry path and action order:

• Open the current project, then go to Applications > Namespaces.
• Click the target namespace.
• Use Actions to choose Update Pod Security Admission.

When you update the namespace policy from this view, confirm that:

• the change belongs to a namespace already associated with the current project
• the action order is namespace selection first, then the specific governance action, because cluster and namespace identity stay fixed during update
• the cluster and namespace identity remain fixed while policy values are updated
• the change still fits the project's intended resource and security governance model

#Updating a Pod Security Admission by using CLI

Update Pod Security Admission CLI command

Stricter namespace-level security settings can block Pods that rely on elevated privileges, host access, or incompatible security contexts. Review expected workload requirements before tightening the policy.

#Updating a namespace from the Clusters view in the new web console

This page mainly describes the legacy console workflow, but namespace updates in the new web console can start from different views.

#Update from the Clusters view

Use the Clusters view when you are adjusting namespace governance from a concrete cluster.

Entry path and action order:

• Open the target cluster first.
• Go to Namespaces in that cluster context and open the target namespace.
• Use Actions to choose Update, Delete

You can manage the corresponding resources under the namespace in the Resource Quota Tab and LimitRange Tab on the details page.