fix: enable triples generator and event log to call themselves

SwissDataScienceCenter · Nov 20, 2024 · a7c6156 · a7c6156
1 parent 62065a4
commit a7c6156
Showing 1 changed file with 12 additions and 0 deletions.
diff --git a/helm-chart/renku/templates/network-policies.yaml b/helm-chart/renku/templates/network-policies.yaml
@@ -796,6 +796,12 @@ spec:
             matchLabels:
               app: {{ template "renku.graph.commitEventService.name" . }}
               release: {{ .Release.Name }}
+        - podSelector:
+            matchLabels:
+              # The event log calls itself via a k8s service so if it is not allowed in the 
+              # network policy like this then those requests fail.
+              app: {{ template "renku.graph.eventLog.name" . }}
+              release: {{ .Release.Name }}
       ports:
         - protocol: TCP
           port: http-event-log
@@ -872,6 +878,12 @@ spec:
             matchLabels:
               app: {{ template "renku.graph.knowledgeGraph.name" . }}
               release: {{ .Release.Name }}
+        - podSelector:
+            matchLabels:
+              # The triples generator calls itself via a k8s service so if it is not allowed in the 
+              # network policy like this then those requests fail.
+              app: {{ template "renku.graph.triplesGenerator.name" . }}
+              release: {{ .Release.Name }}
       ports:
         - protocol: TCP
           port: http-triples-gn