From 8f2bed6191b147907310ed723ad9ab30072d18cc Mon Sep 17 00:00:00 2001 From: Sridhar Gaddam Date: Wed, 18 Nov 2020 16:46:03 +0530 Subject: [PATCH] Exclude openshift-dns namespace in Globalnet In an OCP Cluster, openshift-dns namespace has dns-default service and this is controlled by its operator. When Globalnet is deployed on OCP, it was seen that globalip annotation added to it is periodically getting deleted by the operator, so Globalnet tries to re-add the annotation and this goes on forever. This will cause Globalnet to consume CPU unnecessarily and could affect user-experience with Submariner Globalnet. We have plans to enhance Globalnet to improve its scalability, but until then we can exclude annotating services in openshift-dns namespace. Signed-Off-by: Sridhar Gaddam --- submariner/templates/globalnet.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/submariner/templates/globalnet.yaml b/submariner/templates/globalnet.yaml index 2f8729a..45e69a0 100644 --- a/submariner/templates/globalnet.yaml +++ b/submariner/templates/globalnet.yaml @@ -36,7 +36,7 @@ spec: - name: SUBMARINER_CLUSTERID value: '{{ .Values.submariner.clusterId }}' - name: SUBMARINER_EXCLUDENS - value: 'submariner-operator,kube-system,operators,openshift-monitoring' + value: 'submariner-operator,kube-system,operators,openshift-monitoring,openshift-dns' - name: SUBMARINER_NAMESPACE value: '{{ .Release.Namespace }}' securityContext: