Kubeconfig certs

CKA v1.35 · Cluster Architecture, Installation and Configuration (25%) → "Manage role based access control" / "Manage the lifecycle of Kubernetes clusters" ALSO: Troubleshooting (30%) — "Troubleshoot cluster components" Target time: 10 minutes

A kubeconfig for another environment has been dropped at /tmp/kc/config. Do NOT merge it into your own kubeconfig or change your current context. Answer by writing files — the grader reads them, exactly as the exam does.

1. Write every context name in /tmp/kc/config to /tmp/kc/contexts.txt, one per line.
2. Write the name of that file's current-context to /tmp/kc/current.txt.
3. The user of context dev-storage authenticates with a client certificate embedded in the file. Decode it and write the certificate's Subject line (as openssl prints it) to /tmp/kc/user-subject.txt. It must contain the CN.
4. On the control-plane node, find the kube-apiserver's serving certificate and write its expiry line (openssl's notAfter=…) to /tmp/kc/apiserver-expiry.txt.
5. Make prod-ops the current-context of /tmp/kc/config — in THAT file only. Your own kubeconfig's current context must be unchanged.

Node shell: docker exec -it muscle-control-plane bash