From 3c9f05a85110aadd9dfddb2603c7c3ce836330e0 Mon Sep 17 00:00:00 2001 From: Yuvi Panda Date: Fri, 19 May 2017 10:44:28 -0700 Subject: [PATCH] Use DaemonSet for nginx kubeadm deployment example This is a much better default fit than a default deployment, since you get to hit any node for it to work (rather than a deployment, which could end up anywhere) --- .../deployment/nginx/kubeadm/nginx-ingress-controller.yaml | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/examples/deployment/nginx/kubeadm/nginx-ingress-controller.yaml b/examples/deployment/nginx/kubeadm/nginx-ingress-controller.yaml index 299d39b37..faaa54453 100644 --- a/examples/deployment/nginx/kubeadm/nginx-ingress-controller.yaml +++ b/examples/deployment/nginx/kubeadm/nginx-ingress-controller.yaml @@ -51,14 +51,13 @@ spec: k8s-app: default-http-backend --- apiVersion: extensions/v1beta1 -kind: Deployment +kind: DaemonSet metadata: name: nginx-ingress-controller labels: k8s-app: nginx-ingress-controller namespace: kube-system spec: - replicas: 1 template: metadata: labels: