Operations Documentation

Operations documentation for Legemiddelgrunndata (repository nompd): what runs where, and how to operate it. It is written for engineers who deploy, monitor, and troubleshoot the service.

Facts here are taken from the repository (manifests/, .gitlab-ci.yml, backend/src/Api). Items that cannot be verified from the repository are marked TODO: and must be confirmed in GitLab, ArgoCD, or the cluster.

Contents

Environments

• Environments overview — dev, test, and prod side by side, plus how changes reach each environment
• dev
• test
• prod

Runbooks

• Deploy and promote
• Rollback
• Database migrations
• Sync jobs (FEST and upstream)
• Backup and restore
• Secrets and API keys
• Monitoring, logs, and alerts
• Incident troubleshooting checklist

Open items

• Open items (TODO summary) — unverified or missing information to resolve

Related documentation

Deeper, design-level documentation lives in docs/system:

• Deployment
• Configuration
• Sync Pipeline
• Error Handling
• Database Backup and Restore
• OpenBao Setup
• Code flow through environments

Conventions

• Application resources live in the namespaces lmgd-dev, lmgd-test, and lmgd-prod. Commands use kubectl -n lmgd-<env>.
• Never paste secret values into documentation, tickets, or chat. Refer to secret names, keys, and OpenBao paths only.