diff --git a/_includes/v1.3/v1-definitions.html b/_includes/v1.3/v1-definitions.html
index 4cd88cc6ed..42ed010f3c 100755
--- a/_includes/v1.3/v1-definitions.html
+++ b/_includes/v1.3/v1-definitions.html
@@ -6415,7 +6415,7 @@ The resulting set of endpoints can be viewed as:
names
-
Names by which this image is known. e.g. ["gcr.io/google_containers/hyperkube:v1.0.7", "dockerhub.io/google_containers/hyperkube:v1.0.7"]
+
Names by which this image is known. e.g. ["k8s.gcr.io/hyperkube:v1.0.7", "dockerhub.io/google_containers/hyperkube:v1.0.7"]
true
string array
diff --git a/_includes/v1.4/v1-definitions.html b/_includes/v1.4/v1-definitions.html
index 254075b5cb..8e61a5b040 100755
--- a/_includes/v1.4/v1-definitions.html
+++ b/_includes/v1.4/v1-definitions.html
@@ -6671,7 +6671,7 @@ The resulting set of endpoints can be viewed as:
names
-
Names by which this image is known. e.g. ["gcr.io/google_containers/hyperkube:v1.0.7", "dockerhub.io/google_containers/hyperkube:v1.0.7"]
+
Names by which this image is known. e.g. ["k8s.gcr.io/hyperkube:v1.0.7", "dockerhub.io/google_containers/hyperkube:v1.0.7"]
true
string array
diff --git a/_includes/v1.5/v1-definitions.html b/_includes/v1.5/v1-definitions.html
index ed1b302484..5dbb6c7094 100755
--- a/_includes/v1.5/v1-definitions.html
+++ b/_includes/v1.5/v1-definitions.html
@@ -6850,7 +6850,7 @@ The resulting set of endpoints can be viewed as:
names
-
Names by which this image is known. e.g. ["gcr.io/google_containers/hyperkube:v1.0.7", "dockerhub.io/google_containers/hyperkube:v1.0.7"]
+
Names by which this image is known. e.g. ["k8s.gcr.io/hyperkube:v1.0.7", "dockerhub.io/google_containers/hyperkube:v1.0.7"]
true
string array
diff --git a/_redirects b/_redirects
index b810d18955..8d57712722 100644
--- a/_redirects
+++ b/_redirects
@@ -443,3 +443,4 @@ https://kubernetes-io-v1-7.netlify.com/* https://v1-7.docs.kubernetes.io/:spl
/docs/admin/kubefed_unjoin/ /docs/reference/generated/kubefed_unjoin/ 301
/docs/admin/kubefed_version/ /docs/reference/generated/kubefed_version/ 301
+/docs/reference/generated/kubeadm/ /docs/reference/setup-tools/kubeadm/kubeadm/ 301
diff --git a/cn/docs/admin/cluster-large.md b/cn/docs/admin/cluster-large.md
index 9f6b33c94f..5670f7e0ae 100644
--- a/cn/docs/admin/cluster-large.md
+++ b/cn/docs/admin/cluster-large.md
@@ -85,7 +85,7 @@ AWS使用的规格为：
```yaml
containers:
- name: fluentd-cloud-logging
- image: gcr.io/google_containers/fluentd-gcp:1.16
+ image: k8s.gcr.io/fluentd-gcp:1.16
resources:
limits:
cpu: 100m
diff --git a/cn/docs/admin/node-conformance.md b/cn/docs/admin/node-conformance.md
index 6be4ba50a0..91af9fde63 100644
--- a/cn/docs/admin/node-conformance.md
+++ b/cn/docs/admin/node-conformance.md
@@ -40,7 +40,7 @@ title: 节点设置校验
# $LOG_DIR 是测试结果输出的路径。
sudo docker run -it --rm --privileged --net=host \
-v /:/rootfs -v $CONFIG_DIR:$CONFIG_DIR -v $LOG_DIR:/var/result \
- gcr.io/google_containers/node-test:0.2
+ k8s.gcr.io/node-test:0.2
```
## 针对其他硬件体系结构运行节点合规性测试
@@ -61,7 +61,7 @@ Kubernetes 也为其他硬件体系结构的系统提供了节点合规性测试
sudo docker run -it --rm --privileged --net=host \
-v /:/rootfs:ro -v $CONFIG_DIR:$CONFIG_DIR -v $LOG_DIR:/var/result \
-e FOCUS=MirrorPod \ # 只运行MirrorPod测试
- gcr.io/google_containers/node-test:0.2
+ k8s.gcr.io/node-test:0.2
```
为跳过指定的测试，用正则表达式来描述将要跳过的测试，并重载 `SKIP` 环境变量。
@@ -70,7 +70,7 @@ sudo docker run -it --rm --privileged --net=host \
sudo docker run -it --rm --privileged --net=host \
-v /:/rootfs:ro -v $CONFIG_DIR:$CONFIG_DIR -v $LOG_DIR:/var/result \
-e SKIP=MirrorPod \ # 运行除MirrorPod外的所有测试
- gcr.io/google_containers/node-test:0.2
+ k8s.gcr.io/node-test:0.2
```
节点合规性测试是[节点端到端测试](https://github.com/kubernetes/community/blob/{{page.githubbranch}}/contributors/devel/e2e-node-tests.md)的一个容器化的版本。
diff --git a/cn/docs/concepts/architecture/cloud-controller.md b/cn/docs/concepts/architecture/cloud-controller.md
index 644e3e7d0a..15840fd8b5 100644
--- a/cn/docs/concepts/architecture/cloud-controller.md
+++ b/cn/docs/concepts/architecture/cloud-controller.md
@@ -172,7 +172,7 @@ v1/ServiceAccount:
针对CCM的RBAC ClusterRole如下所示：
```yaml
-apiVersion: rbac.authorization.k8s.io/v1beta1
+apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
name: cloud-controller-manager
diff --git a/cn/docs/concepts/architecture/nodes.md b/cn/docs/concepts/architecture/nodes.md
index fa9bb53098..da999dd7a6 100644
--- a/cn/docs/concepts/architecture/nodes.md
+++ b/cn/docs/concepts/architecture/nodes.md
@@ -216,7 +216,7 @@ metadata:
spec:
containers:
- name: sleep-forever
- image: gcr.io/google_containers/pause:0.8.0
+ image: k8s.gcr.io/pause:0.8.0
resources:
requests:
cpu: 100m
diff --git a/cn/docs/concepts/configuration/manage-compute-resources-container.md b/cn/docs/concepts/configuration/manage-compute-resources-container.md
index 6b06fc5064..341706ef10 100644
--- a/cn/docs/concepts/configuration/manage-compute-resources-container.md
+++ b/cn/docs/concepts/configuration/manage-compute-resources-container.md
@@ -199,7 +199,7 @@ Conditions:
Events:
FirstSeen LastSeen Count From SubobjectPath Reason Message
Tue, 07 Jul 2015 12:53:51 -0700 Tue, 07 Jul 2015 12:53:51 -0700 1 {scheduler } scheduled Successfully assigned simmemleak-hra99 to kubernetes-node-tf0f
- Tue, 07 Jul 2015 12:53:51 -0700 Tue, 07 Jul 2015 12:53:51 -0700 1 {kubelet kubernetes-node-tf0f} implicitly required container POD pulled Pod container image "gcr.io/google_containers/pause:0.8.0" already present on machine
+ Tue, 07 Jul 2015 12:53:51 -0700 Tue, 07 Jul 2015 12:53:51 -0700 1 {kubelet kubernetes-node-tf0f} implicitly required container POD pulled Pod container image "k8s.gcr.io/pause:0.8.0" already present on machine
Tue, 07 Jul 2015 12:53:51 -0700 Tue, 07 Jul 2015 12:53:51 -0700 1 {kubelet kubernetes-node-tf0f} implicitly required container POD created Created with docker id 6a41280f516d
Tue, 07 Jul 2015 12:53:51 -0700 Tue, 07 Jul 2015 12:53:51 -0700 1 {kubelet kubernetes-node-tf0f} implicitly required container POD started Started with docker id 6a41280f516d
Tue, 07 Jul 2015 12:53:51 -0700 Tue, 07 Jul 2015 12:53:51 -0700 1 {kubelet kubernetes-node-tf0f} spec.containers{simmemleak} created Created with docker id 87348f12526a
diff --git a/cn/docs/concepts/configuration/pod-with-node-affinity.yaml b/cn/docs/concepts/configuration/pod-with-node-affinity.yaml
index 7c38e19997..253d2b21ea 100644
--- a/cn/docs/concepts/configuration/pod-with-node-affinity.yaml
+++ b/cn/docs/concepts/configuration/pod-with-node-affinity.yaml
@@ -23,4 +23,4 @@ spec:
- another-node-label-value
containers:
- name: with-node-affinity
- image: gcr.io/google_containers/pause:2.0
\ No newline at end of file
+ image: k8s.gcr.io/pause:2.0
\ No newline at end of file
diff --git a/cn/docs/concepts/configuration/pod-with-pod-affinity.yaml b/cn/docs/concepts/configuration/pod-with-pod-affinity.yaml
index 3728537d5a..1897af901f 100644
--- a/cn/docs/concepts/configuration/pod-with-pod-affinity.yaml
+++ b/cn/docs/concepts/configuration/pod-with-pod-affinity.yaml
@@ -26,4 +26,4 @@ spec:
topologyKey: kubernetes.io/hostname
containers:
- name: with-pod-affinity
- image: gcr.io/google_containers/pause:2.0
+ image: k8s.gcr.io/pause:2.0
diff --git a/cn/docs/concepts/configuration/secret.md b/cn/docs/concepts/configuration/secret.md
index 9b61a725eb..c8c9319485 100644
--- a/cn/docs/concepts/configuration/secret.md
+++ b/cn/docs/concepts/configuration/secret.md
@@ -518,7 +518,7 @@ spec:
secretName: dotfile-secret
containers:
- name: dotfile-test-container
- image: gcr.io/google_containers/busybox
+ image: k8s.gcr.io/busybox
command:
- ls
- "-l"
diff --git a/cn/docs/concepts/workloads/pods/pod-lifecycle.md b/cn/docs/concepts/workloads/pods/pod-lifecycle.md
index 8420f318bc..176e57b829 100644
--- a/cn/docs/concepts/workloads/pods/pod-lifecycle.md
+++ b/cn/docs/concepts/workloads/pods/pod-lifecycle.md
@@ -108,7 +108,7 @@ spec:
containers:
- args:
- /server
- image: gcr.io/google_containers/liveness
+ image: k8s.gcr.io/liveness
livenessProbe:
httpGet:
# when "host" is not defined, "PodIP" will be used
diff --git a/cn/docs/tasks/access-application-cluster/redis-master.yaml b/cn/docs/tasks/access-application-cluster/redis-master.yaml
index 57305a7a35..589de648f5 100644
--- a/cn/docs/tasks/access-application-cluster/redis-master.yaml
+++ b/cn/docs/tasks/access-application-cluster/redis-master.yaml
@@ -9,7 +9,7 @@ metadata:
spec:
containers:
- name: master
- image: gcr.io/google_containers/redis:v1
+ image: k8s.gcr.io/redis:v1
env:
- name: MASTER
value: "true"
diff --git a/cn/docs/tasks/administer-cluster/cpu-memory-limit.md b/cn/docs/tasks/administer-cluster/cpu-memory-limit.md
index b437c8a2f0..341e3070f6 100644
--- a/cn/docs/tasks/administer-cluster/cpu-memory-limit.md
+++ b/cn/docs/tasks/administer-cluster/cpu-memory-limit.md
@@ -178,7 +178,7 @@ $ kubectl get pods valid-pod --namespace=limit-example -o yaml | grep -C 6 resou
uid: 3b1bfd7a-f53c-11e5-b066-64510658e388
spec:
containers:
- - image: gcr.io/google_containers/serve_hostname
+ - image: k8s.gcr.io/serve_hostname
imagePullPolicy: Always
name: kubernetes-serve-hostname
resources:
diff --git a/cn/docs/tasks/administer-cluster/dns-horizontal-autoscaler.yaml b/cn/docs/tasks/administer-cluster/dns-horizontal-autoscaler.yaml
index f29dd2e275..b427829b5f 100644
--- a/cn/docs/tasks/administer-cluster/dns-horizontal-autoscaler.yaml
+++ b/cn/docs/tasks/administer-cluster/dns-horizontal-autoscaler.yaml
@@ -13,7 +13,7 @@ spec:
spec:
containers:
- name: autoscaler
- image: gcr.io/google_containers/cluster-proportional-autoscaler-amd64:1.0.0
+ image: k8s.gcr.io/cluster-proportional-autoscaler-amd64:1.0.0
resources:
requests:
cpu: "20m"
diff --git a/cn/docs/tasks/administer-cluster/pod1.yaml b/cn/docs/tasks/administer-cluster/pod1.yaml
index 733aa97d99..560b6aa0fb 100644
--- a/cn/docs/tasks/administer-cluster/pod1.yaml
+++ b/cn/docs/tasks/administer-cluster/pod1.yaml
@@ -7,4 +7,4 @@ metadata:
spec:
containers:
- name: pod-with-no-annotation-container
- image: gcr.io/google_containers/pause:2.0
\ No newline at end of file
+ image: k8s.gcr.io/pause:2.0
\ No newline at end of file
diff --git a/cn/docs/tasks/administer-cluster/pod2.yaml b/cn/docs/tasks/administer-cluster/pod2.yaml
index e1e280ff09..2f065efe65 100644
--- a/cn/docs/tasks/administer-cluster/pod2.yaml
+++ b/cn/docs/tasks/administer-cluster/pod2.yaml
@@ -8,4 +8,4 @@ spec:
schedulerName: default-scheduler
containers:
- name: pod-with-default-annotation-container
- image: gcr.io/google_containers/pause:2.0
+ image: k8s.gcr.io/pause:2.0
diff --git a/cn/docs/tasks/administer-cluster/pod3.yaml b/cn/docs/tasks/administer-cluster/pod3.yaml
index 63be0e0aa3..a1b8db3200 100644
--- a/cn/docs/tasks/administer-cluster/pod3.yaml
+++ b/cn/docs/tasks/administer-cluster/pod3.yaml
@@ -8,4 +8,4 @@ spec:
schedulerName: my-scheduler
containers:
- name: pod-with-second-annotation-container
- image: gcr.io/google_containers/pause:2.0
+ image: k8s.gcr.io/pause:2.0
diff --git a/cn/docs/tasks/configure-pod-container/exec-liveness.yaml b/cn/docs/tasks/configure-pod-container/exec-liveness.yaml
index 7b04a5eb8d..1ecb6cc25f 100644
--- a/cn/docs/tasks/configure-pod-container/exec-liveness.yaml
+++ b/cn/docs/tasks/configure-pod-container/exec-liveness.yaml
@@ -15,7 +15,7 @@ spec:
- -c
- touch /tmp/healthy; sleep 30; rm -rf /tmp/healthy; sleep 600
- image: gcr.io/google_containers/busybox
+ image: k8s.gcr.io/busybox
livenessProbe:
exec:
diff --git a/cn/docs/tasks/configure-pod-container/http-liveness.yaml b/cn/docs/tasks/configure-pod-container/http-liveness.yaml
index 6381ab3d1a..9d15abcd02 100644
--- a/cn/docs/tasks/configure-pod-container/http-liveness.yaml
+++ b/cn/docs/tasks/configure-pod-container/http-liveness.yaml
@@ -9,7 +9,7 @@ spec:
- name: liveness
args:
- /server
- image: gcr.io/google_containers/liveness
+ image: k8s.gcr.io/liveness
livenessProbe:
httpGet:
path: /healthz
diff --git a/cn/docs/tasks/configure-pod-container/tcp-liveness-readiness.yaml b/cn/docs/tasks/configure-pod-container/tcp-liveness-readiness.yaml
index 08065019c5..08fb77ff0f 100644
--- a/cn/docs/tasks/configure-pod-container/tcp-liveness-readiness.yaml
+++ b/cn/docs/tasks/configure-pod-container/tcp-liveness-readiness.yaml
@@ -7,7 +7,7 @@ metadata:
spec:
containers:
- name: goproxy
- image: gcr.io/google_containers/goproxy:0.1
+ image: k8s.gcr.io/goproxy:0.1
ports:
- containerPort: 8080
readinessProbe:
diff --git a/cn/docs/tasks/inject-data-application/dapi-envars-container.yaml b/cn/docs/tasks/inject-data-application/dapi-envars-container.yaml
index 8b3b3a39d3..55bd4dd263 100644
--- a/cn/docs/tasks/inject-data-application/dapi-envars-container.yaml
+++ b/cn/docs/tasks/inject-data-application/dapi-envars-container.yaml
@@ -5,7 +5,7 @@ metadata:
spec:
containers:
- name: test-container
- image: gcr.io/google_containers/busybox:1.24
+ image: k8s.gcr.io/busybox:1.24
command: [ "sh", "-c"]
args:
- while true; do
diff --git a/cn/docs/tasks/inject-data-application/dapi-envars-pod.yaml b/cn/docs/tasks/inject-data-application/dapi-envars-pod.yaml
index 00762373b3..071fa82bb3 100644
--- a/cn/docs/tasks/inject-data-application/dapi-envars-pod.yaml
+++ b/cn/docs/tasks/inject-data-application/dapi-envars-pod.yaml
@@ -5,7 +5,7 @@ metadata:
spec:
containers:
- name: test-container
- image: gcr.io/google_containers/busybox
+ image: k8s.gcr.io/busybox
command: [ "sh", "-c"]
args:
- while true; do
diff --git a/cn/docs/tasks/inject-data-application/dapi-volume-resources.yaml b/cn/docs/tasks/inject-data-application/dapi-volume-resources.yaml
index 65770f283f..55af44ac1b 100644
--- a/cn/docs/tasks/inject-data-application/dapi-volume-resources.yaml
+++ b/cn/docs/tasks/inject-data-application/dapi-volume-resources.yaml
@@ -5,7 +5,7 @@ metadata:
spec:
containers:
- name: client-container
- image: gcr.io/google_containers/busybox:1.24
+ image: k8s.gcr.io/busybox:1.24
command: ["sh", "-c"]
args:
- while true; do
diff --git a/cn/docs/tasks/inject-data-application/dapi-volume.yaml b/cn/docs/tasks/inject-data-application/dapi-volume.yaml
index 7126cefae5..864c99d11e 100644
--- a/cn/docs/tasks/inject-data-application/dapi-volume.yaml
+++ b/cn/docs/tasks/inject-data-application/dapi-volume.yaml
@@ -12,7 +12,7 @@ metadata:
spec:
containers:
- name: client-container
- image: gcr.io/google_containers/busybox
+ image: k8s.gcr.io/busybox
command: ["sh", "-c"]
args:
- while true; do
diff --git a/cn/docs/tasks/manage-gpus/scheduling-gpus.md b/cn/docs/tasks/manage-gpus/scheduling-gpus.md
index 208d01caf1..6aded77023 100644
--- a/cn/docs/tasks/manage-gpus/scheduling-gpus.md
+++ b/cn/docs/tasks/manage-gpus/scheduling-gpus.md
@@ -41,13 +41,13 @@ spec:
containers:
-
name: gpu-container-1
- image: gcr.io/google_containers/pause:2.0
+ image: k8s.gcr.io/pause:2.0
resources:
limits:
alpha.kubernetes.io/nvidia-gpu: 2 # requesting 2 GPUs
-
name: gpu-container-2
- image: gcr.io/google_containers/pause:2.0
+ image: k8s.gcr.io/pause:2.0
resources:
limits:
alpha.kubernetes.io/nvidia-gpu: 3 # requesting 3 GPUs
@@ -141,7 +141,7 @@ metadata:
spec:
containers:
- name: gpu-container-1
- image: gcr.io/google_containers/pause:2.0
+ image: k8s.gcr.io/pause:2.0
resources:
limits:
alpha.kubernetes.io/nvidia-gpu: 1
diff --git a/cn/docs/tutorials/services/source-ip.md b/cn/docs/tutorials/services/source-ip.md
index 18d0c4f902..92191c5cc4 100644
--- a/cn/docs/tutorials/services/source-ip.md
+++ b/cn/docs/tutorials/services/source-ip.md
@@ -33,7 +33,7 @@ Kubernetes 集群中运行的应用通过抽象的 Service 查找彼此，相互
你必须拥有一个正常工作的 Kubernetes 1.5 集群，用来运行本文中的示例。该示例使用一个简单的 nginx webserver 回送它接收到的请求的 HTTP 头中的源 IP 地址。你可以像下面这样创建它：
```console
-$ kubectl run source-ip-app --image=gcr.io/google_containers/echoserver:1.4
+$ kubectl run source-ip-app --image=k8s.gcr.io/echoserver:1.4
deployment "source-ip-app" created
```
diff --git a/cn/docs/tutorials/stateful-application/basic-stateful-set.md b/cn/docs/tutorials/stateful-application/basic-stateful-set.md
index 049c86de11..5f2b5f9edf 100644
--- a/cn/docs/tutorials/stateful-application/basic-stateful-set.md
+++ b/cn/docs/tutorials/stateful-application/basic-stateful-set.md
@@ -434,7 +434,7 @@ Kubernetes 1.7 版本的 StatefulSet 控制器支持自动更新。更新策略
Patch `web` StatefulSet 的容器镜像。
```shell
-kubectl patch statefulset web --type='json' -p='[{"op": "replace", "path": "/spec/template/spec/containers/0/image", "value":"gcr.io/google_containers/nginx-slim:0.7"}]'
+kubectl patch statefulset web --type='json' -p='[{"op": "replace", "path": "/spec/template/spec/containers/0/image", "value":"k8s.gcr.io/nginx-slim:0.7"}]'
"web" patched
```
@@ -470,9 +470,9 @@ web-0 1/1 Running 0 3s
```shell{% raw %}
kubectl get pod -l app=nginx -o jsonpath='{range .items[*]}{.metadata.name}{"\t"}{.spec.containers[0].image}{"\n"}{end}'
-web-0 gcr.io/google_containers/nginx-slim:0.7
-web-1 gcr.io/google_containers/nginx-slim:0.8
-web-2 gcr.io/google_containers/nginx-slim:0.8
+web-0 k8s.gcr.io/nginx-slim:0.7
+web-1 k8s.gcr.io/nginx-slim:0.8
+web-2 k8s.gcr.io/nginx-slim:0.8
{% endraw %}```
`web-0` has had its image updated, but `web-0` and `web-1` still have the original
@@ -513,9 +513,9 @@ web-2 1/1 Running 0 36s
```shell{% raw %}
kubectl get pod -l app=nginx -o jsonpath='{range .items[*]}{.metadata.name}{"\t"}{.spec.containers[0].image}{"\n"}{end}'
-web-0 gcr.io/google_containers/nginx-slim:0.7
-web-1 gcr.io/google_containers/nginx-slim:0.7
-web-2 gcr.io/google_containers/nginx-slim:0.7
+web-0 k8s.gcr.io/nginx-slim:0.7
+web-1 k8s.gcr.io/nginx-slim:0.7
+web-2 k8s.gcr.io/nginx-slim:0.7
{% endraw %}
```
@@ -539,7 +539,7 @@ statefulset "web" patched
在一个终端窗口中 patch `web` StatefulSet 来再次的改变容器镜像。
```shell
-kubectl patch statefulset web --type='json' -p='[{"op": "replace", "path": "/spec/template/spec/containers/0/image", "value":"gcr.io/google_containers/nginx-slim:0.8"}]'
+kubectl patch statefulset web --type='json' -p='[{"op": "replace", "path": "/spec/template/spec/containers/0/image", "value":"k8s.gcr.io/nginx-slim:0.8"}]'
statefulset "web" patched
```
@@ -589,9 +589,9 @@ StatefulSet 里的 Pod 采用和序号相反的顺序更新。在更新下一个
```shell{% raw %}
for p in 0 1 2; do kubectl get po web-$p --template '{{range $i, $c := .spec.containers}}{{$c.image}}{{end}}'; echo; done
-gcr.io/google_containers/nginx-slim:0.8
-gcr.io/google_containers/nginx-slim:0.8
-gcr.io/google_containers/nginx-slim:0.8
+k8s.gcr.io/nginx-slim:0.8
+k8s.gcr.io/nginx-slim:0.8
+k8s.gcr.io/nginx-slim:0.8
{% endraw %}
```
@@ -617,7 +617,7 @@ statefulset "web" patched
再次 Patch StatefulSet 来改变容器镜像。
```shell
-kubectl patch statefulset web --type='json' -p='[{"op": "replace", "path": "/spec/template/spec/containers/0/image", "value":"gcr.io/google_containers/nginx-slim:0.7"}]'
+kubectl patch statefulset web --type='json' -p='[{"op": "replace", "path": "/spec/template/spec/containers/0/image", "value":"k8s.gcr.io/nginx-slim:0.7"}]'
statefulset "web" patched
```
@@ -646,7 +646,7 @@ web-2 1/1 Running 0 18s
```shell{% raw %}
get po web-2 --template '{{range $i, $c := .spec.containers}}{{$c.image}}{{end}}'
-gcr.io/google_containers/nginx-slim:0.8
+k8s.gcr.io/nginx-slim:0.8
{% endraw %}
```
@@ -683,7 +683,7 @@ web-2 1/1 Running 0 18s
```shell{% raw %}
kubectl get po web-2 --template '{{range $i, $c := .spec.containers}}{{$c.image}}{{end}}'
-gcr.io/google_containers/nginx-slim:0.7
+k8s.gcr.io/nginx-slim:0.7
{% endraw %}
```
@@ -721,7 +721,7 @@ web-1 1/1 Running 0 18s
```shell{% raw %}
get po web-1 --template '{{range $i, $c := .spec.containers}}{{$c.image}}{{end}}'
-gcr.io/google_containers/nginx-slim:0.8
+k8s.gcr.io/nginx-slim:0.8
{% endraw %}
```
@@ -767,9 +767,9 @@ web-0 1/1 Running 0 3s
```shell{% raw %}
for p in 0 1 2; do kubectl get po web-$p --template '{{range $i, $c := .spec.containers}}{{$c.image}}{{end}}'; echo; done
-gcr.io/google_containers/nginx-slim:0.7
-gcr.io/google_containers/nginx-slim:0.7
-gcr.io/google_containers/nginx-slim:0.7
+k8s.gcr.io/nginx-slim:0.7
+k8s.gcr.io/nginx-slim:0.7
+k8s.gcr.io/nginx-slim:0.7
{% endraw %}
```
diff --git a/cn/docs/tutorials/stateful-application/web.yaml b/cn/docs/tutorials/stateful-application/web.yaml
index 6c2770082b..e56d43b76b 100644
--- a/cn/docs/tutorials/stateful-application/web.yaml
+++ b/cn/docs/tutorials/stateful-application/web.yaml
@@ -26,7 +26,7 @@ spec:
spec:
containers:
- name: nginx
- image: gcr.io/google_containers/nginx-slim:0.8
+ image: k8s.gcr.io/nginx-slim:0.8
ports:
- containerPort: 80
name: web
diff --git a/cn/docs/tutorials/stateful-application/webp.yaml b/cn/docs/tutorials/stateful-application/webp.yaml
index 74a71c90ac..948a1c01d9 100644
--- a/cn/docs/tutorials/stateful-application/webp.yaml
+++ b/cn/docs/tutorials/stateful-application/webp.yaml
@@ -27,7 +27,7 @@ spec:
spec:
containers:
- name: nginx
- image: gcr.io/google_containers/nginx-slim:0.8
+ image: k8s.gcr.io/nginx-slim:0.8
ports:
- containerPort: 80
name: web
diff --git a/code-of-conduct.md b/code-of-conduct.md
new file mode 100644
index 0000000000..0d15c00cf3
--- /dev/null
+++ b/code-of-conduct.md
@@ -0,0 +1,3 @@
+# Kubernetes Community Code of Conduct
+
+Please refer to our [Kubernetes Community Code of Conduct](https://git.k8s.io/community/code-of-conduct.md)
diff --git a/docs/admin/authentication.md b/docs/admin/authentication.md
index 2dc4e9fd58..8d3bd1885f 100644
--- a/docs/admin/authentication.md
+++ b/docs/admin/authentication.md
@@ -196,10 +196,10 @@ spec:
metadata:
# ...
spec:
+ serviceAccountName: bob-the-bot
containers:
- name: nginx
image: nginx:1.7.9
- serviceAccountName: bob-the-bot
```
Service account bearer tokens are perfectly valid to use outside the cluster and
diff --git a/docs/admin/bootstrap-tokens.md b/docs/admin/bootstrap-tokens.md
index 552f056337..e84fd2cd6e 100644
--- a/docs/admin/bootstrap-tokens.md
+++ b/docs/admin/bootstrap-tokens.md
@@ -36,74 +36,86 @@ information. It is used when referring to a token without leaking the secret
part used for authentication. The second part is the "Token Secret" and should
only be shared with trusted parties.
-## Enabling Bootstrap Tokens
+## Enabling Bootstrap Token Authentication
-All features for Bootstrap Tokens are disabled by default in Kubernetes v1.8.
+The Bootstrap Token authenticator can be enabled using the following flag on the
+API server:
-You can enable the Bootstrap Token authenticator with the
-`--enable-bootstrap-token-auth` flag on the API server. You can enable
-the Bootstrap controllers by specifying them with the `--controllers` flag on the
-controller manager with something like
-`--controllers=*,tokencleaner,bootstrapsigner`. This is done automatically when
-using `kubeadm`.
+```
+--enable-bootstrap-token-auth
+```
-Tokens are used in an HTTPS call as follows:
+When enabled, bootstrapping tokens can be used as bearer token credentials to
+authenticate requests against the API server.
```http
Authorization: Bearer 07401b.f395accd246ae52d
```
+Tokens authenticate as the username `system:bootstrap:` and are members
+of the group `system:bootstrappers`. Additional groups may be specified in the
+token's Secret.
+
+Expired tokens can be deleted automatically by enabling the `tokencleaner`
+controller on the controller manager.
+
+```
+--controllers=*,tokencleaner
+```
+
## Bootstrap Token Secret Format
Each valid token is backed by a secret in the `kube-system` namespace. You can
find the full design doc
[here](https://github.com/kubernetes/community/blob/{{page.githubbranch}}/contributors/design-proposals/cluster-lifecycle/bootstrap-discovery.md).
-Here is what the secret looks like. Note that `base64(string)` indicates the
-value should be base64 encoded. The undecoded version is provided here for
-readability.
+Here is what the secret looks like.
```yaml
apiVersion: v1
kind: Secret
metadata:
+ # Name MUST be of form "bootstrap-token-"
name: bootstrap-token-07401b
namespace: kube-system
+
+# Type MUST be 'bootstrap.kubernetes.io/token'
type: bootstrap.kubernetes.io/token
-data:
- description: base64(The default bootstrap token generated by 'kubeadm init'.)
- token-id: base64(07401b)
- token-secret: base64(f395accd246ae52d)
- expiration: base64(2017-03-10T03:22:11Z)
- usage-bootstrap-authentication: base64(true)
- usage-bootstrap-signing: base64(true)
- auth-extra-groups: base64(system:bootstrappers:group1,system:bootstrappers:group2)
+stringData:
+ # Human readable description. Optional.
+ description: "The default bootstrap token generated by 'kubeadm init'."
+
+ # Token ID and secret. Required.
+ token-id: 07401b
+ token-secret: f395accd246ae52d
+
+ # Expiration. Optional.
+ expiration: 2017-03-10T03:22:11Z
+
+ # Allowed usages.
+ usage-bootstrap-authentication: true
+ usage-bootstrap-signing: true
+
+ # Extra groups to authenticate the token as. Must start with "system:bootstrappers:"
+ auth-extra-groups: system:bootstrappers:worker,system:bootstrappers:ingress
```
The type of the secret must be `bootstrap.kubernetes.io/token` and the name must
be `bootstrap-token-`. It must also exist in the `kube-system`
-namespace. `description` is a human readable description that should not be
-used for machine readable information. The Token ID and Secret are included in
-the data dictionary.
+namespace.
The `usage-bootstrap-*` members indicate what this secret is intended to be used
for. A value must be set to `true` to be enabled.
-`usage-bootstrap-authentication` indicates that the token can be used to
-authenticate to the API server. The authenticator authenticates as
-`system:bootstrap:`. It is included in the `system:bootstrappers`
-group. `auth-extra-groups` indicates that it will also be included in the
-`system:bootstrappers:group1`, and `system:bootstrappers:group2` groups. The
-naming and groups are intentionally limited to discourage users from using these
-tokens past bootstrapping. Extra bootstrap token groups must start with
-`system:bootstrappers:`.
-
-`usage-bootstrap-signing` indicates that the token should be used to sign the
+* `usage-bootstrap-authentication` indicates that the token can be used to
+authenticate to the API server as a bearer token.
+* `usage-bootstrap-signing` indicates that the token may be used to sign the
`cluster-info` ConfigMap as described below.
-The `expiration` data member lists a time after which the token is no longer
-valid. This is encoded as an absolute UTC time using RFC3339. The TokenCleaner
-controller will delete expired tokens.
+The `expiration` field controls the expiry of the token. Expired tokens are
+rejected when used for authentication and ignored during ConfigMap signing.
+The expiry value is encoded as an absolute UTC time using RFC3339. Enable the
+`tokencleaner` controller to automatically delete expired tokens.
## Token Management with `kubeadm`
@@ -116,6 +128,13 @@ In addition to authentication, the tokens can be used to sign a ConfigMap. This
is used early in a cluster bootstrap process before the client trusts the API
server. The signed ConfigMap can be authenticated by the shared token.
+Enable ConfigMap signing by enabling the `bootstrapsigner` controller on the
+Controller Manager.
+
+```
+--controllers=*,bootstrapsigner
+```
+
The ConfigMap that is signed is `cluster-info` in the `kube-public` namespace.
The typical flow is that a client reads this ConfigMap while unauthenticated and
ignoring TLS errors. It then validates the payload of the ConfigMap by looking
@@ -156,3 +175,11 @@ is then used to form a whole JWS by inserting it between the 2 dots. You can
verify the JWS using the `HS256` scheme (HMAC-SHA256) with the full token (e.g.
`07401b.f395accd246ae52d`) as the shared secret. Users _must_ verify that HS256
is used.
+
+WARNING: Any party with a bootstrapping token can create a valid signature for that
+token. When using ConfigMap signing it's discouraged to share the same token with
+many clients, since a compromised client can potentially man-in-the middle another
+client relying on the signature to bootstrap TLS trust.
+
+Consult the [kubeadm security model](/docs/reference/generated/kubeadm/#security-model)
+section for more information.
diff --git a/docs/admin/cluster-large.md b/docs/admin/cluster-large.md
index b443d42132..21c50531aa 100644
--- a/docs/admin/cluster-large.md
+++ b/docs/admin/cluster-large.md
@@ -86,7 +86,7 @@ For example:
```yaml
containers:
- name: fluentd-cloud-logging
- image: gcr.io/google_containers/fluentd-gcp:1.16
+ image: k8s.gcr.io/fluentd-gcp:1.16
resources:
limits:
cpu: 100m
diff --git a/docs/admin/federation/index.md b/docs/admin/federation/index.md
index 9127a1aa36..6936a43b20 100644
--- a/docs/admin/federation/index.md
+++ b/docs/admin/federation/index.md
@@ -87,9 +87,9 @@ images or you can build them yourself from HEAD.
### Using official release images
As part of every Kubernetes release, official release images are pushed to
-`gcr.io/google_containers`. To use the images in this repository, you can
+`k8s.gcr.io`. To use the images in this repository, you can
set the container image fields in the following configs to point to the
-images in this repository. `gcr.io/google_containers/hyperkube` image
+images in this repository. `k8s.gcr.io/hyperkube` image
includes the federation-apiserver and federation-controller-manager
binaries, so you can point the corresponding configs for those components
to the hyperkube image.
@@ -315,8 +315,8 @@ official release images or you can build from HEAD.
#### Using official release images
-As part of every release, images are pushed to `gcr.io/google_containers`. To use
-these images, set env var `FEDERATION_PUSH_REPO_BASE=gcr.io/google_containers`
+As part of every release, images are pushed to `k8s.gcr.io`. To use
+these images, set env var `FEDERATION_PUSH_REPO_BASE=k8s.gcr.io`
This will always use the latest image.
To use the hyperkube image which includes federation-apiserver and
federation-controller-manager from a specific release, set the
@@ -345,7 +345,7 @@ Once you have the images, you can run these as pods on your existing kubernetes
The command to run these pods on an existing GCE cluster will look like:
```shell
-$ KUBERNETES_PROVIDER=gce FEDERATION_DNS_PROVIDER=google-clouddns FEDERATION_NAME=myfederation DNS_ZONE_NAME=myfederation.example FEDERATION_PUSH_REPO_BASE=gcr.io/google_containers ./federation/cluster/federation-up.sh
+$ KUBERNETES_PROVIDER=gce FEDERATION_DNS_PROVIDER=google-clouddns FEDERATION_NAME=myfederation DNS_ZONE_NAME=myfederation.example FEDERATION_PUSH_REPO_BASE=k8s.gcr.io ./federation/cluster/federation-up.sh
```
`KUBERNETES_PROVIDER` is the cloud provider.
diff --git a/docs/admin/high-availability/etcd.yaml b/docs/admin/high-availability/etcd.yaml
index 8bcf52b159..364791da6f 100644
--- a/docs/admin/high-availability/etcd.yaml
+++ b/docs/admin/high-availability/etcd.yaml
@@ -5,7 +5,7 @@ metadata:
spec:
hostNetwork: true
containers:
- - image: gcr.io/google_containers/etcd:3.0.17
+ - image: k8s.gcr.io/etcd:3.0.17
name: etcd-container
command:
- /usr/local/bin/etcd
diff --git a/docs/admin/high-availability/kube-apiserver.yaml b/docs/admin/high-availability/kube-apiserver.yaml
index 33d5cff5cd..057764fc52 100644
--- a/docs/admin/high-availability/kube-apiserver.yaml
+++ b/docs/admin/high-availability/kube-apiserver.yaml
@@ -6,7 +6,7 @@ spec:
hostNetwork: true
containers:
- name: kube-apiserver
- image: gcr.io/google_containers/kube-apiserver:9680e782e08a1a1c94c656190011bd02
+ image: k8s.gcr.io/kube-apiserver:9680e782e08a1a1c94c656190011bd02
command:
- /bin/sh
- -c
diff --git a/docs/admin/high-availability/kube-controller-manager.yaml b/docs/admin/high-availability/kube-controller-manager.yaml
index 0ecbebb276..ba481fbfc3 100644
--- a/docs/admin/high-availability/kube-controller-manager.yaml
+++ b/docs/admin/high-availability/kube-controller-manager.yaml
@@ -10,7 +10,7 @@ spec:
- /usr/local/bin/kube-controller-manager --master=127.0.0.1:8080 --cluster-name=e2e-test-bburns
--cluster-cidr=10.245.0.0/16 --allocate-node-cidrs=true --cloud-provider=gce --service-account-private-key-file=/srv/kubernetes/server.key
--v=2 --leader-elect=true 1>>/var/log/kube-controller-manager.log 2>&1
- image: gcr.io/google_containers/kube-controller-manager:fda24638d51a48baa13c35337fcd4793
+ image: k8s.gcr.io/kube-controller-manager:fda24638d51a48baa13c35337fcd4793
livenessProbe:
httpGet:
path: /healthz
diff --git a/docs/admin/high-availability/kube-scheduler.yaml b/docs/admin/high-availability/kube-scheduler.yaml
index 40c863da48..b4ef0e466e 100644
--- a/docs/admin/high-availability/kube-scheduler.yaml
+++ b/docs/admin/high-availability/kube-scheduler.yaml
@@ -6,7 +6,7 @@ spec:
hostNetwork: true
containers:
- name: kube-scheduler
- image: gcr.io/google_containers/kube-scheduler:34d0b8f8b31e27937327961528739bc9
+ image: k8s.gcr.io/kube-scheduler:34d0b8f8b31e27937327961528739bc9
command:
- /bin/sh
- -c
diff --git a/docs/admin/high-availability/podmaster.yaml b/docs/admin/high-availability/podmaster.yaml
index d634225b93..cd20e15b38 100644
--- a/docs/admin/high-availability/podmaster.yaml
+++ b/docs/admin/high-availability/podmaster.yaml
@@ -6,7 +6,7 @@ spec:
hostNetwork: true
containers:
- name: scheduler-elector
- image: gcr.io/google_containers/podmaster:1.1
+ image: k8s.gcr.io/podmaster:1.1
command:
- /podmaster
- --etcd-servers=http://127.0.0.1:4001
@@ -20,7 +20,7 @@ spec:
- mountPath: /manifests
name: manifests
- name: controller-manager-elector
- image: gcr.io/google_containers/podmaster:1.1
+ image: k8s.gcr.io/podmaster:1.1
command:
- /podmaster
- --etcd-servers=http://127.0.0.1:4001
diff --git a/docs/admin/limitrange/invalid-pod.yaml b/docs/admin/limitrange/invalid-pod.yaml
index b63f25deba..ecb45dd95f 100644
--- a/docs/admin/limitrange/invalid-pod.yaml
+++ b/docs/admin/limitrange/invalid-pod.yaml
@@ -5,7 +5,7 @@ metadata:
spec:
containers:
- name: kubernetes-serve-hostname
- image: gcr.io/google_containers/serve_hostname
+ image: k8s.gcr.io/serve_hostname
resources:
limits:
cpu: "3"
diff --git a/docs/admin/limitrange/valid-pod.yaml b/docs/admin/limitrange/valid-pod.yaml
index c1ec54183b..d83e91267a 100644
--- a/docs/admin/limitrange/valid-pod.yaml
+++ b/docs/admin/limitrange/valid-pod.yaml
@@ -7,7 +7,7 @@ metadata:
spec:
containers:
- name: kubernetes-serve-hostname
- image: gcr.io/google_containers/serve_hostname
+ image: k8s.gcr.io/serve_hostname
resources:
limits:
cpu: "1"
diff --git a/docs/admin/multiple-schedulers/pod1.yaml b/docs/admin/multiple-schedulers/pod1.yaml
index 6cf8fec25a..60cdab226d 100644
--- a/docs/admin/multiple-schedulers/pod1.yaml
+++ b/docs/admin/multiple-schedulers/pod1.yaml
@@ -7,4 +7,4 @@ metadata:
spec:
containers:
- name: pod-with-no-annotation-container
- image: gcr.io/google_containers/pause:2.0
+ image: k8s.gcr.io/pause:2.0
diff --git a/docs/admin/multiple-schedulers/pod2.yaml b/docs/admin/multiple-schedulers/pod2.yaml
index e1e280ff09..2f065efe65 100644
--- a/docs/admin/multiple-schedulers/pod2.yaml
+++ b/docs/admin/multiple-schedulers/pod2.yaml
@@ -8,4 +8,4 @@ spec:
schedulerName: default-scheduler
containers:
- name: pod-with-default-annotation-container
- image: gcr.io/google_containers/pause:2.0
+ image: k8s.gcr.io/pause:2.0
diff --git a/docs/admin/multiple-schedulers/pod3.yaml b/docs/admin/multiple-schedulers/pod3.yaml
index 63be0e0aa3..a1b8db3200 100644
--- a/docs/admin/multiple-schedulers/pod3.yaml
+++ b/docs/admin/multiple-schedulers/pod3.yaml
@@ -8,4 +8,4 @@ spec:
schedulerName: my-scheduler
containers:
- name: pod-with-second-annotation-container
- image: gcr.io/google_containers/pause:2.0
+ image: k8s.gcr.io/pause:2.0
diff --git a/docs/admin/multiple-zones.md b/docs/admin/multiple-zones.md
index 3f590016c0..1900e7e1a4 100644
--- a/docs/admin/multiple-zones.md
+++ b/docs/admin/multiple-zones.md
@@ -43,7 +43,7 @@ placement, and so if the zones in your cluster are heterogeneous
(e.g. different numbers of nodes, different types of nodes, or
different pod resource requirements), this might prevent perfectly
even spreading of your pods across zones. If desired, you can use
-homogenous zones (same number and types of nodes) to reduce the
+homogeneous zones (same number and types of nodes) to reduce the
probability of unequal spreading.
When persistent volumes are created, the `PersistentVolumeLabel`
diff --git a/docs/admin/namespaces/OWNERS b/docs/admin/namespaces/OWNERS
deleted file mode 100644
index cca389a741..0000000000
--- a/docs/admin/namespaces/OWNERS
+++ /dev/null
@@ -1,4 +0,0 @@
-approvers:
-- derekwaynecarr
-- janetkuo
-
diff --git a/docs/admin/namespaces/namespace-dev.json b/docs/admin/namespaces/namespace-dev.json
deleted file mode 100644
index b2b43b0b73..0000000000
--- a/docs/admin/namespaces/namespace-dev.json
+++ /dev/null
@@ -1,10 +0,0 @@
-{
- "kind": "Namespace",
- "apiVersion": "v1",
- "metadata": {
- "name": "development",
- "labels": {
- "name": "development"
- }
- }
-}
diff --git a/docs/admin/node-conformance.md b/docs/admin/node-conformance.md
index 5c3997fe53..5b6a1297fa 100644
--- a/docs/admin/node-conformance.md
+++ b/docs/admin/node-conformance.md
@@ -48,7 +48,7 @@ other Kubelet flags you may care:
# $LOG_DIR is the test output path.
sudo docker run -it --rm --privileged --net=host \
-v /:/rootfs -v $CONFIG_DIR:$CONFIG_DIR -v $LOG_DIR:/var/result \
- gcr.io/google_containers/node-test:0.2
+ k8s.gcr.io/node-test:0.2
```
## Running Node Conformance Test for Other Architectures
@@ -71,7 +71,7 @@ regular expression of tests you want to run.
sudo docker run -it --rm --privileged --net=host \
-v /:/rootfs:ro -v $CONFIG_DIR:$CONFIG_DIR -v $LOG_DIR:/var/result \
-e FOCUS=MirrorPod \ # Only run MirrorPod test
- gcr.io/google_containers/node-test:0.2
+ k8s.gcr.io/node-test:0.2
```
To skip specific tests, overwrite the environment variable `SKIP` with the
@@ -81,7 +81,7 @@ regular expression of tests you want to skip.
sudo docker run -it --rm --privileged --net=host \
-v /:/rootfs:ro -v $CONFIG_DIR:$CONFIG_DIR -v $LOG_DIR:/var/result \
-e SKIP=MirrorPod \ # Run all conformance tests but skip MirrorPod test
- gcr.io/google_containers/node-test:0.2
+ k8s.gcr.io/node-test:0.2
```
Node conformance test is a containerized version of [node e2e test](https://github.com/kubernetes/community/blob/{{page.githubbranch}}/contributors/devel/e2e-node-tests.md).
diff --git a/docs/api-reference/v1.9/index.html b/docs/api-reference/v1.9/index.html
index 18cc2917db..c255107dc7 100644
--- a/docs/api-reference/v1.9/index.html
+++ b/docs/api-reference/v1.9/index.html
@@ -56950,7 +56950,7 @@ Appears In:
names string array
-
Names by which this image is known. e.g. ["gcr.io/google_containers/hyperkube:v1.0.7", "dockerhub.io/google_containers/hyperkube:v1.0.7"]
+
Names by which this image is known. e.g. ["k8s.gcr.io/hyperkube:v1.0.7", "dockerhub.io/google_containers/hyperkube:v1.0.7"]
sizeBytes integer
diff --git a/docs/concepts/architecture/cloud-controller.md b/docs/concepts/architecture/cloud-controller.md
index 12d5e13c53..fe87703e9a 100644
--- a/docs/concepts/architecture/cloud-controller.md
+++ b/docs/concepts/architecture/cloud-controller.md
@@ -97,7 +97,7 @@ The Node controller contains the cloud-dependent functionality of the kubelet. P
In this new model, the kubelet initializes a node without cloud-specific information. However, it adds a taint to the newly created node that makes the node unschedulable until the CCM initializes the node with cloud-specific information, and then removes this taint.
-### 3. Kubernets API server
+### 3. Kubernetes API server
The PersistentVolumeLabels controller moves the cloud-dependent functionality of the Kubernetes API server to the CCM as described in the preceding sections.
@@ -174,7 +174,7 @@ v1/ServiceAccount:
The RBAC ClusterRole for the CCM looks like this:
```yaml
-apiVersion: rbac.authorization.k8s.io/v1beta1
+apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
name: cloud-controller-manager
diff --git a/docs/concepts/architecture/nodes.md b/docs/concepts/architecture/nodes.md
index 4cc4424111..27b9e01e30 100644
--- a/docs/concepts/architecture/nodes.md
+++ b/docs/concepts/architecture/nodes.md
@@ -265,7 +265,7 @@ metadata:
spec:
containers:
- name: sleep-forever
- image: gcr.io/google_containers/pause:0.8.0
+ image: k8s.gcr.io/pause:0.8.0
resources:
requests:
cpu: 100m
diff --git a/docs/concepts/cluster-administration/controller-metrics.md b/docs/concepts/cluster-administration/controller-metrics.md
index ceca94f7de..2f1c71e34a 100644
--- a/docs/concepts/cluster-administration/controller-metrics.md
+++ b/docs/concepts/cluster-administration/controller-metrics.md
@@ -13,10 +13,10 @@ the controller manager.
Controller manager metrics provide important insight into the performance and health of the controller manager.
These metrics include common Go language runtime metrics such as go_routine count and controller specific metrics such as
-etcd request latencies or Cloudprovider (AWS, GCE, Openstack) API latencies that can be used
+etcd request latencies or Cloudprovider (AWS, GCE, OpenStack) API latencies that can be used
to gauge the health of a cluster.
-Starting from Kubernetes 1.7, detailed Cloudprovider metrics are available for storage operations for GCE, AWS, Vsphere and Openstack.
+Starting from Kubernetes 1.7, detailed Cloudprovider metrics are available for storage operations for GCE, AWS, Vsphere and OpenStack.
These metrics can be used to monitor health of persistent volume operations.
For example, for GCE these metrics are called:
diff --git a/docs/concepts/cluster-administration/device-plugins.md b/docs/concepts/cluster-administration/device-plugins.md
index 310c2793df..b688e774a2 100644
--- a/docs/concepts/cluster-administration/device-plugins.md
+++ b/docs/concepts/cluster-administration/device-plugins.md
@@ -65,7 +65,7 @@ The general workflow of a device plugin includes the following steps:
```gRPC
service DevicePlugin {
// ListAndWatch returns a stream of List of Devices
- // Whenever a Device state change or a Device disapears, ListAndWatch
+ // Whenever a Device state change or a Device disappears, ListAndWatch
// returns the new list
rpc ListAndWatch(Empty) returns (stream ListAndWatchResponse) {}
@@ -107,8 +107,10 @@ in the plugin's
## Examples
-For an example device plugin implementation, see
-[nvidia GPU device plugin for COS base OS](https://github.com/GoogleCloudPlatform/container-engine-accelerators/tree/master/cmd/nvidia_gpu).
+For examples of device plugin implementations, see:
+* The official [NVIDIA GPU device plugin](https://github.com/NVIDIA/k8s-device-plugin)
+ * it requires using [nvidia-docker 2.0](https://github.com/NVIDIA/nvidia-docker) which allows you to run GPU enabled docker containers
+* The [NVIDIA GPU device plugin for COS base OS](https://github.com/GoogleCloudPlatform/container-engine-accelerators/tree/master/cmd/nvidia_gpu).
{% endcapture %}
diff --git a/docs/concepts/cluster-administration/two-files-counter-pod-agent-sidecar.yaml b/docs/concepts/cluster-administration/two-files-counter-pod-agent-sidecar.yaml
index 9737f13493..b37b616e6f 100644
--- a/docs/concepts/cluster-administration/two-files-counter-pod-agent-sidecar.yaml
+++ b/docs/concepts/cluster-administration/two-files-counter-pod-agent-sidecar.yaml
@@ -22,7 +22,7 @@ spec:
- name: varlog
mountPath: /var/log
- name: count-agent
- image: gcr.io/google_containers/fluentd-gcp:1.30
+ image: k8s.gcr.io/fluentd-gcp:1.30
env:
- name: FLUENTD_ARGS
value: -c /etc/fluentd-config/fluentd.conf
diff --git a/docs/concepts/configuration/manage-compute-resources-container.md b/docs/concepts/configuration/manage-compute-resources-container.md
index cced47f00b..16ce9419d5 100644
--- a/docs/concepts/configuration/manage-compute-resources-container.md
+++ b/docs/concepts/configuration/manage-compute-resources-container.md
@@ -285,7 +285,7 @@ Conditions:
Events:
FirstSeen LastSeen Count From SubobjectPath Reason Message
Tue, 07 Jul 2015 12:53:51 -0700 Tue, 07 Jul 2015 12:53:51 -0700 1 {scheduler } scheduled Successfully assigned simmemleak-hra99 to kubernetes-node-tf0f
- Tue, 07 Jul 2015 12:53:51 -0700 Tue, 07 Jul 2015 12:53:51 -0700 1 {kubelet kubernetes-node-tf0f} implicitly required container POD pulled Pod container image "gcr.io/google_containers/pause:0.8.0" already present on machine
+ Tue, 07 Jul 2015 12:53:51 -0700 Tue, 07 Jul 2015 12:53:51 -0700 1 {kubelet kubernetes-node-tf0f} implicitly required container POD pulled Pod container image "k8s.gcr.io/pause:0.8.0" already present on machine
Tue, 07 Jul 2015 12:53:51 -0700 Tue, 07 Jul 2015 12:53:51 -0700 1 {kubelet kubernetes-node-tf0f} implicitly required container POD created Created with docker id 6a41280f516d
Tue, 07 Jul 2015 12:53:51 -0700 Tue, 07 Jul 2015 12:53:51 -0700 1 {kubelet kubernetes-node-tf0f} implicitly required container POD started Started with docker id 6a41280f516d
Tue, 07 Jul 2015 12:53:51 -0700 Tue, 07 Jul 2015 12:53:51 -0700 1 {kubelet kubernetes-node-tf0f} spec.containers{simmemleak} created Created with docker id 87348f12526a
@@ -312,7 +312,7 @@ Kubernetes version 1.8 introduces a new resource, _ephemeral-storage_ for managi
This partition is “ephemeral” and applications cannot expect any performance SLAs (Disk IOPS for example) from this partition. Local ephemeral storage management only applies for the root partition; the optional partition for image layer and writable layer is out of scope.
-**Note:** If an optional runntime partition is used, root partition will not hold any image layer or writable layers.
+**Note:** If an optional runtime partition is used, root partition will not hold any image layer or writable layers.
{: .note}
### Requests and limits setting for local ephemeral storage
diff --git a/docs/concepts/configuration/pod-with-node-affinity.yaml b/docs/concepts/configuration/pod-with-node-affinity.yaml
index 7c38e19997..253d2b21ea 100644
--- a/docs/concepts/configuration/pod-with-node-affinity.yaml
+++ b/docs/concepts/configuration/pod-with-node-affinity.yaml
@@ -23,4 +23,4 @@ spec:
- another-node-label-value
containers:
- name: with-node-affinity
- image: gcr.io/google_containers/pause:2.0
\ No newline at end of file
+ image: k8s.gcr.io/pause:2.0
\ No newline at end of file
diff --git a/docs/concepts/configuration/pod-with-pod-affinity.yaml b/docs/concepts/configuration/pod-with-pod-affinity.yaml
index 3728537d5a..1897af901f 100644
--- a/docs/concepts/configuration/pod-with-pod-affinity.yaml
+++ b/docs/concepts/configuration/pod-with-pod-affinity.yaml
@@ -26,4 +26,4 @@ spec:
topologyKey: kubernetes.io/hostname
containers:
- name: with-pod-affinity
- image: gcr.io/google_containers/pause:2.0
+ image: k8s.gcr.io/pause:2.0
diff --git a/docs/concepts/configuration/secret.md b/docs/concepts/configuration/secret.md
index ee8f85d4b5..54db877ce6 100644
--- a/docs/concepts/configuration/secret.md
+++ b/docs/concepts/configuration/secret.md
@@ -618,7 +618,7 @@ spec:
secretName: dotfile-secret
containers:
- name: dotfile-test-container
- image: gcr.io/google_containers/busybox
+ image: k8s.gcr.io/busybox
command:
- ls
- "-l"
diff --git a/docs/concepts/overview/components.md b/docs/concepts/overview/components.md
index 52fcd42175..debb1f98b6 100644
--- a/docs/concepts/overview/components.md
+++ b/docs/concepts/overview/components.md
@@ -58,8 +58,8 @@ The following controllers have cloud provider dependencies:
### kube-scheduler
-[kube-scheduler](/docs/admin/kube-scheduler/) watches newly created pods that have no node assigned, and
-selects a node for them to run on.
+[kube-scheduler](/docs/admin/kube-scheduler/) watches newly created pods that
+are not assigned to any node, and selects a node for them to run on.
### addons
diff --git a/docs/concepts/services-networking/ingress.md b/docs/concepts/services-networking/ingress.md
index 256410d4cc..d33e2d8e71 100644
--- a/docs/concepts/services-networking/ingress.md
+++ b/docs/concepts/services-networking/ingress.md
@@ -224,7 +224,7 @@ Note that there is a gap between TLS features supported by various Ingress contr
### Loadbalancing
-An Ingress controller is bootstrapped with some load balancing policy settings that it applies to all Ingress, such as the load balancing algorithm, backend weight scheme, and others. More advanced load balancing concepts (e.g.: persistent sessions, dynamic weights) are not yet exposed through the Ingress. You can still get these features through the [service loadbalancer](https://git.k8s.io/contrib/service-loadbalancer). With time, we plan to distill load balancing patterns that are applicable cross platform into the Ingress resource.
+An Ingress controller is bootstrapped with some load balancing policy settings that it applies to all Ingress, such as the load balancing algorithm, backend weight scheme, and others. More advanced load balancing concepts (e.g.: persistent sessions, dynamic weights) are not yet exposed through the Ingress. You can still get these features through the [service loadbalancer](https://github.com/kubernetes/ingress-nginx/blob/master/docs/catalog.md). With time, we plan to distill load balancing patterns that are applicable cross platform into the Ingress resource.
It's also worth noting that even though health checks are not exposed directly through the Ingress, there exist parallel concepts in Kubernetes such as [readiness probes](/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/) which allow you to achieve the same end result. Please review the controller specific docs to see how they handle health checks ([nginx](https://git.k8s.io/ingress-nginx/README.md), [GCE](https://git.k8s.io/ingress-gce/README.md#health-checks)).
diff --git a/docs/concepts/services-networking/service.md b/docs/concepts/services-networking/service.md
index ddbca9c9a0..6c4ccbed87 100644
--- a/docs/concepts/services-networking/service.md
+++ b/docs/concepts/services-networking/service.md
@@ -193,15 +193,15 @@ having working [readiness probes](/docs/tasks/configure-pod-container/configure-
{% assign for_k8s_version="v1.9" %}{% include feature-state-beta.md %}
In this mode, kube-proxy watches Kubernetes `services` and `endpoints`,
-call `netlink` interface create ipvs rules accordingly and sync ipvs rules with Kubernetes
+calls `netlink` interface to create ipvs rules accordingly and syncs ipvs rules with Kubernetes
`services` and `endpoints` periodically, to make sure ipvs status is
-consistent with the expectation. When access the `service`, traffic will
-be redirect to one of the backend `pod`.
+consistent with the expectation. When `service` is accessed, traffic will
+be redirected to one of the backend `pod`s.
-Similar to iptables, Ipvs is based on netfilter hook function, but use hash
-table as the underlying data structure and work in the kernal state.
-That means ipvs redirects traffic can be much faster, and have much
-better performance when sync proxy rules. Furthermore, ipvs provides more
+Similar to iptables, Ipvs is based on netfilter hook function, but uses hash
+table as the underlying data structure and works in the kernel space.
+That means ipvs redirects traffic much faster, and has much
+better performance when syncing proxy rules. Furthermore, ipvs provides more
options for load balancing algorithm, such as:
- rr: round-robin
@@ -211,7 +211,7 @@ options for load balancing algorithm, such as:
- sed: shortest expected delay
- nq: never queue
-**Note:** ipvs mode assumed IPVS kernel modules are installed on the node
+**Note:** ipvs mode assumes IPVS kernel modules are installed on the node
before running kube-proxy. When kube-proxy starts with ipvs proxy mode,
kube-proxy would validate if IPVS modules are installed on the node, if
it's not installed kube-proxy will fall back to iptables proxy mode.
diff --git a/docs/concepts/storage/persistent-volumes.md b/docs/concepts/storage/persistent-volumes.md
index 059202db28..bc7a57c913 100644
--- a/docs/concepts/storage/persistent-volumes.md
+++ b/docs/concepts/storage/persistent-volumes.md
@@ -125,7 +125,7 @@ spec:
path: /any/path/it/will/be/replaced
containers:
- name: pv-recycler
- image: "gcr.io/google_containers/busybox"
+ image: "k8s.gcr.io/busybox"
command: ["/bin/sh", "-c", "test -e /scrub && rm -rf /scrub/..?* /scrub/.[!.]* /scrub/* && test -z \"$(ls -A /scrub)\" || exit 1"]
volumeMounts:
- name: vol
@@ -218,24 +218,24 @@ resizing to take place. Also, file system resizing is only supported for followi
Each PV contains a spec and status, which is the specification and status of the volume.
```yaml
- apiVersion: v1
- kind: PersistentVolume
- metadata:
- name: pv0003
- spec:
- capacity:
- storage: 5Gi
- volumeMode: Filesystem
- accessModes:
- - ReadWriteOnce
- persistentVolumeReclaimPolicy: Recycle
- storageClassName: slow
- mountOptions:
- - hard
- - nfsvers=4.1
- nfs:
- path: /tmp
- server: 172.17.0.2
+apiVersion: v1
+kind: PersistentVolume
+metadata:
+ name: pv0003
+spec:
+ capacity:
+ storage: 5Gi
+ volumeMode: Filesystem
+ accessModes:
+ - ReadWriteOnce
+ persistentVolumeReclaimPolicy: Recycle
+ storageClassName: slow
+ mountOptions:
+ - hard
+ - nfsvers=4.1
+ nfs:
+ path: /tmp
+ server: 172.17.0.2
```
### Capacity
diff --git a/docs/concepts/storage/volumes.md b/docs/concepts/storage/volumes.md
index 247c593d75..2c5ccf492d 100644
--- a/docs/concepts/storage/volumes.md
+++ b/docs/concepts/storage/volumes.md
@@ -131,7 +131,7 @@ metadata:
name: test-ebs
spec:
containers:
- - image: gcr.io/google_containers/test-webserver
+ - image: k8s.gcr.io/test-webserver
name: test-container
volumeMounts:
- mountPath: /test-ebs
@@ -246,7 +246,7 @@ metadata:
name: test-pd
spec:
containers:
- - image: gcr.io/google_containers/test-webserver
+ - image: k8s.gcr.io/test-webserver
name: test-container
volumeMounts:
- mountPath: /cache
@@ -326,7 +326,7 @@ metadata:
name: test-pd
spec:
containers:
- - image: gcr.io/google_containers/test-webserver
+ - image: k8s.gcr.io/test-webserver
name: test-container
volumeMounts:
- mountPath: /test-pd
@@ -432,7 +432,7 @@ metadata:
name: test-pd
spec:
containers:
- - image: gcr.io/google_containers/test-webserver
+ - image: k8s.gcr.io/test-webserver
name: test-container
volumeMounts:
- mountPath: /test-pd
@@ -665,7 +665,7 @@ metadata:
name: test-portworx-volume-pod
spec:
containers:
- - image: gcr.io/google_containers/test-webserver
+ - image: k8s.gcr.io/test-webserver
name: test-container
volumeMounts:
- mountPath: /mnt
@@ -736,7 +736,7 @@ metadata:
name: pod-0
spec:
containers:
- - image: gcr.io/google_containers/test-webserver
+ - image: k8s.gcr.io/test-webserver
name: pod-0
volumeMounts:
- mountPath: /test-pd
@@ -866,7 +866,7 @@ metadata:
name: test-vmdk
spec:
containers:
- - image: gcr.io/google_containers/test-webserver
+ - image: k8s.gcr.io/test-webserver
name: test-container
volumeMounts:
- mountPath: /test-vmdk
diff --git a/docs/concepts/workloads/controllers/statefulset.md b/docs/concepts/workloads/controllers/statefulset.md
index 0fd76d4c8d..8fa4c6f8c7 100644
--- a/docs/concepts/workloads/controllers/statefulset.md
+++ b/docs/concepts/workloads/controllers/statefulset.md
@@ -87,7 +87,7 @@ spec:
terminationGracePeriodSeconds: 10
containers:
- name: nginx
- image: gcr.io/google_containers/nginx-slim:0.8
+ image: k8s.gcr.io/nginx-slim:0.8
ports:
- containerPort: 80
name: web
diff --git a/docs/concepts/workloads/pods/pod-lifecycle.md b/docs/concepts/workloads/pods/pod-lifecycle.md
index 3bf5f80a53..8e22ec2556 100644
--- a/docs/concepts/workloads/pods/pod-lifecycle.md
+++ b/docs/concepts/workloads/pods/pod-lifecycle.md
@@ -198,7 +198,7 @@ spec:
containers:
- args:
- /server
- image: gcr.io/google_containers/liveness
+ image: k8s.gcr.io/liveness
livenessProbe:
httpGet:
# when "host" is not defined, "PodIP" will be used
diff --git a/docs/concepts/workloads/pods/pod.md b/docs/concepts/workloads/pods/pod.md
index 64d3008b2d..c07608e601 100644
--- a/docs/concepts/workloads/pods/pod.md
+++ b/docs/concepts/workloads/pods/pod.md
@@ -32,7 +32,9 @@ Containers within a pod share an IP address and port space, and
can find each other via `localhost`. They can also communicate with each
other using standard inter-process communications like SystemV semaphores or
POSIX shared memory. Containers in different pods have distinct IP addresses
-and can not communicate by IPC.
+and can not communicate by IPC without
+[special configuration](/docs/concepts/policy/pod-security-policy/).
+These containers usually communicate with each other via Pod IP addresses.
Applications within a pod also have access to shared volumes, which are defined
as part of a pod and are made available to be mounted into each application's
diff --git a/docs/getting-started-guides/fluentd-gcp.yaml b/docs/getting-started-guides/fluentd-gcp.yaml
index a81427bdfc..d212752cca 100644
--- a/docs/getting-started-guides/fluentd-gcp.yaml
+++ b/docs/getting-started-guides/fluentd-gcp.yaml
@@ -14,7 +14,7 @@ spec:
dnsPolicy: Default
containers:
- name: fluentd-cloud-logging
- image: gcr.io/google_containers/fluentd-gcp:2.0.2
+ image: k8s.gcr.io/fluentd-gcp:2.0.2
# If fluentd consumes its own logs, the following situation may happen:
# fluentd fails to send a chunk to the server => writes it to the log =>
# tries to send this message to the server => fails to send a chunk and so on.
diff --git a/docs/getting-started-guides/minikube.md b/docs/getting-started-guides/minikube.md
index 470a452c11..57fbf6cadb 100644
--- a/docs/getting-started-guides/minikube.md
+++ b/docs/getting-started-guides/minikube.md
@@ -46,7 +46,7 @@ Running pre-create checks...
Creating machine...
Starting local Kubernetes cluster...
-$ kubectl run hello-minikube --image=gcr.io/google_containers/echoserver:1.4 --port=8080
+$ kubectl run hello-minikube --image=k8s.gcr.io/echoserver:1.4 --port=8080
deployment "hello-minikube" created
$ kubectl expose deployment hello-minikube --type=NodePort
service "hello-minikube" exposed
diff --git a/docs/home/contribute/write-new-topic.md b/docs/home/contribute/write-new-topic.md
index 95f57d2f3d..ccde10eb9f 100644
--- a/docs/home/contribute/write-new-topic.md
+++ b/docs/home/contribute/write-new-topic.md
@@ -27,7 +27,7 @@ is the best fit for your content:
Tutorial
-
A tutorial page shows how to accomplish a goal that ties together several Kubernetes features. A tutorial might provide several sequences of steps that readers can actually do as they read the page. Or it might provide explanations of related pieces of code. For example, a tutorial could provide a walkthrough of a code sample. A tutorial can include brief explanations of the Kubernetes features that are being tied togeter, but should link to related concept topics for deep explanations of individual features.
+
A tutorial page shows how to accomplish a goal that ties together several Kubernetes features. A tutorial might provide several sequences of steps that readers can actually do as they read the page. Or it might provide explanations of related pieces of code. For example, a tutorial could provide a walkthrough of a code sample. A tutorial can include brief explanations of the Kubernetes features that are being tied together, but should link to related concept topics for deep explanations of individual features.
diff --git a/docs/reference/generated/kubefed_init.md b/docs/reference/generated/kubefed_init.md
index b8920cb603..d58736792e 100644
--- a/docs/reference/generated/kubefed_init.md
+++ b/docs/reference/generated/kubefed_init.md
@@ -40,13 +40,13 @@ kubefed init FEDERATION_NAME --host-cluster-context=HOST_CONTEXT
--dns-provider-config string Config file path on local file system for configuring DNS provider.
--dns-zone-name string DNS suffix for this federation. Federated Service DNS names are published with this suffix.
--dry-run dry run without sending commands to server.
- --etcd-image string Image to use for etcd server. (default "gcr.io/google_containers/etcd:3.1.10")
+ --etcd-image string Image to use for etcd server. (default "k8s.gcr.io/etcd:3.1.10")
--etcd-persistent-storage Use persistent volume for etcd. Defaults to 'true'. (default true)
--etcd-pv-capacity string Size of persistent volume claim to be used for etcd. (default "10Gi")
--etcd-pv-storage-class string The storage class of the persistent volume claim used for etcd. Must be provided if a default storage class is not enabled for the host cluster.
--federation-system-namespace string Namespace in the host cluster where the federation system components are installed (default "federation-system")
--host-cluster-context string Host cluster context
- --image string Image to use for federation API server and controller manager binaries. (default "gcr.io/google_containers/hyperkube-amd64:v0.0.0-master_$Format:%h$")
+ --image string Image to use for federation API server and controller manager binaries. (default "k8s.gcr.io/hyperkube-amd64:v0.0.0-master_$Format:%h$")
--image-pull-policy string PullPolicy describes a policy for if/when to pull a container image. The default pull policy is IfNotPresent which will not pull an image if it already exists. (default "IfNotPresent")
--image-pull-secrets string Provide secrets that can access the private registry.
--kubeconfig string Path to the kubeconfig file to use for CLI requests.
diff --git a/docs/reference/generated/kubelet.md b/docs/reference/generated/kubelet.md
index 0f3cdf79f1..c97c0bc95c 100644
--- a/docs/reference/generated/kubelet.md
+++ b/docs/reference/generated/kubelet.md
@@ -167,7 +167,7 @@ VolumeScheduling=true|false (ALPHA - default=false)
--node-status-update-frequency duration Specifies how often kubelet posts node status to master. Note: be cautious when changing the constant, it must work with nodeMonitorGracePeriod in nodecontroller. (default 10s)
--oom-score-adj int32 The oom-score-adj value for kubelet process. Values must be within the range [-1000, 1000] (default -999)
--pod-cidr string The CIDR to use for pod IP addresses, only used in standalone mode. In cluster mode, this is obtained from the master.
- --pod-infra-container-image string The image whose network/ipc namespaces containers in each pod will use. (default "gcr.io/google_containers/pause-amd64:3.0")
+ --pod-infra-container-image string The image whose network/ipc namespaces containers in each pod will use. (default "k8s.gcr.io/pause-amd64:3.0")
--pod-manifest-path string Path to the directory containing pod manifest files to run, or the path to a single pod manifest file. Files starting with dots will be ignored.
--pods-per-core int32 Number of Pods per core that can run on this Kubelet. The total number of Pods on this Kubelet cannot exceed max-pods, so max-pods will be used if this calculation results in a larger number of Pods allowed on the Kubelet. A value of 0 disables this limit.
--port int32 The port for the Kubelet to serve on. (default 10250)
diff --git a/docs/reference/generated/kubernetes-api/v1.9/index.html b/docs/reference/generated/kubernetes-api/v1.9/index.html
index 0f81fe78e8..ee5ea737b1 100644
--- a/docs/reference/generated/kubernetes-api/v1.9/index.html
+++ b/docs/reference/generated/kubernetes-api/v1.9/index.html
@@ -520,6 +520,10 @@ Appears In:
The maximum number of pods that can be scheduled above the desired number of pods. Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%). This can not be 0 if MaxUnavailable is 0. Absolute number is calculated from percentage by rounding up. Defaults to 25%. Example: when this is set to 30%, the new RC can be scaled up immediately when the rolling update starts, such that the total number of old and new pods do not exceed 130% of desired pods. Once old pods have been killed, new RC can be scaled up further, ensuring that total number of pods running at any time during the update is atmost 130% of desired pods.
+
The maximum number of pods that can be scheduled above the desired number of pods. Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%). This can not be 0 if MaxUnavailable is 0. Absolute number is calculated from percentage by rounding up. Defaults to 25%. Example: when this is set to 30%, the new RC can be scaled up immediately when the rolling update starts, such that the total number of old and new pods do not exceed 130% of desired pods. Once old pods have been killed, new RC can be scaled up further, ensuring that total number of pods running at any time during the update is at most 130% of desired pods.
FlexVolume represents a generic volume resource that is provisioned/attached using an exec based plugin. This is an alpha feature and may change in future.
+
FlexVolume represents a generic volume resource that is provisioned/attached using an exec based plugin.
FlexVolume represents a generic volume resource that is provisioned/attached using an exec based plugin. This is an alpha feature and may change in future.
+
FlexVolume represents a generic volume resource that is provisioned/attached using an exec based plugin.
Names by which this image is known. e.g. ["gcr.io/google_containers/hyperkube:v1.0.7", "dockerhub.io/google_containers/hyperkube:v1.0.7"]
+
Names by which this image is known. e.g. ["k8s.gcr.io/hyperkube:v1.0.7", "dockerhub.io/google_containers/hyperkube:v1.0.7"]
sizeBytes integer
@@ -61247,7 +61249,7 @@ Appears In:
-
FlexVolume represents a generic volume resource that is provisioned/attached using an exec based plugin. This is an alpha feature and may change in future.
+
FlexVolume represents a generic volume resource that is provisioned/attached using an exec based plugin.