Kubernetes Downward API Concepts: Difference between revisions
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
=External= | =External= | ||
* https://kubernetes.io/docs/concepts/storage/volumes/#downwardapi | |||
* https://kubernetes.io/docs/tasks/inject-data-application/downward-api-volume-expose-pod-information/ | * https://kubernetes.io/docs/tasks/inject-data-application/downward-api-volume-expose-pod-information/ | ||
Revision as of 23:25, 18 June 2020
External
- https://kubernetes.io/docs/concepts/storage/volumes/#downwardapi
- https://kubernetes.io/docs/tasks/inject-data-application/downward-api-volume-expose-pod-information/
Internal
Overview
Kubernetes is exposing pod information to the containers running inside the pod through files, which are projected in the container by a mechanism known as the Downward API.
Example
This is how the pod name and namespace can be projected to be available to containers running inside the pod.
Declare a "downwardAPI" volume and mount it in the pod:
apiVersion: v1
kind: Pod
metadata:
name: loop
spec:
containers:
- name: loop
image: docker.io/ovidiufeodorov/loop:latest