From cb64f4fb31b166f41d7e672754bc076a76541dd6 Mon Sep 17 00:00:00 2001 From: Yiping Kang Date: Tue, 23 Apr 2024 11:37:04 -0400 Subject: [PATCH] [elastic] Add fsGroup to security context for permission issue for elastic AND enable CORS (#1241) * Add fsGroup to security context for permission issue for elastic * enable CORS for elastic --- jaseci_core/jaseci/jsorc/manifests/elastic.yaml | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/jaseci_core/jaseci/jsorc/manifests/elastic.yaml b/jaseci_core/jaseci/jsorc/manifests/elastic.yaml index 532b9b682d..b357d3355d 100644 --- a/jaseci_core/jaseci/jsorc/manifests/elastic.yaml +++ b/jaseci_core/jaseci/jsorc/manifests/elastic.yaml @@ -5639,6 +5639,7 @@ spec: serviceAccountName: elastic-operator securityContext: runAsNonRoot: true + fsGroup: 65534 containers: - image: "docker.elastic.co/eck/eck-operator:2.7.0" imagePullPolicy: IfNotPresent @@ -6000,6 +6001,10 @@ spec: count: 1 config: node.store.allow_mmap: false + http.cors.enabled: true + http.cors.allow-origin: "*" + http.cors.allow-methods: OPTIONS, POST, GET + http.cors.allow-headers: X-Requested-With, X-Auth-Token, Content-Type, Content-Length, Authorization, Access-Control-Allow-Headers, Accept volumeClaimTemplates: - metadata: name: elasticsearch-data