From 6f21f624a45882af0c8b526dcedd4e55e7f29dcb Mon Sep 17 00:00:00 2001 From: Russell Bryant Date: Fri, 26 Jul 2019 11:38:52 -0400 Subject: [PATCH] assets: Drop ingress-controller manifest. The intention of this manifest was to change the node selector so that the ingress controller would run on masters. This manifest is owned by the ingress operator, so our changes would just get overwritten. In my local cluster, that does appear to be the case and there's no node selector setting at all. --- assets/templates/99_ingress-controller.yaml | 13 ------------- 1 file changed, 13 deletions(-) delete mode 100644 assets/templates/99_ingress-controller.yaml diff --git a/assets/templates/99_ingress-controller.yaml b/assets/templates/99_ingress-controller.yaml deleted file mode 100644 index 15af43418..000000000 --- a/assets/templates/99_ingress-controller.yaml +++ /dev/null @@ -1,13 +0,0 @@ -apiVersion: operator.openshift.io/v1 -kind: IngressController -metadata: - name: default - namespace: openshift-ingress-operator -spec: - replicas: 3 - endpointPublishingStrategy: - type: HostNetwork - nodePlacement: - nodeSelector: - node-role.kubernetes.io/master: "" -