Deploy on Kubernetes | Loggo Documentation

There’s no packaged Helm chart yet, but Loggo drops right into a cluster with a StatefulSet or Deployment paired with a PersistentVolumeClaim. The manifests below are a starting point — adapt names, namespace, and resource limits to your cluster.

Create a PersistentVolumeClaim

Holds your SQLite database and markdown mirror files.

Apply the Deployment and Service

kubectl apply -f the manifests below.

Expose the Service

Point your cluster’s Ingress, Gateway, or LoadBalancer at it.

PersistentVolumeClaim

loggo-pvc.yamlyaml

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: loggo-data
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 1Gi

Deployment

loggo-deployment.yamlyaml

apiVersion: apps/v1
kind: Deployment
metadata:
  name: loggo
spec:
  replicas: 1
  selector:
    matchLabels:
      app: loggo
  template:
    metadata:
      labels:
        app: loggo
    spec:
      containers:
        - name: loggo
          image: ghcr.io/loggo-dev/loggo:latest
          ports:
            - containerPort: 3000
          volumeMounts:
            - name: loggo-data
              mountPath: /app/data
      volumes:
        - name: loggo-data
          persistentVolumeClaim:
            claimName: loggo-data

Service

loggo-service.yamlyaml

apiVersion: v1
kind: Service
metadata:
  name: loggo
spec:
  selector:
    app: loggo
  ports:
    - port: 80
      targetPort: 3000

Apply

kubectl apply -f loggo-pvc.yaml -f loggo-deployment.yaml -f loggo-service.yaml