Repair Helm values through the rendered resource graph
A hands-on CKA lab. You produce the real artefact and 7 automated checks verify it behaves the way the exam expects.
- Certification
- CKA
- Format
- Artifact workspace
- Difficulty
- hard
- Estimated time
- 35 min
- Automated checks
- 7
The brief
Repair values.yaml for the fixed ledger-chart@1, release ledger in billing. Edit values, not rendered resources. Defaults are replicaCount:2; image repository example.invalid/ledger, tag:'2.1', digest:''; podLabels:{}; containerPort:8080 and containerPortName:http; service type:ClusterIP, port:80, targetPort:http, selector app.kubernetes.io/name:ledger and app.kubernetes.io/instance:ledger; config create:true, existingName:ledger-shared, data LEDGER_ID:primary and WRITE_MODE:append. Recursive map merging retains omitted defaults; null removes a default key. Required resulting keys and real string/boolean/integer types must remain valid; quote numeric-looking image tags. Preserve two to five replicas, the original image identity and ClusterIP entry TCP80. Both example.invalid/ledger:2.1 and example.invalid/ledger@sha256:eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee are accepted image identities. The process is independently observed listening on TCP8080. A named target resolves through containerPortName/containerPort; a numeric target is the actual destination. A changed port declaration cannot start a different listener. The Deployment selector always uses the two default app labels. podLabels overlays its Pod template labels; the Service's coalesced selector must select those Pods. config.create:true renders ledger-config; false references existingName. Existing ledger-shared contains primary/append; ledger-shadow contains archive/read-only. Both environment keys must resolve to primary/append. Either create the correct ConfigMap with named routing and tag identity, or reuse ledger-shared with numeric routing and the digest identity. Inspect the coalesced values, rendered resources and actual graph consequences; repair a newly visible configuration mistake without Reset.
What the checks verify
Your work is graded on 7 independent properties, not on matching one reference answer.
- Coalesced values retain every required chart field with the selected real API-compatible types.
- The rendered container image preserves one independently accepted original image identity.
- The rendered Deployment preserves at least two desired replicas.
- The rendered Deployment selector matches its Pod template and the nonempty Service selector selects that population.
- The selected population receives TCP80 through a target that resolves to its independently observed TCP8080 listener.
- Both rendered environment references consume the observed primary/append configuration from a created or existing ConfigMap.
- The rendered entry point retains the original ClusterIP exposure.
Where this sits in the CKA blueprint
- Domain
- Cluster Architecture, Installation and Configuration
- Objective
- Helm and Kustomize
- Skill
- Rendering and Release Configuration
Part of CKA preparation
Labs are written by ExamNova to teach the decisions the exam tests. They are not reproductions of vendor lab content.