Kubernetes and Cloud Native Associate (KCNA)Cloud Native DeliveryMedium
A team is designing a CI/CD pipeline for a Kubernetes application. They want to ensure that once the code passes all automated tests and is deemed production-ready, it is automatically deployed to the production environment without any manual intervention. Which stage of the CI/CD pipeline enables this full automation to production?
- AContinuous Deployment
- BContinuous Delivery
- CContinuous Testing
- DContinuous Integration
Show answer & explanationAnswer & explanation
Correct answer: A. Continuous Deployment
Continuous Deployment (CD) extends Continuous Delivery by automatically releasing every change that passes the automated pipeline into production. This eliminates manual intervention for production releases.
Why the other options are wrong
- B. Continuous Delivery ensures code is always ready for release, but deployment to production is still manual.
- C. Continuous Testing is a component of CI/CD, focusing on automated testing throughout the pipeline, not a deployment stage itself.
- D. Continuous Integration focuses on building and testing code, not deployment to production.
Continuous Deployment (CD)
Continuous Deployment is a software release process that uses automated testing to validate if changes are ready for release, and then automatically deploys them to production.
- Automates the entire software release process.
- Requires robust automated testing.
- Eliminates manual intervention for production releases.
Memory trick: CD is when the code smoothly glides into production, no human needed.