How does the Downward API expose pod metadata to containers?

• A. Through environment variables or mounted files in a downward API volume
• B. By copying to logs only
• C. Via the Kubernetes UI
• D. Through an external API call only

Answer: (A)

The Downward API exposes a pod’s own metadata inside containers by two accessible methods: environment variables and a mounted volume. You can map specific pod fields to environment variables using fieldRef, for example pulling metadata.name or metadata.namespace into a variable inside the container. You can also mount a downward API volume and project chosen pod fields into files within that volume, so the container can read values like the podName, namespace, labels, annotations, or IP from those files. This lets containers adapt based on their own pod context without making API calls. The other options don’t describe how the Downward API provides access to pod metadata.