Meilisearch UI in Kubernetes context

[nitrix78]

Hello, I use mealisearch self-hosted in a kube like this : https://gitlab.cri.epita.fr/forge/infra/infrastructure/-/blob/475b795d145cb16018f636ca1c14a4ea80f4d8c2/k8s/apps/intranet/base/meilisearch.yml
So, meilisearch is on a dedicated pod and meilisearch-ui is on another.

I need to set up a service and ingress on my meilisearch-ui pod to access it from outside my Kubernetes cluster.

However, this isn't working because the API calls are now redirecting to my meilisearch service (http://meilisearch -srv:7700), which is visible from the pod inside my Kubernetes cluster, but not from outside where I'm browsing.
To make it work, I also need to set up a service and ingress on my meilisearch pod, but that's a major security vulnerability.

Do you have a solution?

apiVersion: apps/v1
kind: Deployment
metadata:
  name: meilisearch-ui
spec:
  replicas: 1
  selector:
    matchLabels:
      app: meilisearch-ui
  template:
    metadata:
      labels:
        app: meilisearch-ui
    spec:
      containers:
        - name: meilisearch-ui
          image: riccoxie/meilisearch-ui
          env:
            - name: SINGLETON_MODE
              value: "true"  # pour voir le pod meilisearch
            - name: SINGLETON_HOST
              #value: "http://meilisearch-srv:7700"  # That i want
              value: "https://meilisearch.uat.v2.mydomain.com"  # That i do make
            - name: SINGLETON_API_KEY
              valueFrom:
                secretKeyRef:
                  name: meilisearch-master-key
                  key: masterkey
          ports:
            - containerPort: 24900

[eyeix]

@nitrix78
Unfortunately, the current implementation method of Meilisearch-UI cannot meet this scenario because all meilisearch connection requests of this SPA app are based on the JS SDK on the browser side.

[nitrix78]

OK, thank you.