For those who want to deploy usememos using Kubernetes

[scipsycho]

For the most part, the details are very similar to how one would deploy using docker compose. However, the issue came with the GRPC and HTTP protocol of which Memos uses both. I for one, don't have any HTTPS/TLS support in my homelab, so it might have been more difficult for me.

This may have become more convoluted as I am using Kubernetes's Gateway api instead of any other proxy to route the traffic.

My setup:

• Kubernetes (v1.30.3)
• Cilium (1.17.6)

Below are the manifest for different components:

apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: usememos
  labels:
    app: usememos
spec:
  replicas: 1
  serviceName: usememos-service
  selector:
    matchLabels:
      app: usememos
  template:
    metadata:
      labels:
        app: usememos
    spec:
      restartPolicy: Always
      containers:
      - name: memos
        image: neosmemo/memos:stable
        envFrom:
          - secretRef:
              name: memos-db-secret. #I have the variables required for Postgres here
        env:
        - name: MEMOS_DRIVER
          value: postgres
        - name: MEMOS_MODE
          value: prod
        ports:
        - containerPort: 5230
          name: memos-web-ui
        volumeMounts:
        - mountPath: /var/opt/memos
          name: memos
          subPath: data
      volumes:
      - name: memos
        persistentVolumeClaim:
          claimName: memos-pvc

The main aspects of this are the Service and the HTTPRoute.

For service, I did this:

apiVersion: v1
kind: Service
metadata:
  name: usememos-service
spec:
  clusterIP: None
  selector:
    app: usememos
  ports:
  - port: 10001
    name: grpc-port
    targetPort: memos-web-ui
    protocol: TCP
    appProtocol: kubernetes.io/h2c
  - port: 10002
    name: http-port
    targetPort: memos-web-ui
    protocol: TCP

I observed that the http calls made via the browser for this would be in http/1 which won't work with GRPC's requirement of http/2. So, I created two ports for different app protocols pointing to the same container port.

Then, in HTTPRoute, I just used this:

apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
  name: usememos-route
spec:
  parentRefs:
  - name: main-gateway
  hostnames:
  - "<hostname>"
  rules:
  - matches:
    - path:
        type: RegularExpression
        value: "/grpc.*". #for any GRPC help methods
    backendRefs:
    - name: usememos-service
      port: 10001
  - matches:
    - path:
        type: RegularExpression
        value: "/memos.api.v1.*". #for GRPC methods used by the usememos.
    backendRefs:
    - name: usememos-service
      port: 10001
  - backendRefs:
    - name: usememos-service
      port: 10002

I didn't use GRPCRoute as I found that HTTPRoute was able to handle it normally. However, in case that doesn't happen, a similar setup should work for both GRPCRoute and HTTPRoute.