A Guide to Namespaces and Resource Quotas for Kubernetes Users

Mohmmad SaifMohmmad Saif
2 min read

In Kubernetes, namespaces, and resource quotas are key concepts for managing and organizing resources within a cluster, especially in multi-tenant environments. Here's a detailed explanation of each:

Namespaces

Namespaces provide a way to divide cluster resources between multiple users or teams. They create a scope for names and resources, allowing for better organization and management.

Key Features:

  • Isolation: Resources within a namespace are isolated from those in other namespaces.

  • Scoped Names: Resource names must be unique within a namespace but can be duplicated across namespaces.

  • Resource Management: Useful for managing environments such as development, testing, and production within the same cluster.

Common Commands:

# List all namespaces
kubectl get namespaces

# Create a new namespace
kubectl create namespace <namespace-name>

# Delete a namespace
kubectl delete namespace <namespace-name>

Resource Quotas

Resource Quotas provide constraints that limit resource consumption within a namespace. They ensure that resources are fairly distributed and prevent a single namespace from consuming too many resources.

Key Features:

  • Limit Resource Usage: Set limits on the number of resources (e.g., pods) and compute resources (e.g., CPU, memory) a namespace can use.

  • Prevent Resource Exhaustion: Helps avoid a scenario where a single namespace exhausts cluster resources.

  • Per-Namespace Scope: Quotas apply to individual namespaces and enforce resource usage policies within those namespaces.

Example ResourceQuota YAML Definition:

apiVersion: v1
kind: ResourceQuota
metadata:
  name: example-quota
  namespace: <namespace-name>
spec:
  hard:
    pods: "10"
    requests.cpu: "4"
    requests.memory: "8Gi"
    limits.cpu: "10"
    limits.memory: "16Gi"
    configmaps: "10"
    persistentvolumeclaims: "5"

Common Commands:

# Apply a resource quota
kubectl apply -f <quota-file.yaml>

# List resource quotas in a namespace
kubectl get resourcequotas -n <namespace-name>

# Describe a specific resource quota
kubectl describe resourcequota <quota-name> -n <namespace-name>

Workflow for Setting Up Namespaces and Resource Quotas

  1. Create a Namespace:
kubectl create namespace dev
  1. Define a Resource Quota YAML File:
apiVersion: v1
kind: ResourceQuota
metadata:
  name: dev-quota
  namespace: dev
spec:
  hard:
    pods: "10"
    requests.cpu: "4"
    requests.memory: "8Gi"
    limits.cpu: "10"
    limits.memory: "16Gi"
  1. Apply the Resource Quota:
kubectl apply -f dev-quota.yaml

Benefits

  • Resource Management: Ensures resources are allocated efficiently across different teams or projects.

  • Isolation: Provides logical separation between different environments or projects, reducing the risk of resource conflicts.

  • Control: Allows administrators to set limits and enforce policies, preventing resource overuse and ensuring fair distribution.

By using namespaces and resource quotas, Kubernetes administrators can effectively manage resources in a cluster. This ensures that different teams or projects have the resources they need without interfering with each other, promoting efficient resource usage and maintaining cluster stability.

0
Subscribe to my newsletter

Read articles from Mohmmad Saif directly inside your inbox. Subscribe to the newsletter, and don't miss out.

Written by

Mohmmad Saif
Mohmmad Saif

👋Hello I am Mohd Saif, passionate technology enthusiast currently pursuing a bachelor of Computer application degree. 🎓Education: I am currently pursuing a bachelor of Computer application degree with the focus on coding at Bareilly University my education journey has equipped me with strong foundation in Computer science and I am eager to apply my knowledge to real word challenges. 💡Passion for technology: I have always been deeply passionate about technology and I am particular drawn to devops with AWS. 🚀Skills: 🔹Linux 🔹Shell scripting 🔹Python 🔹Ansible 🔹Docker 🔹Kubernetes 🔹Jenkins CI/CD 🔹Maven 🔹Git and GitHub ✨Future goals: My goal is to facilitate seamless collaboration between development and operations teams, ensuring faster releases and high-quality software. I am a proactive learner, constantly exploring new DevOps trends and practices