Upgrading and rolling back releases in Kubernetes - Time & Space Complexity

Time Complexity: Upgrading and rolling back releases

O(n)

Understanding Time Complexity

When upgrading or rolling back releases in Kubernetes, it's important to understand how the time taken grows as the number of resources changes.

We want to know how the process scales when many components are involved.

Scenario Under Consideration

Analyze the time complexity of the following Helm upgrade and rollback commands.

helm upgrade myapp ./mychart --install
helm rollback myapp 2
    

This code upgrades a release named 'myapp' or installs it if missing, and rolls back to revision 2 if needed.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Applying or reverting changes to each Kubernetes resource in the release.
• How many times: Once per resource in the release, which can be many depending on the app size.

How Execution Grows With Input

The time to upgrade or rollback grows roughly in proportion to the number of resources managed.

Input Size (n)	Approx. Operations
10	About 10 resource updates
100	About 100 resource updates
1000	About 1000 resource updates

Pattern observation: The time grows linearly as the number of resources increases.

Final Time Complexity

Time Complexity: O(n)

This means the time to upgrade or rollback grows directly with the number of resources involved.

Common Mistake

[X] Wrong: "Upgrading or rolling back always takes the same time regardless of release size."

[OK] Correct: The process must handle each resource, so more resources mean more work and longer time.

Interview Connect

Understanding how upgrade and rollback times grow helps you plan deployments and troubleshoot delays calmly and confidently.

Self-Check

"What if the release includes many dependent resources that must update in sequence? How would that affect the time complexity?"

Practice

1. What is the primary purpose of the helm upgrade command in Kubernetes?

easy

A. To create a new Helm release from scratch

B. To delete a Helm release from the cluster

C. To update an existing Helm release with a new version of the application

D. To list all Helm releases in the cluster

Solution

1. Step 1: Understand the role of helm upgrade

   This command is used to update an existing release with new chart or configuration changes.

2. Step 2: Differentiate from other Helm commands

   Unlike helm install which creates new releases, helm upgrade modifies existing ones.

3. Final Answer:

   To update an existing Helm release with a new version of the application -> Option C

4. Quick Check:

   Upgrade means update existing release [OK]

Hint: Upgrade means update existing release, not create or delete [OK]

Common Mistakes:

• Confusing upgrade with install
• Thinking upgrade deletes releases
• Assuming upgrade lists releases

2. Which of the following is the correct syntax to rollback a Helm release named myapp to revision 2?

easy

A. helm upgrade myapp --revision=2

B. helm rollback myapp 2

C. helm rollback --release myapp --rev 2

D. helm revert myapp 2

Solution

1. Step 1: Recall Helm rollback syntax

   The correct command is helm rollback RELEASE_NAME REVISION.

2. Step 2: Match syntax with options

   helm rollback myapp 2 matches the correct syntax exactly: helm rollback myapp 2.

3. Final Answer:

   helm rollback myapp 2 -> Option B

4. Quick Check:

   Rollback syntax is helm rollback name revision [OK]

Hint: Rollback uses: helm rollback release_name revision_number [OK]

Common Mistakes:

• Using helm upgrade instead of rollback
• Using incorrect flags like --revision
• Using nonexistent command 'helm revert'

3. Given the following commands executed in order:

helm install myapp ./chart
helm upgrade myapp ./chart --set image.tag=v2
helm rollback myapp 1
helm status myapp

What will be the image tag shown in the status output after the rollback?

medium

A. No image tag shown

B. v2 (tag set during upgrade)

C. v3 (latest tag automatically applied)

D. v1 (original tag from install)

Solution

1. Step 1: Understand the sequence of commands

   First, the app is installed with default image tag (assumed v1). Then upgraded to tag v2. Then rolled back to revision 1 (the original install).

2. Step 2: Determine image tag after rollback

   Rollback to revision 1 restores the original state, so image tag reverts to v1.

3. Final Answer:

   v1 (original tag from install) -> Option D

4. Quick Check:

   Rollback restores previous revision state [OK]

Hint: Rollback returns to previous revision state, undoing upgrades [OK]

Common Mistakes:

• Assuming rollback keeps upgraded tag
• Thinking rollback applies latest tag automatically
• Ignoring rollback effect on release state

4. You ran helm upgrade myapp ./chart --set replicas=3 but the number of pods did not change. What is the most likely cause?

medium

A. The chart does not use the replicas value to set pod count

B. You forgot to run helm rollback first

C. The helm upgrade command syntax is incorrect

D. The Kubernetes cluster is down

Solution

1. Step 1: Check if the chart supports the replicas value

   Not all charts use the replicas parameter; if the chart template ignores it, no change occurs.

2. Step 2: Rule out other causes

   Syntax is correct, rollback is unrelated, and cluster down would cause more errors.

3. Final Answer:

   The chart does not use the replicas value to set pod count -> Option A

4. Quick Check:

   Chart must support value for upgrade to affect it [OK]

Hint: Check if chart templates use your set values before expecting changes [OK]

Common Mistakes:

• Assuming all charts respond to replicas value
• Confusing rollback with upgrade necessity
• Blaming syntax when command is correct

5. You want to upgrade your Helm release webapp to version 3 of your chart but keep the previous configuration values intact except for changing the image tag to v3. Which command achieves this safely?

hard

A. helm upgrade webapp ./chart --reuse-values --set image.tag=v3

B. helm upgrade webapp ./chart --reset-values --set image.tag=v3

C. helm upgrade webapp ./chart --set image.tag=v3

D. helm rollback webapp 3 --set image.tag=v3

Solution

1. Step 1: Understand --reuse-values option

   This option keeps existing values from the previous release and applies new overrides.

2. Step 2: Compare with other options

   --reset-values resets to chart defaults, losing previous config. Omitting reuse-values loses previous config. Rollback does not upgrade.

3. Final Answer:

   helm upgrade webapp ./chart --reuse-values --set image.tag=v3 -> Option A

4. Quick Check:

   Use --reuse-values to keep old config and override selectively [OK]

Hint: Use --reuse-values with --set to keep config and update specific values [OK]

Common Mistakes:

• Using --reset-values and losing config
• Not using --reuse-values and losing previous settings
• Trying rollback to upgrade