From 9afdfa2b74641bcab698de662a19cc7e86c3094a Mon Sep 17 00:00:00 2001 From: Suraj Deshmukh Date: Tue, 25 Oct 2016 22:59:15 +0530 Subject: [PATCH] Use daemonset in docker registry add on Using daemonset to bring up a pod on each node of cluster, right now the docs suggests to bring up a pod on each node by manually dropping the pod manifests into directory /etc/kubernetes/manifests. --- cluster/addons/registry/README.md | 51 +++++++++++-------- .../kube-registry-proxy.yaml | 51 +++++++++++-------- 2 files changed, 62 insertions(+), 40 deletions(-) diff --git a/cluster/addons/registry/README.md b/cluster/addons/registry/README.md index cef1f1f3633..155487c3350 100644 --- a/cluster/addons/registry/README.md +++ b/cluster/addons/registry/README.md @@ -175,33 +175,44 @@ spec: Now that we have a running `Service`, we need to expose it onto each Kubernetes `Node` so that Docker will see it as `localhost`. We can load a `Pod` on every -node by dropping a YAML file into the kubelet config directory -(/etc/kubernetes/manifests by default). +node by creating following daemonset. ```yaml -apiVersion: v1 -kind: Pod +apiVersion: extensions/v1beta1 +kind: DaemonSet metadata: name: kube-registry-proxy namespace: kube-system + labels: + k8s-app: kube-registry + kubernetes.io/cluster-service: "true" + version: v0.4 spec: - containers: - - name: kube-registry-proxy - image: gcr.io/google_containers/kube-registry-proxy:0.4 - resources: - limits: - cpu: 100m - memory: 50Mi - env: - - name: REGISTRY_HOST - value: kube-registry.kube-system.svc.cluster.local - - name: REGISTRY_PORT - value: "5000" - ports: - - name: registry - containerPort: 80 - hostPort: 5000 + template: + metadata: + labels: + k8s-app: kube-registry + kubernetes.io/name: "kube-registry-proxy" + kubernetes.io/cluster-service: "true" + version: v0.4 + spec: + containers: + - name: kube-registry-proxy + image: gcr.io/google_containers/kube-registry-proxy:0.4 + resources: + limits: + cpu: 100m + memory: 50Mi + env: + - name: REGISTRY_HOST + value: kube-registry.kube-system.svc.cluster.local + - name: REGISTRY_PORT + value: "5000" + ports: + - name: registry + containerPort: 80 + hostPort: 5000 ``` diff --git a/cluster/saltbase/salt/kube-registry-proxy/kube-registry-proxy.yaml b/cluster/saltbase/salt/kube-registry-proxy/kube-registry-proxy.yaml index 14f92256019..f00142ad65f 100644 --- a/cluster/saltbase/salt/kube-registry-proxy/kube-registry-proxy.yaml +++ b/cluster/saltbase/salt/kube-registry-proxy/kube-registry-proxy.yaml @@ -1,24 +1,35 @@ -apiVersion: v1 -kind: Pod +apiVersion: extensions/v1beta1 +kind: DaemonSet metadata: name: kube-registry-proxy namespace: kube-system + labels: + k8s-app: kube-registry + kubernetes.io/cluster-service: "true" + version: v0.4 spec: - containers: - - name: kube-registry-proxy - image: gcr.io/google_containers/kube-registry-proxy:0.3 - resources: - limits: - cpu: 100m - memory: 50Mi - env: - - name: REGISTRY_HOST - value: kube-registry.kube-system.svc.cluster.local - - name: REGISTRY_PORT - value: "5000" - - name: FORWARD_PORT - value: "5000" - ports: - - name: registry - containerPort: 5000 - hostPort: 5000 + template: + metadata: + labels: + k8s-app: kube-registry + kubernetes.io/name: "kube-registry-proxy" + kubernetes.io/cluster-service: "true" + version: v0.4 + spec: + containers: + - name: kube-registry-proxy + image: gcr.io/google_containers/kube-registry-proxy:0.4 + resources: + limits: + cpu: 100m + memory: 50Mi + env: + - name: REGISTRY_HOST + value: kube-registry.kube-system.svc.cluster.local + - name: REGISTRY_PORT + value: "5000" + ports: + - name: registry + containerPort: 80 + hostPort: 5000 +