Deploy in kubernetes - meilisearch-ui doesn't see meilisearch pod

[nitrix78]

Hello,
I'm using in kubernetes with argocd like this:
https://gitlab.cri.epita.fr/forge/infra/infrastructure/-/blob/d7e6b06470e1cbdfec493c3e94bd31cd295d0194/k8s/apps/intranet/base/meilisearch.yml
I have added meilisearch-ui Deployment, the pod run correctly, but don't see the pod instance of meilisearch.

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_HOST
              value: "http://meilisearch-srv:7700"  # service meilisearch name
            - name: SINGLETON_API_KEY
              valueFrom:
                secretKeyRef:
                  name: meilisearch-master-key
                  key: masterkey
          ports:
            - containerPort: 24900

Do yi have to set other variables ?

[eyeix]

According to this, it seems that your environment variables configuration is missing the item 'SINGLETON_MODE=true'.

[nitrix78]

Yes i added it, but it doesn't work. I have the error: Something went wrong! Request to http://meilisearch-srv:7700/stats has failed.

1. The Meilisearch service is ok "status | Meilisearch is running" on port 7700.
2. The Meilisearch-ui pod is running well: Processed routes in 709ms
   ➜ Local: http://localhost:24900/
   ➜ Network: http://[myIp]:24900/
3. The Meilisearch-ui pod can see the Meilisearch service with "curl -v http://meilisearch-srv:7700" command.
4. If i remove SINGLETON_MODE and i run Meilisearch and Meilisearch-ui in local by "port-forward", Meilisearch-ui can connect to Meilisearch (typing the host and key manualy in UI) and see the datas.

[eyeix]

Could u paste some console & networks logs in dev panel with error happened?

[nitrix78]

In Meilisearch-ui page: Singleton mode detected! Connection fail! Running with invalid instance config, you must have set correct instance env config before launch.
I see in network console that the path of route has: "GET | http://meilisearch-srv:7700/stats".
But it's an internal kubernetes access.. I don't want give him external access.
I think it miss a mapper or bridge...
I tryed to add service resource for Meilisearch-ui and a traefik IngressRoute resource, but it's the same think.

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"  # le service Elasticsearch
            - name: SINGLETON_API_KEY
              valueFrom:
                secretKeyRef:
                  name: meilisearch-master-key
                  key: masterkey
          ports:
            - containerPort: 24900
---
apiVersion: v1
kind: Service
metadata:
  name: meilisearch-ui-srv
spec:
  type: ClusterIP # ClusterIP, NodePort ou LoadBalancer
  ports:
    - port: 24900
      targetPort: 24900
  selector:
    app: meilisearch-ui
---
apiVersion: traefik.containo.us/v1alpha1
kind: IngressRoute
metadata:
  name: meilisearch-ui-ingressroute
spec:
  entryPoints:
    - web
    - websecure
  routes:  
    - kind: Rule
      match: "Host(`meilisearch-ui.uat.domain.com`)"
      services:
        - name: meilisearch-ui-srv
          port: 24900
  tls:
    secretName: meilisearch-ui-dns

[eyeix]

Just as mentioned in the discussion, it seems that we know why this singleton pattern doesn't work