Serve legacy Modmail logs with Barium

kubernetes/namespaces/modmail/README.md

@@ -1,12 +1,15 @@
 # Modmail
 
-This folder contains the manifests for our Modmail service.
+This namespace runs our Modmail system.
 
-## Secrets
+| Component | Description |
+| --------- | ----------- |
+| Polonium (`polonium-api`, `polonium-bot`) | The current Modmail bot. Its manifests are not in this directory. |
+| [`barium/`](./barium) | Read-only viewer for logs from the **legacy** Modmail bot, so old `modmail.pydis.wtf/logs/<key>` links keep working. |
+
+The legacy Modmail bot and its web logviewer have been retired. Their logs were exported from MongoDB
+and are now served statically by Barium.
 
-The services require one shared secret called `modmail` containing the following:
+## Secrets
 
-| Key                     | Value                            | Description                                                  |
-| ------------------------| ---------------------------------|--------------------------------------------------------------|
-| `CONNECTION_URI`        | MongoDB connection URI           | Used for storing data                                        |
-| `TOKEN`                 | Discord Token                    | Used to connect to Discord                                   |
+The `modmail` secret is shared by the Polonium deployments.

kubernetes/namespaces/modmail/barium/README.md

@@ -0,0 +1,8 @@
+# Barium
+Static viewer for logs from the legacy Modmail bot. Serves pre-rendered logs at `/logs/<key>`
+(the original `modmail.pydis.wtf` URLs) and a SQLite index for client-side search.
+
+The image (`ghcr.io/owl-corp/barium`) is private, as it contains the archived logs, and is built
+locally from a Modmail export (see the [barium repo](https://github.com/owl-corp/barium)). It needs
+no secrets, and is exposed on `modmail.pydis.wtf` through the `modmail-pydis-wtf` route in
+`nginx-gateway/routes/service-routes/`.

kubernetes/namespaces/modmail/web/deployment.yaml → kubernetes/namespaces/modmail/barium/deployment.yaml

@@ -1,38 +1,41 @@
 apiVersion: apps/v1
 kind: Deployment
 metadata:
-  name: modmail-web
+  name: barium
   namespace: modmail
 spec:
   replicas: 1
   selector:
     matchLabels:
-      app: modmail-web
+      app: barium
   template:
     metadata:
       labels:
-        app: modmail-web
+        app: barium
     spec:
       containers:
-        - name: modmail-web
-          image: ghcr.io/python-discord/logviewer:latest
+        - name: barium
+          image: ghcr.io/owl-corp/barium:latest
           imagePullPolicy: Always
           resources:
             requests:
               cpu: 50m
-              memory: 100Mi
+              memory: 64Mi
             limits:
-              cpu: 100m
-              memory: 150Mi
+              cpu: 200m
+              memory: 128Mi
           ports:
             - containerPort: 8000
-          envFrom:
-            - secretRef:
-                name: modmail
-            - configMapRef:
-                name: modmail-config-env
+          volumeMounts:
+            - name: tmp
+              mountPath: /tmp
           securityContext:
             readOnlyRootFilesystem: true
+      volumes:
+        - name: tmp
+          emptyDir: {}
+      imagePullSecrets:
+        - name: ghcr-pull-secret
       securityContext:
         fsGroup: 2000
         runAsUser: 1000

kubernetes/namespaces/modmail/web/service.yaml → kubernetes/namespaces/modmail/barium/service.yaml

@@ -1,11 +1,11 @@
 apiVersion: v1
 kind: Service
 metadata:
-  name: modmail-web
+  name: barium
   namespace: modmail
 spec:
   selector:
-    app: modmail-web
+    app: barium
   ports:
     - protocol: TCP
       port: 80

kubernetes/namespaces/nginx-gateway/routes/service-routes/modmail-pydis-wtf.yaml

@@ -11,7 +11,7 @@ spec:
       namespace: nginx-gateway
   rules:
     - backendRefs:
-      - name: modmail-web
+      - name: barium
         namespace: modmail
         port: 80
       filters: