From 277d91969b6ed25c5844aeb40612368915a29c52 Mon Sep 17 00:00:00 2001 From: Sridhar Gaddam Date: Fri, 6 Nov 2020 12:06:31 +0530 Subject: [PATCH] Exclude openshift-monitoring namespace in Globalnet In an OCP Cluster, openshift-monitoring namespace has couple of services and these are controlled by their respective operators. When Globalnet is deployed on OCP, it was seen that globalip annotation added to such services are periodically getting deleted by the operators, 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-monitoring 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 7a52eac..2f8729a 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' + value: 'submariner-operator,kube-system,operators,openshift-monitoring' - name: SUBMARINER_NAMESPACE value: '{{ .Release.Namespace }}' securityContext: