SIMULATION Quick Reference ConfigMaps, Documentation Deployments, Namespace You must connect to the correct host . Failure to do so may result in a zero score. [candidate@base]$ $ ssh cka000048b…

Question

Explanation

This task tests your ability to update a Kubernetes ConfigMap that drives NGINX TLS configuration, then trigger a rolling restart so the Deployment picks up the new settings. The core skill is understanding how ConfigMaps are consumed by Pods and how to safely roll those changes into a running workload.

Approach. First, inspect the existing ConfigMap with kubectl -n nginx-static get configmap nginx-config -o yaml to understand the current NGINX SSL/TLS configuration block. You will likely find a ssl_protocols directive that only lists TLSv1.3 (or is missing TLSv1.2). Edit the ConfigMap - either with kubectl -n nginx-static edit configmap nginx-config or by patching it - and change (or add) the directive to ssl_protocols TLSv1.2 TLSv1.3;. Because ConfigMap changes are not automatically propagated to running Pods that mount the file via a volume (and are never propagated at all when used as environment variables), you must trigger a rollout with kubectl -n nginx-static rollout restart deployment/nginx-static. Once the new Pods are Running, validate with curl --tls-max 1.2 https://web.k8s.local - a successful HTTP response confirms TLSv1.2 is now accepted.

Concept tested. Kubernetes ConfigMap lifecycle management and NGINX TLS protocol configuration - specifically: reading and editing a ConfigMap that supplies an nginx.conf snippet, understanding that mounted ConfigMap volumes may require a Pod restart to reflect changes, using kubectl rollout restart to safely cycle a Deployment, and validating TLS protocol support with curl.

Reference. https://kubernetes.io/docs/concepts/configuration/configmap/#mounted-configmaps-are-updated-automatically

No community discussion yet for this question.