Qiming
9bf026e951
There are many YAML manifests sneaking into the `zh/docs/` directory. These files should go to the `zh/examples` directory instead. Having these "garbage" files (not referenced anywhere) is creating confusion for the release meister when merging branches. For example, some YAML files found in the 'master' branch are no longer there in the release-1.16 branch. It is tedious, if possible at all, to solve all this kind of conflicts during a rebase. The PR cleanses the zh/docs directory for all dangling YAML files.
46 lines
1.2 KiB
YAML
46 lines
1.2 KiB
YAML
apiVersion: v1
|
|
kind: Pod
|
|
metadata:
|
|
name: dapi-envars-resourcefieldref
|
|
spec:
|
|
containers:
|
|
- name: test-container
|
|
image: k8s.gcr.io/busybox:1.24
|
|
command: [ "sh", "-c"]
|
|
args:
|
|
- while true; do
|
|
echo -en '\n';
|
|
printenv MY_CPU_REQUEST MY_CPU_LIMIT;
|
|
printenv MY_MEM_REQUEST MY_MEM_LIMIT;
|
|
sleep 10;
|
|
done;
|
|
resources:
|
|
requests:
|
|
memory: "32Mi"
|
|
cpu: "125m"
|
|
limits:
|
|
memory: "64Mi"
|
|
cpu: "250m"
|
|
env:
|
|
- name: MY_CPU_REQUEST
|
|
valueFrom:
|
|
resourceFieldRef:
|
|
containerName: test-container
|
|
resource: requests.cpu
|
|
- name: MY_CPU_LIMIT
|
|
valueFrom:
|
|
resourceFieldRef:
|
|
containerName: test-container
|
|
resource: limits.cpu
|
|
- name: MY_MEM_REQUEST
|
|
valueFrom:
|
|
resourceFieldRef:
|
|
containerName: test-container
|
|
resource: requests.memory
|
|
- name: MY_MEM_LIMIT
|
|
valueFrom:
|
|
resourceFieldRef:
|
|
containerName: test-container
|
|
resource: limits.memory
|
|
restartPolicy: Never
|