Joel Smith
5ec5118445
Because API data volumes like downwardAPI are expected to be fully managed by Kubernetes and are now mounted read-only, this causes problems with other files in /etc like /etc/resolv.conf that Docker tries to add to the volume. Our examples should show such volumes being mounted to a dedicated subdirectory for the volume.
55 lines
1.6 KiB
YAML
55 lines
1.6 KiB
YAML
apiVersion: v1
|
|
kind: Pod
|
|
metadata:
|
|
name: kubernetes-downwardapi-volume-example-2
|
|
spec:
|
|
containers:
|
|
- name: client-container
|
|
image: k8s.gcr.io/busybox:1.24
|
|
command: ["sh", "-c"]
|
|
args:
|
|
- while true; do
|
|
echo -en '\n';
|
|
if [[ -e /etc/podinfo/cpu_limit ]]; then
|
|
echo -en '\n'; cat /etc/podinfo/cpu_limit; fi;
|
|
if [[ -e /etc/podinfo/cpu_request ]]; then
|
|
echo -en '\n'; cat /etc/podinfo/cpu_request; fi;
|
|
if [[ -e /etc/podinfo/mem_limit ]]; then
|
|
echo -en '\n'; cat /etc/podinfo/mem_limit; fi;
|
|
if [[ -e /etc/podinfo/mem_request ]]; then
|
|
echo -en '\n'; cat /etc/podinfo/mem_request; fi;
|
|
sleep 5;
|
|
done;
|
|
resources:
|
|
requests:
|
|
memory: "32Mi"
|
|
cpu: "125m"
|
|
limits:
|
|
memory: "64Mi"
|
|
cpu: "250m"
|
|
volumeMounts:
|
|
- name: podinfo
|
|
mountPath: /etc/podinfo
|
|
readOnly: false
|
|
volumes:
|
|
- name: podinfo
|
|
downwardAPI:
|
|
items:
|
|
- path: "cpu_limit"
|
|
resourceFieldRef:
|
|
containerName: client-container
|
|
resource: limits.cpu
|
|
- path: "cpu_request"
|
|
resourceFieldRef:
|
|
containerName: client-container
|
|
resource: requests.cpu
|
|
- path: "mem_limit"
|
|
resourceFieldRef:
|
|
containerName: client-container
|
|
resource: limits.memory
|
|
- path: "mem_request"
|
|
resourceFieldRef:
|
|
containerName: client-container
|
|
resource: requests.memory
|
|
|