Using Secrets as mounted volumes in Kubernetes - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Output of pod with secret mounted as volume

You have a Kubernetes pod that mounts a secret as a volume at /etc/secret-volume. The secret contains a key password with value mypassword. What will be the output of cat /etc/secret-volume/password inside the pod?

Kubernetes

kubectl exec pod-secret-volume -- cat /etc/secret-volume/password

A mypassword

B base64 encoded string of mypassword

C Error: file not found

D Empty output

💡 Hint

Secrets mounted as volumes are decoded automatically and stored as plain text files.

When a secret is mounted as a volume, Kubernetes decodes the base64 encoded data and writes the plain text content to files named after the secret keys. So the file /etc/secret-volume/password contains the plain text 'mypassword'.

❓ Configuration

intermediate

Correct secret volume mount configuration

Which of the following YAML snippets correctly mounts a secret named db-secret as a volume at /etc/db inside a pod?

A

volumes:
  - name: db-volume
    secret:
      secretName: db-secret
containers:
  - name: app
    volumeMounts:
      - name: db-volume
        path: /etc/db

B

volumes:
  - name: db-volume
    secret:
      secretName: db-secret
containers:
  - name: app
    volumeMounts:
      - name: db-volume
        mountPath: /etc/db

C

bd/cte/ :htaPtnuom        
emulov-bd :eman -      
:stnuoMemulov    
ppa :eman -  
:sreniatnoc
terces-bd :emaNterces      
:terces    
emulov-bd :eman -  
:semulov

D

volumes:
  - name: db-volume
    configMap:
      name: db-secret
containers:
  - name: app
    volumeMounts:
      - name: db-volume
        mountPath: /etc/db

💡 Hint

The secret volume must specify 'secretName' and volumeMount must use 'mountPath'.

Option B correctly uses 'secretName' under 'secret' and 'mountPath' under 'volumeMounts'. Option B uses configMap instead of secret. Option B uses 'secretName' correctly (fixed from 'name'). Option B uses 'path' instead of 'mountPath'.

❓ Troubleshoot

advanced

Reason for secret volume files missing in pod

You mounted a secret as a volume in your pod, but when you exec into the pod, the secret files are missing from the mount path. What is the most likely cause?

A The secret does not exist or has a different name than specified in the volume.

B The pod does not have permission to read the secret because of RBAC rules.

C The secret was mounted as environment variables, not as a volume.

D The pod's container image does not support volumes.

💡 Hint

Check if the secret name in the volume matches an existing secret.

If the secret name in the volume does not match any existing secret, Kubernetes cannot mount it, so the files will be missing. RBAC does not restrict secret volume mounts. Environment variables are different from volume mounts. Container images do not affect volume mounting.

🔀 Workflow

advanced

Steps to update a secret mounted as volume in a running pod

You updated a Kubernetes secret that is mounted as a volume in a running pod. What is the correct way to see the updated secret files inside the pod?

A Update the secret and wait 24 hours for automatic refresh inside the pod.

B Run 'kubectl exec' and the secret files update automatically without pod restart.

C Restart the container inside the pod using 'kubectl rollout restart'.

D Delete and recreate the pod to reload the secret volume with updated data.

💡 Hint

Secret volumes are mounted at pod start and do not update automatically.

Kubernetes mounts secret volumes at pod start. Updating the secret does not update the files inside running pods. You must delete and recreate the pod to see changes. Option D is incorrect because files do not update automatically. Option D is invalid because 'kubectl rollout restart' applies to deployments, not containers. Option D is false; no automatic refresh occurs.

✅ Best Practice

expert

Best practice for restricting secret volume file permissions

You want to mount a secret as a volume but restrict the file permissions so only the owner can read the secret files inside the pod. Which volume configuration option achieves this?

A Set 'fsGroup' to 0 in the pod security context.

B Set 'readOnly: true' under the volumeMount in the container spec.

C Set 'defaultMode: 0400' under the secret volume in the pod spec.

D Set 'defaultMode: 0777' under the secret volume in the pod spec.

💡 Hint

File permission modes control access rights; 0400 means read by owner only.

The 'defaultMode' field under the secret volume controls the permission bits of the mounted files. Setting it to 0400 makes files readable only by the owner. 'readOnly' only prevents writing but does not restrict read permissions. 'fsGroup' controls group ownership, not file permissions. 0777 gives full permissions to all, which is insecure.