purge meilisearch from chart

chart/Chart.yaml

@@ -9,10 +9,6 @@ appVersion: "0.0.0"
 icon: https://raw.githubusercontent.com/zoriya/Kyoo/refs/heads/master/icons/icon.svg
 
 dependencies:
-- condition: meilisearch.enabled
-  name: meilisearch
-  repository: https://meilisearch.github.io/meilisearch-kubernetes
-  version: 0.17.1
 - condition: postgresql.enabled
   name: postgresql
   repository: https://charts.bitnami.com/bitnami

chart/README.md

@@ -1,5 +1,5 @@
 # Kyoo Helm Chart
-Kyoo consists of multiple interconnected workloads, leveraging a variety of technologies including Meilisearch, Postgres, and RabbitMQ.  This helm chart is designed to simplify configurations for basic setups while offering advanced customization options.  Naming and opinionation aims to follow structures described in [diagrams](../DIAGRAMS.md).
+Kyoo consists of multiple interconnected workloads, leveraging a variety of technologies including Postgres, and RabbitMQ.  This helm chart is designed to simplify configurations for basic setups while offering advanced customization options.  Naming and opinionation aims to follow structures described in [diagrams](../DIAGRAMS.md).
 
 # Examples
 ## Quickstart
@@ -12,8 +12,6 @@ helm upgrade kyoo oci://ghcr.io/zoriya/helm-charts/kyoo --install --values myval
 ```yaml
 kyoo:
   address: https://kyoo.mydomain.com
-meilisearch:
-  enabled: true
 postgresql:
   enabled: true
 rabbitmq:
@@ -50,9 +48,6 @@ values.yaml configuration
 ```yaml
 # specify external hosts for backend resources
 global:
-  meilisearch:
-    kyoo_back:
-      host: meilisearch
   postgres:
     kyoo_back:
       host: postgres
@@ -106,7 +101,7 @@ stringData:
 Kyoo consists of multiple microservices.  Best practice is for each microservice to use its own database.  Kyoo workloads support best practices or sharing a single postgres database.  Please see the `POSTGRES_SCHEMA` setting for additional information.  Strongly recomended to use a Kubernetes operator for managing Postgres.
 
 ## Subchart Support
-Subcharts are updated frequently and subject to changes.  This chart includes subcharts for deploying Meilisearch, PostgreSQL, and RabbitMQ.  Please consider hosting those independently of Kyoo to better handle versioning and lifecycle management.
+Subcharts are updated frequently and subject to changes.  This chart includes subcharts for deploying PostgreSQL, and RabbitMQ.  Please consider hosting those independently of Kyoo to better handle versioning and lifecycle management.
 
 # v5 ForwardAuth Requirement
 Starting with v5, Kyoo leverages ForwardAuth middleware for offloading auth from the microservices onto a gateway.  For additional reading, please see gateway-api sigs [documentation](https://gateway-api.sigs.k8s.io/geps/gep-1494/). 

chart/templates/back/deployment.yaml

@@ -126,13 +126,6 @@ spec:
               value: {{ .Values.global.rabbitmq.host | quote }}
             - name: RABBITMQ_PORT
               value: {{ .Values.global.rabbitmq.port | quote }}
-            - name: MEILI_HOST
-              value: "{{ .Values.global.meilisearch.proto }}://{{ .Values.global.meilisearch.host }}:{{ .Values.global.meilisearch.port }}"
-            - name: MEILI_MASTER_KEY
-              valueFrom:
-                secretKeyRef:
-                  key: {{ .Values.global.meilisearch.kyoo_back.masterkeyKey }}
-                  name: {{ .Values.global.meilisearch.kyoo_back.existingSecret }}
             {{- range $index, $provider := .Values.kyoo.oidc_providers }}
             - name: OIDC_{{ $provider.name | upper }}_NAME
               value: {{ $provider.name | quote }}

chart/values.yaml

@@ -15,21 +15,6 @@ global:
   podLabels: {}
   extraEnv: []
 
-  # kyoo connectivity & subchart settings for meilisearch
-  # subchart configuration can be found at .meilisearch
-  meilisearch:
-    proto: http
-    host: kyoo-meilisearch
-    port: 7700
-    # subchart specific settings
-    infra:
-      # subchart does not support specifying keyname.
-      # key must be named `MEILI_MASTER_KEY`
-      existingSecret: bigsecret
-    # kyoo_back workload specific settings
-    kyoo_back:
-      masterkeyKey: MEILI_MASTER_KEY
-      existingSecret: bigsecret
   # kyoo connectivity & subchart settings for postgres
   # subchart configuration can be found at .postgresql
   postgres:
@@ -480,19 +465,6 @@ traefikproxy:
   extraInitContainers: []
   extraVolumes: []
 
-# subchart settings
-meilisearch:
-  enabled: false
-  environment:
-    MEILI_ENV: production
-  auth:
-    # subchart does not support specifying keyname.
-    # key must be named `MEILI_MASTER_KEY`
-    existingMasterKeySecret: "{{ .Values.global.meilisearch.infra.existingSecret }}"
-  persistence:
-    enabled: true
-    size: 3Gi
-
 # subchart settings
 postgresql:
   enabled: false