Creating custom namespaces in Kubernetes - Performance & Efficiency

Time Complexity: Creating custom namespaces

O(n)

Understanding Time Complexity

When creating custom namespaces in Kubernetes, it's important to understand how the time to create them grows as you add more namespaces.

We want to know how the work needed changes when the number of namespaces increases.

Scenario Under Consideration

Analyze the time complexity of the following Kubernetes YAML for creating a namespace.

apiVersion: v1
kind: Namespace
metadata:
  name: custom-namespace

This code creates one custom namespace named "custom-namespace" in the cluster.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Creating a single namespace resource.
• How many times: Once per YAML application.

How Execution Grows With Input

Each namespace creation is a separate operation. If you create more namespaces, the total work grows directly with the number of namespaces.

Input Size (n)	Approx. Operations
10	10 namespace creations
100	100 namespace creations
1000	1000 namespace creations

Pattern observation: The work grows linearly as you add more namespaces.

Final Time Complexity

Time Complexity: O(n)

This means the time to create namespaces grows directly in proportion to how many you create.

Common Mistake

[X] Wrong: "Creating multiple namespaces happens all at once, so time stays the same no matter how many."

[OK] Correct: Each namespace creation is a separate action that takes time, so more namespaces mean more total time.

Interview Connect

Understanding how operations scale helps you plan and manage Kubernetes resources efficiently, a useful skill in real projects and discussions.

Self-Check

"What if we created namespaces using a batch process or script that applies all at once? How would the time complexity change?"

Practice

1. What is the main purpose of creating a custom namespace in Kubernetes?

easy

A. To increase the number of nodes in the cluster

B. To group and isolate resources for better organization

C. To speed up container image downloads

D. To automatically update all pods

Solution

1. Step 1: Understand Kubernetes namespaces

   Namespaces help organize and isolate resources within the same cluster.

2. Step 2: Identify the purpose of custom namespaces

   Custom namespaces separate projects, teams, or environments for clarity and management.

3. Final Answer:

   To group and isolate resources for better organization -> Option B

4. Quick Check:

   Namespaces = Organize resources [OK]

Hint: Namespaces isolate resources logically, not physically [OK]

Common Mistakes:

• Thinking namespaces add nodes
• Confusing namespaces with pods
• Believing namespaces speed up downloads

2. Which YAML snippet correctly defines a custom namespace named dev-team?

easy

A. apiVersion: v1\nkind: Namespace\nmetadata:\n name: dev-team

B. apiVersion: v1\nkind: Pod\nmetadata:\n name: dev-team

C. apiVersion: apps/v1\nkind: Namespace\nmetadata:\n name: dev-team

D. apiVersion: v1\nkind: Service\nmetadata:\n name: dev-team

Solution

1. Step 1: Identify correct apiVersion and kind for namespace

   The correct apiVersion is 'v1' and kind is 'Namespace' for creating namespaces.

2. Step 2: Check metadata name field

   The metadata name must be the desired namespace name, here 'dev-team'.

3. Final Answer:

   apiVersion: v1\nkind: Namespace\nmetadata:\n name: dev-team -> Option A

4. Quick Check:

   Namespace YAML = apiVersion v1 + kind Namespace [OK]

Hint: Namespace kind is always 'Namespace' with apiVersion 'v1' [OK]

Common Mistakes:

• Using wrong kind like Pod or Service
• Using wrong apiVersion like apps/v1
• Missing metadata name field

3. What will be the output of the command kubectl get namespaces after applying this YAML?

apiVersion: v1
kind: Namespace
metadata:
  name: test-env

medium

A. Only default namespaces are shown, 'test-env' is missing

B. Shows an error: namespace 'test-env' already exists

C. No output, command hangs

D. Lists all namespaces including 'test-env'

Solution

1. Step 1: Apply the namespace YAML

   Applying the YAML creates a new namespace named 'test-env' in the cluster.

2. Step 2: Run 'kubectl get namespaces'

   This command lists all namespaces, including the newly created 'test-env'.

3. Final Answer:

   Lists all namespaces including 'test-env' -> Option D

4. Quick Check:

   kubectl get namespaces shows all namespaces [OK]

Hint: New namespaces appear in 'kubectl get namespaces' output [OK]

Common Mistakes:

• Expecting error if namespace exists (it won't if new)
• Thinking command hangs
• Assuming only default namespaces show

4. You tried to create a namespace with this YAML but got an error:

apiVersion: v1
kind: Namespace
metadata:
  name: 123team

What is the likely cause?

medium

A. Namespace names cannot start with a number

B. apiVersion 'v1' is incorrect for namespaces

C. Missing 'labels' field in metadata

D. Namespace kind should be 'Project'

Solution

1. Step 1: Check namespace naming rules

   Namespace names must start with a letter and contain only lowercase letters, numbers, and dashes.

2. Step 2: Identify invalid name

   The name '123team' starts with a number, which is invalid and causes the error.

3. Final Answer:

   Namespace names cannot start with a number -> Option A

4. Quick Check:

   Namespace name rules forbid starting with digits [OK]

Hint: Namespace names must start with a letter, not a number [OK]

Common Mistakes:

• Thinking apiVersion v1 is wrong
• Believing labels are mandatory
• Using wrong kind like 'Project'

5. You want to create two namespaces, dev and prod, and ensure pods in dev cannot access services in prod. Which approach is best?

hard

A. Create namespaces and use different node pools for each

B. Create namespaces and label pods with 'access=restricted' only

C. Create both namespaces and use NetworkPolicies to restrict access

D. Create namespaces and deploy all pods in the default namespace

Solution

1. Step 1: Create separate namespaces

   Namespaces 'dev' and 'prod' isolate resources logically in the cluster.

2. Step 2: Use NetworkPolicies to control traffic

   NetworkPolicies can restrict pod-to-service communication between namespaces effectively.

3. Final Answer:

   Create both namespaces and use NetworkPolicies to restrict access -> Option C

4. Quick Check:

   Namespaces + NetworkPolicies = access control [OK]

Hint: Use NetworkPolicies with namespaces for access control [OK]

Common Mistakes:

• Assuming labels alone restrict network access
• Deploying all pods in default namespace ignores isolation
• Using node pools does not isolate network traffic