sync en zh yaml in content/zh/example/admin direcroty (#19766)

content/zh/examples/admin/cloud/ccm-example.yaml

@@ -10,8 +10,8 @@ metadata:
   name: cloud-controller-manager
   namespace: kube-system
 ---
-kind: ClusterRoleBinding
 apiVersion: rbac.authorization.k8s.io/v1
+kind: ClusterRoleBinding
 metadata:
   name: system:cloud-controller-manager
 roleRef:
@@ -47,7 +47,7 @@ spec:
         image: k8s.gcr.io/cloud-controller-manager:v1.8.0
         command:
         - /usr/local/bin/cloud-controller-manager
-        - --cloud-provider=<YOUR_CLOUD_PROVIDER>   # Add your own cloud provider here!
+        - --cloud-provider=[YOUR_CLOUD_PROVIDER]  # Add your own cloud provider here!
         - --leader-elect=true
         - --use-service-account-credentials
         # these flags will vary for every cloud provider

content/zh/examples/admin/dns/dns-horizontal-autoscaler.yaml

@@ -8,7 +8,7 @@ metadata:
 spec:
   selector:
     matchLabels:
-       k8s-app: dns-autoscaler
+      k8s-app: dns-autoscaler
   template:
     metadata:
       labels:
@@ -16,18 +16,18 @@ spec:
     spec:
       containers:
       - name: autoscaler
-        image: k8s.gcr.io/cluster-proportional-autoscaler-amd64:1.1.1
+        image: k8s.gcr.io/cluster-proportional-autoscaler-amd64:1.6.0
         resources:
-            requests:
-                cpu: "20m"
-                memory: "10Mi"
+          requests:
+            cpu: 20m
+            memory: 10Mi
         command:
-          - /cluster-proportional-autoscaler
-          - --namespace=kube-system
-          - --configmap=dns-autoscaler
-          - --target=<SCALE_TARGET>
-          # When cluster is using large nodes(with more cores), "coresPerReplica" should dominate.
-          # If using small nodes, "nodesPerReplica" should dominate.
-          - --default-params={"linear":{"coresPerReplica":256,"nodesPerReplica":16,"min":1}}
-          - --logtostderr=true
-          - --v=2
+        - /cluster-proportional-autoscaler
+        - --namespace=kube-system
+        - --configmap=dns-autoscaler
+        - --target=<SCALE_TARGET>
+        # When cluster is using large nodes(with more cores), "coresPerReplica" should dominate.
+        # If using small nodes, "nodesPerReplica" should dominate.
+        - --default-params={"linear":{"coresPerReplica":256,"nodesPerReplica":16,"min":1}}
+        - --logtostderr=true
+        - --v=2

content/zh/examples/admin/dns/dnsutils.yaml

@@ -0,0 +1,14 @@
+apiVersion: v1
+kind: Pod
+metadata:
+  name: dnsutils
+  namespace: default
+spec:
+  containers:
+  - name: dnsutils
+    image: gcr.io/kubernetes-e2e-test-images/dnsutils:1.3
+    command:
+      - sleep
+      - "3600"
+    imagePullPolicy: IfNotPresent
+  restartPolicy: Always

content/zh/examples/admin/resource/cpu-constraints-pod-3.yaml

@@ -1,10 +1,10 @@
 apiVersion: v1
 kind: Pod
 metadata:
-  name: constraints-cpu-demo-4
+  name: constraints-cpu-demo-3
 spec:
   containers:
-  - name: constraints-cpu-demo-4-ctr
+  - name: constraints-cpu-demo-3-ctr
     image: nginx
     resources:
       limits:

content/zh/examples/admin/resource/quota-objects-pvc-2.yaml

@@ -1,5 +1,5 @@
-kind: PersistentVolumeClaim
 apiVersion: v1
+kind: PersistentVolumeClaim
 metadata:
   name: pvc-quota-demo-2
 spec:

content/zh/examples/admin/resource/quota-objects-pvc.yaml

@@ -1,5 +1,5 @@
-kind: PersistentVolumeClaim
 apiVersion: v1
+kind: PersistentVolumeClaim
 metadata:
   name: pvc-quota-demo
 spec:

content/zh/examples/admin/sched/my-scheduler.yaml

@@ -4,8 +4,8 @@ metadata:
   name: my-scheduler
   namespace: kube-system
 ---
-kind: ClusterRoleBinding
 apiVersion: rbac.authorization.k8s.io/v1
+kind: ClusterRoleBinding
 metadata:
   name: my-scheduler-as-kube-scheduler
 subjects:
@@ -14,7 +14,7 @@ subjects:
   namespace: kube-system
 roleRef:
   kind: ClusterRole
-  name: kube-scheduler
+  name: system:kube-scheduler
   apiGroup: rbac.authorization.k8s.io
 ---
 apiVersion: apps/v1