Progressive delivery concept in Kubernetes - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the main goal of progressive delivery in Kubernetes?

Progressive delivery is a modern approach in Kubernetes deployments. What is its primary goal?

A To gradually roll out changes to a subset of users to reduce risk

B To deploy all changes immediately to all users for faster updates

C To manually update each pod one by one without automation

D To rollback all changes automatically without monitoring

💡 Hint

Think about how to reduce impact of errors during deployment.

Progressive delivery aims to reduce risk by releasing updates gradually to a small group before full rollout.

💻 Command Output

intermediate

What is the output of this kubectl command for a canary deployment?

Given a deployment with a canary strategy, what does this command output?

Kubernetes

kubectl get pods -l app=myapp,version=canary

A Shows an error because label selector syntax is wrong

B Lists all pods regardless of labels

C Lists pods labeled with app=myapp and version=canary only

D Lists pods labeled with app=myapp but ignores version label

💡 Hint

Check how label selectors filter pods.

The command filters pods with both labels app=myapp and version=canary, showing only canary pods.

🔀 Workflow

advanced

Which step correctly describes a blue-green deployment workflow in Kubernetes?

Choose the correct sequence step for switching traffic in a blue-green deployment.

A Update blue environment and keep traffic on green indefinitely

B Update green environment, switch service to green, then delete blue

C Switch service to blue environment before updating green

D Delete blue environment first, then update green environment

💡 Hint

Think about minimizing downtime and risk during traffic switch.

Blue-green deployment updates the inactive environment (green), switches traffic to it, then removes the old (blue) environment.

❓ Troubleshoot

advanced

Why might a canary deployment not receive any traffic in Kubernetes?

You deployed a canary version but notice no traffic reaches it. What is a likely cause?

A Service selector labels do not match canary pods labels

B Canary pods are running but have no CPU requests set

C The deployment has too many replicas for canary

D The cluster has insufficient nodes for canary pods

💡 Hint

Check how services route traffic to pods.

If service selectors don't match canary pod labels, traffic won't be routed to canary pods.

✅ Best Practice

expert

Which practice best supports progressive delivery in Kubernetes environments?

To implement progressive delivery effectively, which practice is most important?

A Deploy all changes at once to reduce complexity

B Manually check logs after full deployment before rollback

C Avoid using feature flags to keep deployment simple

D Automate monitoring and rollback based on real-time metrics

💡 Hint

Think about how to detect and fix issues quickly during rollout.

Automated monitoring and rollback allow quick response to problems during progressive delivery, reducing risk.