Kubernetes and Cloud Native Associate (KCNA)Cloud Native DeliveryHard
A software company uses Kubernetes for its microservices architecture. They have a complex stateful application that requires specialized setup, lifecycle management, and disaster recovery procedures that are beyond standard Kubernetes Deployments. To automate and encapsulate this operational knowledge, which Cloud Native pattern should they implement?
- AA Kubernetes Operator
- BA ConfigMap with startup scripts
- CA Helm chart with pre-install hooks
- DA custom `kubectl` plugin
Show answer & explanationAnswer & explanation
Correct answer: A. A Kubernetes Operator
Kubernetes Operators are applications that extend the Kubernetes API to create, configure, and manage instances of complex applications. They encapsulate human operational knowledge for specific applications, handling stateful logic, upgrades, backups, and more, making them ideal for complex stateful applications.
Why the other options are wrong
- B. ConfigMaps store configuration data, not complex operational automation logic.
- C. Helm charts package applications but don't inherently manage complex stateful operational logic.
- D. Custom `kubectl` plugins provide CLI extensions, not automated application management.
Kubernetes Operator
A method of packaging, deploying, and managing a Kubernetes application. Operators extend the Kubernetes API with custom resources and use custom controllers to automate operational tasks for complex applications.
- Encapsulates human operational knowledge for specific applications.
- Automates lifecycle management, upgrades, and scaling of stateful applications.
- Leverages Custom Resource Definitions (CRDs) and custom controllers.
Memory trick: The Operator is the brain for complex app operations.