Update localization guidelines (#10485)

* Update localization guidelines for language labels Continuing work Continuing work Continuing work More work in progress Add local OWNERS folders Add an OWNERS file to Chinese Remove shortcode for repos Add Japanese Alphabetize languages, change weights accordingly More updates Add Korean in Korean Add English to languageName Feedback from gochist Move Chinese content from cn/ to zh/ Move OWNERS from cn/ to zh/ Resolve merge conflicts by updating from master Add files back in to prep for resolution After rebase on upstream/master, remove files Review and update localization guidelines Feedback from gochist, tnir, cstoku Add a trailing newline to content/ja/OWNERS Add a trailing newline to content/zh/OWNERS Drop requirement for GH repo project Clarify language about forks/branches Edits and typos Remove a shortcode specific to a multi-repo language setup Update aliases and owners Add explicit OWNERS for content/en Migrate content from Chinese repo, update regex in config.toml Remove untranslated strings Add trailing newline to content/en/OWNERS Add trailing newlines to OWNERS files add Jaguar project description (#10433) * add Jaguar project description [Jaguar](https://gitlab.com/sdnlab/jaguar) is an open source solution for Kubernetes's network based on OpenDaylight. Jaguar provides overlay network using vxlan and Jaguar CNIPlugin provides one IP address per pod. * Minor newline tweak blog post for azure vmss (#10538) Add microk8s to pick-right-solution.md (#10542) * Add microk8s to pick-right-solution.md Microk8s is a single-command installation of upstream Kubernetes on any Linux and should be included in the list of local-machine solutions. * capitalized Istio Add microk8s to foundational.md (#10543) * Add microk8s to foundational.md Adding microk8s as credible and stable alternative to get started with Kubernetes on a local machine. This is especially attractive for those not wanting to incur the overhead of running a VM for a local cluster. * Update foundational.md Thank you for your suggestions! LMK if this works now? * Rewrote first paragraph And included a bullet list of features of microk8s * Copyedit fix typo (#10545) Fix the kubectl subcommands links. (#10550) Signed-off-by: William Zhang <warmchang@outlook.com> Fix command issue (#10515) Signed-off-by: mooncake <xcoder@tenxcloud.com> remove imported community files per issue 10184 (#10501) networking.md: Markdown fix (#10498) Fix front matter, federation command-line tools (#10500) Clean up glossary entry (#10399) update slack link (#10536) typo in StatefulSet docs (#10558) fix discription about horizontal pod autoscale (#10557) Remove redundant symbols (#10556) Fix issue #10520 (#10554) Signed-off-by: William Zhang <warmchang@outlook.com> Update api-concepts.md (#10534) Revert "Fix command issue (#10515)" This reverts commit c02a7fb9f9. Update memory-constraint-namespace.md (#10530) update memory request to 100MiB corresponding the yaml content Blog: Introducing Volume Snapshot Alpha for Kubernetes (#10562) * blog post for azure vmss * snapshot blog post Resolve merge conflicts in OWNERS* Minor typo fix (#10567) Not sure what's supposed to be here, proposing removing it. * Feedback from gochist Tweaks to feedback * Feedback from ClaudiaJKang
2018-10-12 14:25:01 -07:00
parent 753f57f0e6
commit abcee2dccd
316 changed files with 9227 additions and 169 deletions
@@ -0,0 +1,135 @@
+---
+title: 将 Pod 分配给节点
+content_template: templates/task
+weight: 120
+---
+<!--
+---
+title: Assign Pods to Nodes
+content_template: templates/task
+weight: 120
+---
+-->
+
+{{% capture overview %}}
+<!--
+This page shows how to assign a Kubernetes Pod to a particular node in a
+Kubernetes cluster.
+-->
+此页面显示如何将 Kubernetes Pod 分配给 Kubernetes 集群中的特定节点。
+{{% /capture %}}
+
+{{% capture prerequisites %}}
+
+{{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}
+
+{{% /capture %}}
+
+{{% capture steps %}}
+
+<!--
+## Add a label to a node
+-->
+## 给节点添加标签
+
+<!--
+1. List the nodes in your cluster:
+-->
+1. 列出集群中的节点
+
+        kubectl get nodes
+
+    <!--
+    The output is similar to this:
+    -->
+    输出类似如下：
+
+        NAME      STATUS    AGE     VERSION
+        worker0   Ready     1d      v1.6.0+fff5156
+        worker1   Ready     1d      v1.6.0+fff5156
+        worker2   Ready     1d      v1.6.0+fff5156
+
+<!--
+1. Chose one of your nodes, and add a label to it:
+-->
+1. 选择其中一个节点，为它添加标签：
+
+        kubectl label nodes <your-node-name> disktype=ssd
+
+    <!--
+    where `<your-node-name>` is the name of your chosen node.
+    -->
+    `<your-node-name>` 是你选择的节点的名称。
+
+<!--
+1. Verify that your chosen node has a `disktype=ssd` label:
+-->
+1. 验证你选择的节点是否有 `disktype=ssd` 标签：
+
+       kubectl get nodes --show-labels
+
+
+    <!--
+    The output is similar to this:
+    -->
+    输出类似如下：
+
+        NAME      STATUS    AGE     VERSION            LABELS
+        worker0   Ready     1d      v1.6.0+fff5156     ...,disktype=ssd,kubernetes.io/hostname=worker0
+        worker1   Ready     1d      v1.6.0+fff5156     ...,kubernetes.io/hostname=worker1
+        worker2   Ready     1d      v1.6.0+fff5156     ...,kubernetes.io/hostname=worker2
+
+    <!--
+    In the preceding output, you can see that the `worker0` node has a
+    `disktype=ssd` label.
+    -->
+    在前面的输出中，你可以看到 `worker0` 节点有 `disktype=ssd` 标签。
+
+<!--
+## Create a pod that gets scheduled to your chosen node
+-->
+## 创建一个调度到你选择的节点的 pod
+
+<!--
+This pod configuration file describes a pod that has a node selector,
+`disktype: ssd`. This means that the pod will get scheduled on a node that has
+a `disktype=ssd` label.
+-->
+该 pod 配置文件描述了一个拥有节点选择器 `disktype: ssd` 的 pod。这表明该 pod 将被调度到
+有 `disktype=ssd` 标签的节点。
+
+{{< codenew file="pods/pod-nginx.yaml" >}}
+
+<!--
+1. Use the configuration file to create a pod that will get scheduled on your
+   chosen node:
+-->
+1. 使用该配置文件去创建一个 pod，该 pod 将被调度到你选择的节点上：
+
+        kubectl create -f https://k8s.io/examples/pods/pod-nginx.yaml
+
+<!--
+1. Verify that the pod is running on your chosen node:
+-->
+1. 验证 pod 是不是运行在你选择的节点上：
+
+        kubectl get pods --output=wide
+
+    <!--
+    The output is similar to this:
+    -->
+    输出类似如下：
+
+        NAME     READY     STATUS    RESTARTS   AGE    IP           NODE
+        nginx    1/1       Running   0          13s    10.200.0.4   worker0
+
+{{% /capture %}}
+
+{{% capture whatsnext %}}
+<!--
+Learn more about
+[labels and selectors](/docs/concepts/overview/working-with-objects/labels/).
+-->
+了解更多关于
+[标签和选择器](/docs/concepts/overview/working-with-objects/labels/)。
+{{% /capture %}}
@@ -0,0 +1,16 @@
+apiVersion: v1
+kind: Pod
+metadata:
+  name: cpu-demo-2
+spec:
+  containers:
+  - name: cpu-demo-ctr-2
+    image: vish/stress
+    resources:
+      limits:
+        cpu: "100"
+      requests:
+        cpu: "100"
+    args:
+    - -cpus
+    - "2"
@@ -0,0 +1,16 @@
+apiVersion: v1
+kind: Pod
+metadata:
+  name: cpu-demo
+spec:
+  containers:
+  - name: cpu-demo-ctr
+    image: vish/stress
+    resources:
+      limits:
+        cpu: "1"
+      requests:
+        cpu: "0.5"
+    args:
+    - -cpus
+    - "2"
@@ -0,0 +1,26 @@
+apiVersion: v1
+kind: Pod
+
+metadata:
+  labels:
+    test: liveness
+  name: liveness-exec
+spec:
+  containers:
+
+  - name: liveness
+
+    args:
+    - /bin/sh
+    - -c
+    - touch /tmp/healthy; sleep 30; rm -rf /tmp/healthy; sleep 600
+
+    image: k8s.gcr.io/busybox
+
+    livenessProbe:
+      exec:
+        command:
+        - cat
+        - /tmp/healthy
+      initialDelaySeconds: 5
+      periodSeconds: 5
@@ -0,0 +1,21 @@
+apiVersion: v1
+kind: Pod
+metadata:
+  labels:
+    test: liveness
+  name: liveness-http
+spec:
+  containers:
+  - name: liveness
+    args:
+    - /server
+    image: k8s.gcr.io/liveness
+    livenessProbe:
+      httpGet:
+        path: /healthz
+        port: 8080
+        httpHeaders:
+        - name: X-Custom-Header
+          value: Awesome
+      initialDelaySeconds: 3
+      periodSeconds: 3
@@ -0,0 +1,30 @@
+apiVersion: v1
+kind: Pod
+metadata:
+  name: init-demo
+spec:
+  containers:
+  - name: nginx
+    image: nginx
+    ports:
+    - containerPort: 80
+    volumeMounts:
+    - name: workdir
+      mountPath: /usr/share/nginx/html
+  # These containers are run during pod initialization
+  initContainers:
+  - name: install
+    image: busybox
+    command:
+    - wget
+    - "-O"
+    - "/work-dir/index.html"
+    - http://kubernetes.io
+    volumeMounts:
+    - name: workdir
+      mountPath: "/work-dir"
+  dnsPolicy: Default
+  volumes:
+  - name: workdir
+    emptyDir: {}
+
@@ -0,0 +1,17 @@
+apiVersion: v1
+kind: Pod
+metadata:
+  name: lifecycle-demo
+spec:
+  containers:
+  - name: lifecycle-demo-container
+    image: nginx
+
+    lifecycle:
+      postStart:
+        exec:
+          command: ["/bin/sh", "-c", "echo Hello from the postStart handler > /usr/share/message"]
+      preStop:
+        exec:
+          command: ["/usr/sbin/nginx","-s","quit"]
+
@@ -0,0 +1,11 @@
+apiVersion: v1
+kind: LimitRange
+metadata:
+  name: mem-limit-range
+spec:
+  limits:
+  - default:
+      memory: 512Mi
+    defaultRequest:
+      memory: 256Mi
+    type: Container
@@ -0,0 +1,20 @@
+apiVersion: v1
+kind: Pod
+metadata:
+  name: memory-demo-2
+spec:
+  containers:
+  - name: memory-demo-2-ctr
+    image: vish/stress
+    resources:
+      requests:
+        memory: 50Mi
+      limits:
+        memory: "100Mi"
+    args:
+    - -mem-total
+    - 250Mi
+    - -mem-alloc-size
+    - 10Mi
+    - -mem-alloc-sleep
+    - 1s
@@ -0,0 +1,20 @@
+apiVersion: v1
+kind: Pod
+metadata:
+  name: memory-demo-3
+spec:
+  containers:
+  - name: memory-demo-3-ctr
+    image: vish/stress
+    resources:
+      limits:
+        memory: "1000Gi"
+      requests:
+        memory: "1000Gi"
+    args:
+    - -mem-total
+    - 150Mi
+    - -mem-alloc-size
+    - 10Mi
+    - -mem-alloc-sleep
+    - 1s
@@ -0,0 +1,20 @@
+apiVersion: v1
+kind: Pod
+metadata:
+  name: memory-demo
+spec:
+  containers:
+  - name: memory-demo-ctr
+    image: vish/stress
+    resources:
+      limits:
+        memory: "200Mi"
+      requests:
+        memory: "100Mi"
+    args:
+    - -mem-total
+    - 150Mi
+    - -mem-alloc-size
+    - 10Mi
+    - -mem-alloc-sleep
+    - 1s
@@ -0,0 +1,11 @@
+apiVersion: v1
+kind: Pod
+metadata:
+  name: oir-demo-2
+spec:
+  containers:
+  - name: oir-demo-2-ctr
+    image: nginx
+    resources:
+      requests:
+        pod.alpha.kubernetes.io/opaque-int-resource-dongle: 2
@@ -0,0 +1,11 @@
+apiVersion: v1
+kind: Pod
+metadata:
+  name: oir-demo
+spec:
+  containers:
+  - name: oir-demo-ctr
+    image: nginx
+    resources:
+      requests:
+        pod.alpha.kubernetes.io/opaque-int-resource-dongle: 3
@@ -0,0 +1,138 @@
+---
+title: 给容器分配非透明整型资源
+content_template: templates/task
+---
+
+{{% capture overview %}}
+
+本页展示了如何给容器分配非透明整型资源。
+
+{{< feature-state state="alpha" >}}
+
+{{% /capture %}}
+
+
+{{% capture prerequisites %}}
+
+{{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}
+
+在做这个练习之前，请在[给节点配置非透明整型资源](/docs/tasks/administer-cluster/opaque-integer-resource-node/)文档中进行练习，
+该文档介绍了在一个节点上配置dongle资源。
+
+{{% /capture %}}
+
+
+{{% capture steps %}}
+
+## 给Pod分配非透明整型资源
+
+为了请求一个非透明整型资源，需要在容器配置文件中包含`resources:requests`字段。
+非透明整型资源类型前缀是`pod.alpha.kubernetes.io/opaque-int-resource-`。
+
+下面是含有一个容器的Pod的配置文件:
+
+{{< code file="oir-pod.yaml" >}}
+
+在配置文件中，可以看到容器请求了3个dongles资源。
+
+创建Pod:
+
+```shell
+kubectl create -f https://k8s.io/docs/tasks/configure-pod-container/oir-pod.yaml
+```
+
+验证Pod是否正在运行:
+
+```shell
+kubectl get pod oir-demo
+```
+
+查询Pod的状态:
+
+```shell
+kubectl describe pod oir-demo
+```
+
+输出显示了dongle请求:
+
+```yaml
+Requests:
+  pod.alpha.kubernetes.io/opaque-int-resource-dongle: 3
+```
+
+## 尝试创建第二个Pod
+
+下面是含有一个容器的Pod的配置文件。该容器请求了两个dongles资源。
+
+{{< code file="oir-pod-2.yaml" >}}
+
+Kubernetes无法再满足两个dongles的请求，因为第一个Pod已经使用了四个可用dongles中的三个。
+
+尝试创建Pod:
+
+```shell
+kubectl create -f https://k8s.io/docs/tasks/configure-pod-container/oir-pod-2.yaml
+```
+
+查询Pod的状态
+
+```shell
+kubectl describe pod oir-demo-2
+```
+
+输出显示该Pod无法被调度，因为没有节点有两个可用的dongles资源:
+
+
+```
+Conditions:
+  Type    Status
+  PodScheduled  False
+...
+Events:
+  ...
+  ... Warning   FailedScheduling  pod (oir-demo-2) failed to fit in any node
+fit failure summary on nodes : Insufficient pod.alpha.kubernetes.io/opaque-int-resource-dongle (1)
+```
+
+查看Pod的状态:
+
+```shell
+kubectl get pod oir-demo-2
+```
+
+输出显示Pod已创建，但是没有被调度并运行在节点上。
+它的状态为Pending:
+
+```yaml
+NAME         READY     STATUS    RESTARTS   AGE
+oir-demo-2   0/1       Pending   0          6m
+```
+
+## 删除
+
+删除本练习中创建的Pod:
+
+```shell
+kubectl delete pod oir-demo
+```
+
+{{% /capture %}}
+
+{{% capture whatsnext %}}
+
+### 对于应用开发者
+
+* [分配内存资源](/docs/tasks/configure-pod-container/assign-memory-resource/)
+* [分配CPU资源](/docs/tasks/configure-pod-container/assign-cpu-resource/)
+
+### 对于集群管理员
+
+* [给节点配置非透明整型资源](/docs/tasks/administer-cluster/opaque-integer-resource-node/)
+
+{{% /capture %}}
+
+
+
+
+
+
@@ -0,0 +1,14 @@
+apiVersion: v1
+kind: Pod
+metadata:
+  name: redis
+spec:
+  containers:
+  - name: redis
+    image: redis
+    volumeMounts:
+    - name: redis-storage
+      mountPath: /data/redis
+  volumes:
+  - name: redis-storage
+    emptyDir: {}
@@ -0,0 +1,13 @@
+apiVersion: v1
+kind: Pod
+metadata:
+  name: nginx
+  labels:
+    env: test
+spec:
+  containers:
+  - name: nginx
+    image: nginx
+    imagePullPolicy: IfNotPresent
+  nodeSelector:
+    disktype: ssd
@@ -0,0 +1,11 @@
+apiVersion: v1
+kind: Pod
+metadata:
+  name: private-reg
+spec:
+  containers:
+  - name: private-reg-container
+    image: <your-private-image>
+  imagePullSecrets:
+  - name: regsecret
+
@@ -0,0 +1,23 @@
+apiVersion: v1
+kind: Pod
+metadata:
+  name: test-projected-volume
+spec:
+  containers:
+  - name: test-projected-volume
+    image: busybox
+    args:
+    - sleep
+    - "86400"
+    volumeMounts:
+    - name: all-in-one
+      mountPath: "/projected-volume"
+      readOnly: true
+  volumes:
+  - name: all-in-one
+    projected:
+      sources:
+      - secret:
+          name: user
+      - secret:
+          name: pass
@@ -0,0 +1,14 @@
+apiVersion: v1
+kind: Pod
+metadata:
+  name: qos-demo-2
+  namespace: qos-example
+spec:
+  containers:
+  - name: qos-demo-2-ctr
+    image: nginx
+    resources:
+      limits:
+        memory: "200Mi"
+      requests:
+        memory: "100Mi"
@@ -0,0 +1,9 @@
+apiVersion: v1
+kind: Pod
+metadata:
+  name: qos-demo-3
+  namespace: qos-example
+spec:
+  containers:
+  - name: qos-demo-3-ctr
+    image: nginx
@@ -0,0 +1,16 @@
+apiVersion: v1
+kind: Pod
+metadata:
+  name: qos-demo-4
+  namespace: qos-example
+spec:
+  containers:
+
+  - name: qos-demo-4-ctr-1
+    image: nginx
+    resources:
+      requests:
+        memory: "200Mi"
+
+  - name: qos-demo-4-ctr-2
+    image: redis
@@ -0,0 +1,16 @@
+apiVersion: v1
+kind: Pod
+metadata:
+  name: qos-demo
+  namespace: qos-example
+spec:
+  containers:
+  - name: qos-demo-ctr
+    image: nginx
+    resources:
+      limits:
+        memory: "200Mi"
+        cpu: "700m"
+      requests:
+        memory: "200Mi"
+        cpu: "700m"
@@ -0,0 +1,11 @@
+apiVersion: v1
+kind: ResourceQuota
+metadata:
+  name: compute-resources
+spec:
+  hard:
+    pods: "4"
+    requests.cpu: "1"
+    requests.memory: 1Gi 
+    limits.cpu: "2"
+    limits.memory: 2Gi
@@ -0,0 +1,12 @@
+apiVersion: v1
+kind: Pod
+metadata:
+  name: security-context-demo-2 
+spec:
+  securityContext:
+    runAsUser: 1000
+  containers:
+  - name: sec-ctx-demo-2
+    image: gcr.io/google-samples/node-hello:1.0
+    securityContext:
+      runAsUser: 2000
@@ -0,0 +1,11 @@
+apiVersion: v1
+kind: Pod
+metadata:
+  name: security-context-demo-3
+spec:
+  containers:
+  - name: sec-ctx-3
+    image: gcr.io/google-samples/node-hello:1.0
+
+
+
@@ -0,0 +1,11 @@
+apiVersion: v1
+kind: Pod
+metadata:
+  name: security-context-demo-4
+spec:
+  containers:
+  - name: sec-ctx-4
+    image: gcr.io/google-samples/node-hello:1.0
+    securityContext:
+      capabilities:
+        add: ["NET_ADMIN", "SYS_TIME"]
@@ -0,0 +1,17 @@
+apiVersion: v1
+kind: Pod
+metadata:
+  name: security-context-demo  
+spec:
+  securityContext:
+    runAsUser: 1000
+    fsGroup: 2000
+  volumes:
+  - name: sec-ctx-vol
+    emptyDir: {}
+  containers:
+  - name: sec-ctx-demo
+    image: gcr.io/google-samples/node-hello:1.0
+    volumeMounts:
+    - name: sec-ctx-vol
+      mountPath: /data/demo
@@ -0,0 +1,11 @@
+kind: PersistentVolumeClaim
+apiVersion: v1
+metadata:
+  name: task-pv-claim
+spec:
+  storageClassName: manual
+  accessModes:
+    - ReadWriteOnce
+  resources:
+    requests:
+      storage: 3Gi
@@ -0,0 +1,22 @@
+kind: Pod
+apiVersion: v1
+metadata:
+  name: task-pv-pod
+spec:
+
+  volumes:
+    - name: task-pv-storage
+      persistentVolumeClaim:
+       claimName: task-pv-claim
+
+  containers:
+    - name: task-pv-container
+      image: nginx
+      ports:
+        - containerPort: 80
+          name: "http-server"
+      volumeMounts:
+      - mountPath: "/usr/share/nginx/html"
+        name: task-pv-storage
+
+
@@ -0,0 +1,14 @@
+kind: PersistentVolume
+apiVersion: v1
+metadata:
+  name: task-pv-volume
+  labels:
+    type: local
+spec:
+  storageClassName: manual
+  capacity:
+    storage: 10Gi
+  accessModes:
+    - ReadWriteOnce
+  hostPath:
+    path: "/tmp/data"
@@ -0,0 +1,22 @@
+apiVersion: v1
+kind: Pod
+metadata:
+  name: goproxy
+  labels:
+    app: goproxy
+spec:
+  containers:
+  - name: goproxy
+    image: k8s.gcr.io/goproxy:0.1
+    ports:
+    - containerPort: 8080
+    readinessProbe:
+      tcpSocket:
+        port: 8080
+      initialDelaySeconds: 5
+      periodSeconds: 10
+    livenessProbe:
+      tcpSocket:
+        port: 8080
+      initialDelaySeconds: 15
+      periodSeconds: 20