Kubernetes and Cloud Native Associate (KCNA)Cloud Native DeliveryHard
A large enterprise is migrating its legacy applications to a cloud-native platform using Kubernetes. Many of these applications rely on custom, stateful resources that require specific initialization, lifecycle management, and disaster recovery procedures. The enterprise wants to automate these complex operations within Kubernetes itself, rather than relying on external scripts or manual processes. Which Kubernetes extension would provide the most robust and integrated solution for this challenge?
- APod Security Policies
- BIngress Controllers
- CCustom Resource Definitions (CRDs) with an Operator
- DNetwork Policies
Show answer & explanationAnswer & explanation
Correct answer: C. Custom Resource Definitions (CRDs) with an Operator
Custom Resource Definitions (CRDs) allow defining new resource types in Kubernetes, while an Operator provides the control logic to manage the lifecycle of instances of these custom resources, automating complex operational tasks for stateful applications.
Why the other options are wrong
- A. Pod Security Policies enforce security standards on pods, not for managing complex application lifecycles.
- B. Ingress Controllers manage external access to services within a cluster, unrelated to internal application lifecycle management.
- D. Network Policies control network traffic between pods, not for automating application-specific operations.
Operator with CRDs
Kubernetes Operators, built upon Custom Resource Definitions (CRDs), extend the Kubernetes API to automate the management of complex stateful applications by encoding operational knowledge into software.
- CRDs define new API objects for custom resources.
- Operators provide the intelligence to manage these custom resources.
- Automate complex tasks like provisioning, scaling, backup, and recovery.
- Integrate deeply with Kubernetes control plane.
Memory trick: CRDs are blueprints, Operators are the builders for your custom K8s apps.