infra/stacks/grampsweb/main.tf

381 lines
9.4 KiB
Terraform
Raw Normal View History

variable "tls_secret_name" {
type = string
sensitive = true
}
2026-02-23 22:05:28 +00:00
variable "nfs_server" { type = string }
resource "kubernetes_manifest" "external_secret" {
manifest = {
apiVersion = "external-secrets.io/v1beta1"
kind = "ExternalSecret"
metadata = {
name = "grampsweb-secrets"
namespace = "grampsweb"
}
spec = {
refreshInterval = "15m"
secretStoreRef = {
name = "vault-kv"
kind = "ClusterSecretStore"
}
target = {
name = "grampsweb-secrets"
}
dataFrom = [{
extract = {
key = "grampsweb"
}
}]
}
}
depends_on = [kubernetes_namespace.grampsweb]
}
data "kubernetes_secret" "eso_secrets" {
metadata {
name = "grampsweb-secrets"
namespace = kubernetes_namespace.grampsweb.metadata[0].name
}
depends_on = [kubernetes_manifest.external_secret]
}
locals {
mailserver_accounts = jsondecode(data.kubernetes_secret.eso_secrets.data["mailserver_accounts"])
}
2026-02-23 22:05:28 +00:00
variable "redis_host" { type = string }
variable "mail_host" { type = string }
resource "kubernetes_namespace" "grampsweb" {
metadata {
name = "grampsweb"
labels = {
tier = local.tiers.aux
}
}
[infra] Suppress Goldilocks vpa-update-mode label drift on all namespaces [ci skip] ## Context Wave 3B-continued: the Goldilocks VPA dashboard (stacks/vpa) runs a Kyverno ClusterPolicy `goldilocks-vpa-auto-mode` that mutates every namespace with `metadata.labels["goldilocks.fairwinds.com/vpa-update-mode"] = "off"`. This is intentional — Terraform owns container resource limits, and Goldilocks should only provide recommendations, never auto-update. The label is how Goldilocks decides per-namespace whether to run its VPA in `off` mode. Effect on Terraform: every `kubernetes_namespace` resource shows the label as pending-removal (`-> null`) on every `scripts/tg plan`. Dawarich survey 2026-04-18 confirmed the drift. Cluster-side count: 88 namespaces carry the label (`kubectl get ns -o json | jq ... | wc -l`). Every TF-managed namespace is affected. This commit brings the intentional admission drift under the same `# KYVERNO_LIFECYCLE_V1` discoverability marker introduced in c9d221d5 for the ndots dns_config pattern. The marker now stands generically for any Kyverno admission-webhook drift suppression; the inline comment records which specific policy stamps which specific field so future grep audits show why each suppression exists. ## This change 107 `.tf` files touched — every stack's `resource "kubernetes_namespace"` resource gets: ```hcl lifecycle { # KYVERNO_LIFECYCLE_V1: goldilocks-vpa-auto-mode ClusterPolicy stamps this label on every namespace ignore_changes = [metadata[0].labels["goldilocks.fairwinds.com/vpa-update-mode"]] } ``` Injection was done with a brace-depth-tracking Python pass (`/tmp/add_goldilocks_ignore.py`): match `^resource "kubernetes_namespace" ` → track `{` / `}` until the outermost closing brace → insert the lifecycle block before the closing brace. The script is idempotent (skips any file that already mentions `goldilocks.fairwinds.com/vpa-update-mode`) so re-running is safe. Vault stack picked up 2 namespaces in the same file (k8s-users produces one, plus a second explicit ns) — confirmed via file diff (+8 lines). ## What is NOT in this change - `stacks/trading-bot/main.tf` — entire file is `/* … */` commented out (paused 2026-04-06 per user decision). Reverted after the script ran. - `stacks/_template/main.tf.example` — per-stack skeleton, intentionally minimal. User keeps it that way. Not touched by the script (file has no real `resource "kubernetes_namespace"` — only a placeholder comment). - `.terraform/` copies (e.g. `stacks/metallb/.terraform/modules/...`) — gitignored, won't commit; the live path was edited. - `terraform fmt` cleanup of adjacent pre-existing alignment issues in authentik, freedify, hermes-agent, nvidia, vault, meshcentral. Reverted to keep the commit scoped to the Goldilocks sweep. Those files will need a separate fmt-only commit or will be cleaned up on next real apply to that stack. ## Verification Dawarich (one of the hundred-plus touched stacks) showed the pattern before and after: ``` $ cd stacks/dawarich && ../../scripts/tg plan Before: Plan: 0 to add, 2 to change, 0 to destroy. # kubernetes_namespace.dawarich will be updated in-place (goldilocks.fairwinds.com/vpa-update-mode -> null) # module.tls_secret.kubernetes_secret.tls_secret will be updated in-place (Kyverno generate.* labels — fixed in 8d94688d) After: No changes. Your infrastructure matches the configuration. ``` Injection count check: ``` $ rg -c 'KYVERNO_LIFECYCLE_V1: goldilocks-vpa-auto-mode' stacks/ | awk -F: '{s+=$2} END {print s}' 108 ``` ## Reproduce locally 1. `git pull` 2. Pick any stack: `cd stacks/<name> && ../../scripts/tg plan` 3. Expect: no drift on the namespace's goldilocks.fairwinds.com/vpa-update-mode label. Closes: code-dwx Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-18 21:15:27 +00:00
lifecycle {
# KYVERNO_LIFECYCLE_V1: goldilocks-vpa-auto-mode ClusterPolicy stamps this label on every namespace
ignore_changes = [metadata[0].labels["goldilocks.fairwinds.com/vpa-update-mode"]]
}
}
module "tls_secret" {
source = "../../modules/kubernetes/setup_tls_secret"
namespace = kubernetes_namespace.grampsweb.metadata[0].name
tls_secret_name = var.tls_secret_name
}
[grampsweb] Align PVC resource to encrypted storage; imported state ## Context Grampsweb stack had an empty Terraform state — 7 K8s resources (namespace, PVC, service, deployment, ingress, ExternalSecret manifest, TLS secret) existed in the cluster but weren't tracked. This blocked commit 7b248897 (ollama LLM env-var removal) from being applied because any apply would attempt to re-create existing resources. Additionally, the TF source declared a **grampsweb-data-proxmox** PVC on **storage_class=proxmox-lvm**, while the cluster had **grampsweb-data-encrypted** on **proxmox-lvm-encrypted** (1 Gi, bound). The deployment was referencing the encrypted PVC. This divergence predated this change — the source was simply out of date vs cluster reality. ## This change Two things: 1. **Source alignment** (the only file diff): - Renames `kubernetes_persistent_volume_claim.data_proxmox` → `data_encrypted`, metadata.name to match cluster, storage class to `proxmox-lvm-encrypted`. - Updates the deployment volume `claim_name` reference accordingly. - Aligns with the newer project convention documented in `.claude/CLAUDE.md`: "Default for sensitive data is proxmox-lvm-encrypted" and "Convention: PVC names end in `-encrypted`". - No destroy/recreate: the PVC and deployment already use the encrypted PVC in the cluster; TF source now just describes reality. 2. **State imports** (out-of-band, via `scripts/tg import`, not in diff): - `kubernetes_namespace.grampsweb` <- `grampsweb` - `kubernetes_persistent_volume_claim.data_encrypted` <- `grampsweb/grampsweb-data-encrypted` - `kubernetes_service.grampsweb` <- `grampsweb/grampsweb` - `kubernetes_deployment.grampsweb` <- `grampsweb/grampsweb` - `module.ingress.kubernetes_ingress_v1.proxied-ingress` <- `grampsweb/family` - `module.tls_secret.kubernetes_secret.tls_secret` <- `grampsweb/tls-secret` - `kubernetes_manifest.external_secret` <- `apiVersion=external-secrets.io/v1beta1,kind=ExternalSecret,namespace=grampsweb,name=grampsweb-secrets` ## Apply result `Apply complete! Resources: 0 added, 7 changed, 0 destroyed.` In-place updates applied: - Deployment: dropped `GRAMPSWEB_LLM_BASE_URL` + `GRAMPSWEB_LLM_MODEL` env vars (both containers) — realising the intent of commit 7b248897. - Ingress: realigned Traefik middleware annotation + cleaned stale `uptime.viktorbarzin.me/external-monitor=false` annotation. - TLS secret: removed Kyverno-generated labels (Kyverno's `sync-tls-secret` ClusterPolicy re-applies them on next reconcile — no functional impact; same pattern in 29 other stacks using `setup_tls_secret` module). - Namespace, PVC, service: trivial metadata alignments (label / `wait_until_bound` / `wait_for_load_balancer`). - `kubernetes_manifest.external_secret`: populated the `manifest` attribute after import (expected). ## What is NOT in this change - No replica bump: deployment stays at `replicas=0` (stack is intentionally inactive per 2026-03-14 OOM incident note). - No destroy/recreate of any resource. - The broader code-w97 (11 stacks with empty state) is NOT closed — only grampsweb is imported. 10 stacks remain: beads-server, insta2spotify, isponsorblocktv, kyverno, meshcentral, pvc-autoresizer, shadowsocks, tor-proxy, travel_blog, + meshcentral PVC. ## Reproduce locally ``` KUBECONFIG=/home/wizard/code/config kubectl get all,ingress,pvc,externalsecret,secret -n grampsweb # Deployment still replicas=0; PVC grampsweb-data-encrypted Bound; ingress 'family' # on family.viktorbarzin.me; ExternalSecret SecretSynced True. cd /home/wizard/code/infra/stacks/grampsweb /home/wizard/code/infra/scripts/tg plan # Expected: 'No changes.' (clean state after apply). ``` ## Test Plan ### Automated ``` $ cd /home/wizard/code/infra/stacks/grampsweb && /home/wizard/code/infra/scripts/tg plan Plan: 0 to add, 7 to change, 0 to destroy. [pre-apply] $ /home/wizard/code/infra/scripts/tg apply --non-interactive Plan: 0 to add, 7 to change, 0 to destroy. kubernetes_namespace.grampsweb: Modifications complete after 0s [id=grampsweb] kubernetes_persistent_volume_claim.data_encrypted: Modifications complete after 0s [id=grampsweb/grampsweb-data-encrypted] kubernetes_service.grampsweb: Modifications complete after 0s [id=grampsweb/grampsweb] module.ingress.kubernetes_ingress_v1.proxied-ingress: Modifications complete after 0s [id=grampsweb/family] module.tls_secret.kubernetes_secret.tls_secret: Modifications complete after 0s [id=grampsweb/tls-secret] kubernetes_manifest.external_secret: Modifications complete after 0s kubernetes_deployment.grampsweb: Modifications complete after 1s [id=grampsweb/grampsweb] Apply complete! Resources: 0 added, 7 changed, 0 destroyed. $ terraform fmt -check -recursive stacks/grampsweb (no output - formatted clean) ``` ### Manual Verification ``` $ KUBECONFIG=/home/wizard/code/config kubectl get all,ingress,pvc,externalsecret,secret -n grampsweb # - deployment.apps/grampsweb 0/0 0 0 47d (replicas=0 preserved) # - service/grampsweb ClusterIP 10.106.232.205:80/TCP # - persistentvolumeclaim/grampsweb-data-encrypted Bound pvc-c9a5dcf4... 1Gi RWO proxmox-lvm-encrypted # - ingress/family traefik family.viktorbarzin.me -> 10.0.20.200:80,443 # - externalsecret/grampsweb-secrets vault-kv 15m SecretSynced True # - secret/tls-secret kubernetes.io/tls # No pod crashes (no pods — replicas=0). ``` Closes: code-8m6
2026-04-18 11:37:45 +00:00
resource "kubernetes_persistent_volume_claim" "data_encrypted" {
wait_until_bound = false
metadata {
[grampsweb] Align PVC resource to encrypted storage; imported state ## Context Grampsweb stack had an empty Terraform state — 7 K8s resources (namespace, PVC, service, deployment, ingress, ExternalSecret manifest, TLS secret) existed in the cluster but weren't tracked. This blocked commit 7b248897 (ollama LLM env-var removal) from being applied because any apply would attempt to re-create existing resources. Additionally, the TF source declared a **grampsweb-data-proxmox** PVC on **storage_class=proxmox-lvm**, while the cluster had **grampsweb-data-encrypted** on **proxmox-lvm-encrypted** (1 Gi, bound). The deployment was referencing the encrypted PVC. This divergence predated this change — the source was simply out of date vs cluster reality. ## This change Two things: 1. **Source alignment** (the only file diff): - Renames `kubernetes_persistent_volume_claim.data_proxmox` → `data_encrypted`, metadata.name to match cluster, storage class to `proxmox-lvm-encrypted`. - Updates the deployment volume `claim_name` reference accordingly. - Aligns with the newer project convention documented in `.claude/CLAUDE.md`: "Default for sensitive data is proxmox-lvm-encrypted" and "Convention: PVC names end in `-encrypted`". - No destroy/recreate: the PVC and deployment already use the encrypted PVC in the cluster; TF source now just describes reality. 2. **State imports** (out-of-band, via `scripts/tg import`, not in diff): - `kubernetes_namespace.grampsweb` <- `grampsweb` - `kubernetes_persistent_volume_claim.data_encrypted` <- `grampsweb/grampsweb-data-encrypted` - `kubernetes_service.grampsweb` <- `grampsweb/grampsweb` - `kubernetes_deployment.grampsweb` <- `grampsweb/grampsweb` - `module.ingress.kubernetes_ingress_v1.proxied-ingress` <- `grampsweb/family` - `module.tls_secret.kubernetes_secret.tls_secret` <- `grampsweb/tls-secret` - `kubernetes_manifest.external_secret` <- `apiVersion=external-secrets.io/v1beta1,kind=ExternalSecret,namespace=grampsweb,name=grampsweb-secrets` ## Apply result `Apply complete! Resources: 0 added, 7 changed, 0 destroyed.` In-place updates applied: - Deployment: dropped `GRAMPSWEB_LLM_BASE_URL` + `GRAMPSWEB_LLM_MODEL` env vars (both containers) — realising the intent of commit 7b248897. - Ingress: realigned Traefik middleware annotation + cleaned stale `uptime.viktorbarzin.me/external-monitor=false` annotation. - TLS secret: removed Kyverno-generated labels (Kyverno's `sync-tls-secret` ClusterPolicy re-applies them on next reconcile — no functional impact; same pattern in 29 other stacks using `setup_tls_secret` module). - Namespace, PVC, service: trivial metadata alignments (label / `wait_until_bound` / `wait_for_load_balancer`). - `kubernetes_manifest.external_secret`: populated the `manifest` attribute after import (expected). ## What is NOT in this change - No replica bump: deployment stays at `replicas=0` (stack is intentionally inactive per 2026-03-14 OOM incident note). - No destroy/recreate of any resource. - The broader code-w97 (11 stacks with empty state) is NOT closed — only grampsweb is imported. 10 stacks remain: beads-server, insta2spotify, isponsorblocktv, kyverno, meshcentral, pvc-autoresizer, shadowsocks, tor-proxy, travel_blog, + meshcentral PVC. ## Reproduce locally ``` KUBECONFIG=/home/wizard/code/config kubectl get all,ingress,pvc,externalsecret,secret -n grampsweb # Deployment still replicas=0; PVC grampsweb-data-encrypted Bound; ingress 'family' # on family.viktorbarzin.me; ExternalSecret SecretSynced True. cd /home/wizard/code/infra/stacks/grampsweb /home/wizard/code/infra/scripts/tg plan # Expected: 'No changes.' (clean state after apply). ``` ## Test Plan ### Automated ``` $ cd /home/wizard/code/infra/stacks/grampsweb && /home/wizard/code/infra/scripts/tg plan Plan: 0 to add, 7 to change, 0 to destroy. [pre-apply] $ /home/wizard/code/infra/scripts/tg apply --non-interactive Plan: 0 to add, 7 to change, 0 to destroy. kubernetes_namespace.grampsweb: Modifications complete after 0s [id=grampsweb] kubernetes_persistent_volume_claim.data_encrypted: Modifications complete after 0s [id=grampsweb/grampsweb-data-encrypted] kubernetes_service.grampsweb: Modifications complete after 0s [id=grampsweb/grampsweb] module.ingress.kubernetes_ingress_v1.proxied-ingress: Modifications complete after 0s [id=grampsweb/family] module.tls_secret.kubernetes_secret.tls_secret: Modifications complete after 0s [id=grampsweb/tls-secret] kubernetes_manifest.external_secret: Modifications complete after 0s kubernetes_deployment.grampsweb: Modifications complete after 1s [id=grampsweb/grampsweb] Apply complete! Resources: 0 added, 7 changed, 0 destroyed. $ terraform fmt -check -recursive stacks/grampsweb (no output - formatted clean) ``` ### Manual Verification ``` $ KUBECONFIG=/home/wizard/code/config kubectl get all,ingress,pvc,externalsecret,secret -n grampsweb # - deployment.apps/grampsweb 0/0 0 0 47d (replicas=0 preserved) # - service/grampsweb ClusterIP 10.106.232.205:80/TCP # - persistentvolumeclaim/grampsweb-data-encrypted Bound pvc-c9a5dcf4... 1Gi RWO proxmox-lvm-encrypted # - ingress/family traefik family.viktorbarzin.me -> 10.0.20.200:80,443 # - externalsecret/grampsweb-secrets vault-kv 15m SecretSynced True # - secret/tls-secret kubernetes.io/tls # No pod crashes (no pods — replicas=0). ``` Closes: code-8m6
2026-04-18 11:37:45 +00:00
name = "grampsweb-data-encrypted"
namespace = kubernetes_namespace.grampsweb.metadata[0].name
annotations = {
"resize.topolvm.io/threshold" = "10%"
"resize.topolvm.io/increase" = "100%"
"resize.topolvm.io/storage_limit" = "5Gi"
}
}
spec {
access_modes = ["ReadWriteOnce"]
[grampsweb] Align PVC resource to encrypted storage; imported state ## Context Grampsweb stack had an empty Terraform state — 7 K8s resources (namespace, PVC, service, deployment, ingress, ExternalSecret manifest, TLS secret) existed in the cluster but weren't tracked. This blocked commit 7b248897 (ollama LLM env-var removal) from being applied because any apply would attempt to re-create existing resources. Additionally, the TF source declared a **grampsweb-data-proxmox** PVC on **storage_class=proxmox-lvm**, while the cluster had **grampsweb-data-encrypted** on **proxmox-lvm-encrypted** (1 Gi, bound). The deployment was referencing the encrypted PVC. This divergence predated this change — the source was simply out of date vs cluster reality. ## This change Two things: 1. **Source alignment** (the only file diff): - Renames `kubernetes_persistent_volume_claim.data_proxmox` → `data_encrypted`, metadata.name to match cluster, storage class to `proxmox-lvm-encrypted`. - Updates the deployment volume `claim_name` reference accordingly. - Aligns with the newer project convention documented in `.claude/CLAUDE.md`: "Default for sensitive data is proxmox-lvm-encrypted" and "Convention: PVC names end in `-encrypted`". - No destroy/recreate: the PVC and deployment already use the encrypted PVC in the cluster; TF source now just describes reality. 2. **State imports** (out-of-band, via `scripts/tg import`, not in diff): - `kubernetes_namespace.grampsweb` <- `grampsweb` - `kubernetes_persistent_volume_claim.data_encrypted` <- `grampsweb/grampsweb-data-encrypted` - `kubernetes_service.grampsweb` <- `grampsweb/grampsweb` - `kubernetes_deployment.grampsweb` <- `grampsweb/grampsweb` - `module.ingress.kubernetes_ingress_v1.proxied-ingress` <- `grampsweb/family` - `module.tls_secret.kubernetes_secret.tls_secret` <- `grampsweb/tls-secret` - `kubernetes_manifest.external_secret` <- `apiVersion=external-secrets.io/v1beta1,kind=ExternalSecret,namespace=grampsweb,name=grampsweb-secrets` ## Apply result `Apply complete! Resources: 0 added, 7 changed, 0 destroyed.` In-place updates applied: - Deployment: dropped `GRAMPSWEB_LLM_BASE_URL` + `GRAMPSWEB_LLM_MODEL` env vars (both containers) — realising the intent of commit 7b248897. - Ingress: realigned Traefik middleware annotation + cleaned stale `uptime.viktorbarzin.me/external-monitor=false` annotation. - TLS secret: removed Kyverno-generated labels (Kyverno's `sync-tls-secret` ClusterPolicy re-applies them on next reconcile — no functional impact; same pattern in 29 other stacks using `setup_tls_secret` module). - Namespace, PVC, service: trivial metadata alignments (label / `wait_until_bound` / `wait_for_load_balancer`). - `kubernetes_manifest.external_secret`: populated the `manifest` attribute after import (expected). ## What is NOT in this change - No replica bump: deployment stays at `replicas=0` (stack is intentionally inactive per 2026-03-14 OOM incident note). - No destroy/recreate of any resource. - The broader code-w97 (11 stacks with empty state) is NOT closed — only grampsweb is imported. 10 stacks remain: beads-server, insta2spotify, isponsorblocktv, kyverno, meshcentral, pvc-autoresizer, shadowsocks, tor-proxy, travel_blog, + meshcentral PVC. ## Reproduce locally ``` KUBECONFIG=/home/wizard/code/config kubectl get all,ingress,pvc,externalsecret,secret -n grampsweb # Deployment still replicas=0; PVC grampsweb-data-encrypted Bound; ingress 'family' # on family.viktorbarzin.me; ExternalSecret SecretSynced True. cd /home/wizard/code/infra/stacks/grampsweb /home/wizard/code/infra/scripts/tg plan # Expected: 'No changes.' (clean state after apply). ``` ## Test Plan ### Automated ``` $ cd /home/wizard/code/infra/stacks/grampsweb && /home/wizard/code/infra/scripts/tg plan Plan: 0 to add, 7 to change, 0 to destroy. [pre-apply] $ /home/wizard/code/infra/scripts/tg apply --non-interactive Plan: 0 to add, 7 to change, 0 to destroy. kubernetes_namespace.grampsweb: Modifications complete after 0s [id=grampsweb] kubernetes_persistent_volume_claim.data_encrypted: Modifications complete after 0s [id=grampsweb/grampsweb-data-encrypted] kubernetes_service.grampsweb: Modifications complete after 0s [id=grampsweb/grampsweb] module.ingress.kubernetes_ingress_v1.proxied-ingress: Modifications complete after 0s [id=grampsweb/family] module.tls_secret.kubernetes_secret.tls_secret: Modifications complete after 0s [id=grampsweb/tls-secret] kubernetes_manifest.external_secret: Modifications complete after 0s kubernetes_deployment.grampsweb: Modifications complete after 1s [id=grampsweb/grampsweb] Apply complete! Resources: 0 added, 7 changed, 0 destroyed. $ terraform fmt -check -recursive stacks/grampsweb (no output - formatted clean) ``` ### Manual Verification ``` $ KUBECONFIG=/home/wizard/code/config kubectl get all,ingress,pvc,externalsecret,secret -n grampsweb # - deployment.apps/grampsweb 0/0 0 0 47d (replicas=0 preserved) # - service/grampsweb ClusterIP 10.106.232.205:80/TCP # - persistentvolumeclaim/grampsweb-data-encrypted Bound pvc-c9a5dcf4... 1Gi RWO proxmox-lvm-encrypted # - ingress/family traefik family.viktorbarzin.me -> 10.0.20.200:80,443 # - externalsecret/grampsweb-secrets vault-kv 15m SecretSynced True # - secret/tls-secret kubernetes.io/tls # No pod crashes (no pods — replicas=0). ``` Closes: code-8m6
2026-04-18 11:37:45 +00:00
storage_class_name = "proxmox-lvm-encrypted"
resources {
requests = {
storage = "1Gi"
}
}
}
lifecycle {
# The autoresizer expands requests.storage up to storage_limit and
# PVCs can't shrink. Without this, every TF apply tries to revert
# to the spec value, K8s rejects the shrink, and the PVC ends up
# in Terminating-but-in-use limbo.
ignore_changes = [spec[0].resources[0].requests]
}
}
resource "random_password" "secret_key" {
length = 64
special = false
}
locals {
common_env = [
{
name = "GRAMPSWEB_TREE"
value = "Gramps Web"
},
{
name = "GRAMPSWEB_SECRET_KEY"
value = random_password.secret_key.result
},
{
name = "GRAMPSWEB_CELERY_CONFIG__broker_url"
2026-02-23 22:05:28 +00:00
value = "redis://${var.redis_host}:6379/2"
},
{
name = "GRAMPSWEB_CELERY_CONFIG__result_backend"
2026-02-23 22:05:28 +00:00
value = "redis://${var.redis_host}:6379/2"
},
{
name = "GRAMPSWEB_RATELIMIT_STORAGE_URI"
2026-02-23 22:05:28 +00:00
value = "redis://${var.redis_host}:6379/3"
},
{
name = "GRAMPSWEB_BASE_URL"
value = "https://family.viktorbarzin.me"
},
{
name = "GRAMPSWEB_REGISTRATION_DISABLED"
value = "True"
},
{
name = "GRAMPSWEB_EMAIL_HOST"
2026-02-23 22:05:28 +00:00
value = var.mail_host
},
{
name = "GRAMPSWEB_EMAIL_PORT"
value = "587"
},
{
name = "GRAMPSWEB_EMAIL_HOST_USER"
value = "info@viktorbarzin.me"
},
{
name = "GRAMPSWEB_EMAIL_HOST_PASSWORD"
value = local.mailserver_accounts["info@viktorbarzin.me"]
},
{
name = "GRAMPSWEB_EMAIL_USE_SSL"
value = "False"
},
{
name = "GRAMPSWEB_EMAIL_USE_STARTTLS"
value = "True"
},
{
name = "GRAMPSWEB_DEFAULT_FROM_EMAIL"
value = "info@viktorbarzin.me"
},
]
}
resource "kubernetes_deployment" "grampsweb" {
metadata {
name = "grampsweb"
namespace = kubernetes_namespace.grampsweb.metadata[0].name
labels = {
app = "grampsweb"
tier = local.tiers.aux
}
}
spec {
# Disabled: grampsweb uses ~1.8GB actual memory with 3GB limit per replica.
# Not actively used — disabled to reduce cluster memory pressure (2026-03-14 node2 OOM incident).
replicas = 0
strategy {
type = "Recreate"
}
selector {
match_labels = {
app = "grampsweb"
}
}
template {
metadata {
labels = {
app = "grampsweb"
}
annotations = {
"dependency.kyverno.io/wait-for" = "redis-master.redis:6379"
}
}
spec {
container {
name = "grampsweb"
image = "ghcr.io/gramps-project/grampsweb:latest"
port {
container_port = 5000
}
dynamic "env" {
for_each = local.common_env
content {
name = env.value.name
value = env.value.value
}
}
volume_mount {
name = "data"
mount_path = "/app/users"
sub_path = "users"
}
volume_mount {
name = "data"
mount_path = "/app/indexdir"
sub_path = "indexdir"
}
volume_mount {
name = "data"
mount_path = "/app/thumbnail_cache"
sub_path = "thumbnail_cache"
}
volume_mount {
name = "data"
mount_path = "/app/cache"
sub_path = "cache"
}
volume_mount {
name = "data"
mount_path = "/app/secret"
sub_path = "secret"
}
volume_mount {
name = "data"
mount_path = "/root/.gramps/grampsdb"
sub_path = "grampsdb"
}
volume_mount {
name = "data"
mount_path = "/app/media"
sub_path = "media"
}
volume_mount {
name = "data"
mount_path = "/tmp"
sub_path = "tmp"
}
resources {
requests = {
cpu = "50m"
memory = "512Mi"
}
limits = {
memory = "512Mi"
}
}
}
container {
name = "grampsweb-celery"
image = "ghcr.io/gramps-project/grampsweb:latest"
command = ["celery", "-A", "gramps_webapi.celery", "worker", "--loglevel=INFO", "--concurrency=2"]
dynamic "env" {
for_each = local.common_env
content {
name = env.value.name
value = env.value.value
}
}
volume_mount {
name = "data"
mount_path = "/app/users"
sub_path = "users"
}
volume_mount {
name = "data"
mount_path = "/app/indexdir"
sub_path = "indexdir"
}
volume_mount {
name = "data"
mount_path = "/app/thumbnail_cache"
sub_path = "thumbnail_cache"
}
volume_mount {
name = "data"
mount_path = "/app/cache"
sub_path = "cache"
}
volume_mount {
name = "data"
mount_path = "/app/secret"
sub_path = "secret"
}
volume_mount {
name = "data"
mount_path = "/root/.gramps/grampsdb"
sub_path = "grampsdb"
}
volume_mount {
name = "data"
mount_path = "/app/media"
sub_path = "media"
}
volume_mount {
name = "data"
mount_path = "/tmp"
sub_path = "tmp"
}
resources {
requests = {
cpu = "50m"
memory = "256Mi"
}
limits = {
memory = "256Mi"
}
}
}
volume {
name = "data"
persistent_volume_claim {
[grampsweb] Align PVC resource to encrypted storage; imported state ## Context Grampsweb stack had an empty Terraform state — 7 K8s resources (namespace, PVC, service, deployment, ingress, ExternalSecret manifest, TLS secret) existed in the cluster but weren't tracked. This blocked commit 7b248897 (ollama LLM env-var removal) from being applied because any apply would attempt to re-create existing resources. Additionally, the TF source declared a **grampsweb-data-proxmox** PVC on **storage_class=proxmox-lvm**, while the cluster had **grampsweb-data-encrypted** on **proxmox-lvm-encrypted** (1 Gi, bound). The deployment was referencing the encrypted PVC. This divergence predated this change — the source was simply out of date vs cluster reality. ## This change Two things: 1. **Source alignment** (the only file diff): - Renames `kubernetes_persistent_volume_claim.data_proxmox` → `data_encrypted`, metadata.name to match cluster, storage class to `proxmox-lvm-encrypted`. - Updates the deployment volume `claim_name` reference accordingly. - Aligns with the newer project convention documented in `.claude/CLAUDE.md`: "Default for sensitive data is proxmox-lvm-encrypted" and "Convention: PVC names end in `-encrypted`". - No destroy/recreate: the PVC and deployment already use the encrypted PVC in the cluster; TF source now just describes reality. 2. **State imports** (out-of-band, via `scripts/tg import`, not in diff): - `kubernetes_namespace.grampsweb` <- `grampsweb` - `kubernetes_persistent_volume_claim.data_encrypted` <- `grampsweb/grampsweb-data-encrypted` - `kubernetes_service.grampsweb` <- `grampsweb/grampsweb` - `kubernetes_deployment.grampsweb` <- `grampsweb/grampsweb` - `module.ingress.kubernetes_ingress_v1.proxied-ingress` <- `grampsweb/family` - `module.tls_secret.kubernetes_secret.tls_secret` <- `grampsweb/tls-secret` - `kubernetes_manifest.external_secret` <- `apiVersion=external-secrets.io/v1beta1,kind=ExternalSecret,namespace=grampsweb,name=grampsweb-secrets` ## Apply result `Apply complete! Resources: 0 added, 7 changed, 0 destroyed.` In-place updates applied: - Deployment: dropped `GRAMPSWEB_LLM_BASE_URL` + `GRAMPSWEB_LLM_MODEL` env vars (both containers) — realising the intent of commit 7b248897. - Ingress: realigned Traefik middleware annotation + cleaned stale `uptime.viktorbarzin.me/external-monitor=false` annotation. - TLS secret: removed Kyverno-generated labels (Kyverno's `sync-tls-secret` ClusterPolicy re-applies them on next reconcile — no functional impact; same pattern in 29 other stacks using `setup_tls_secret` module). - Namespace, PVC, service: trivial metadata alignments (label / `wait_until_bound` / `wait_for_load_balancer`). - `kubernetes_manifest.external_secret`: populated the `manifest` attribute after import (expected). ## What is NOT in this change - No replica bump: deployment stays at `replicas=0` (stack is intentionally inactive per 2026-03-14 OOM incident note). - No destroy/recreate of any resource. - The broader code-w97 (11 stacks with empty state) is NOT closed — only grampsweb is imported. 10 stacks remain: beads-server, insta2spotify, isponsorblocktv, kyverno, meshcentral, pvc-autoresizer, shadowsocks, tor-proxy, travel_blog, + meshcentral PVC. ## Reproduce locally ``` KUBECONFIG=/home/wizard/code/config kubectl get all,ingress,pvc,externalsecret,secret -n grampsweb # Deployment still replicas=0; PVC grampsweb-data-encrypted Bound; ingress 'family' # on family.viktorbarzin.me; ExternalSecret SecretSynced True. cd /home/wizard/code/infra/stacks/grampsweb /home/wizard/code/infra/scripts/tg plan # Expected: 'No changes.' (clean state after apply). ``` ## Test Plan ### Automated ``` $ cd /home/wizard/code/infra/stacks/grampsweb && /home/wizard/code/infra/scripts/tg plan Plan: 0 to add, 7 to change, 0 to destroy. [pre-apply] $ /home/wizard/code/infra/scripts/tg apply --non-interactive Plan: 0 to add, 7 to change, 0 to destroy. kubernetes_namespace.grampsweb: Modifications complete after 0s [id=grampsweb] kubernetes_persistent_volume_claim.data_encrypted: Modifications complete after 0s [id=grampsweb/grampsweb-data-encrypted] kubernetes_service.grampsweb: Modifications complete after 0s [id=grampsweb/grampsweb] module.ingress.kubernetes_ingress_v1.proxied-ingress: Modifications complete after 0s [id=grampsweb/family] module.tls_secret.kubernetes_secret.tls_secret: Modifications complete after 0s [id=grampsweb/tls-secret] kubernetes_manifest.external_secret: Modifications complete after 0s kubernetes_deployment.grampsweb: Modifications complete after 1s [id=grampsweb/grampsweb] Apply complete! Resources: 0 added, 7 changed, 0 destroyed. $ terraform fmt -check -recursive stacks/grampsweb (no output - formatted clean) ``` ### Manual Verification ``` $ KUBECONFIG=/home/wizard/code/config kubectl get all,ingress,pvc,externalsecret,secret -n grampsweb # - deployment.apps/grampsweb 0/0 0 0 47d (replicas=0 preserved) # - service/grampsweb ClusterIP 10.106.232.205:80/TCP # - persistentvolumeclaim/grampsweb-data-encrypted Bound pvc-c9a5dcf4... 1Gi RWO proxmox-lvm-encrypted # - ingress/family traefik family.viktorbarzin.me -> 10.0.20.200:80,443 # - externalsecret/grampsweb-secrets vault-kv 15m SecretSynced True # - secret/tls-secret kubernetes.io/tls # No pod crashes (no pods — replicas=0). ``` Closes: code-8m6
2026-04-18 11:37:45 +00:00
claim_name = kubernetes_persistent_volume_claim.data_encrypted.metadata[0].name
}
}
}
}
}
[infra] Sweep dns_config ignore_changes across all pod-owning resources [ci skip] ## Context Wave 3A (commit c9d221d5) added the `# KYVERNO_LIFECYCLE_V1` marker to the 27 pre-existing `ignore_changes = [...dns_config]` sites so they could be grepped and audited. It did NOT address pod-owning resources that were simply missing the suppression entirely. Post-Wave-3A sampling (2026-04-18) found that navidrome, f1-stream, frigate, servarr, monitoring, crowdsec, and many other stacks showed perpetual `dns_config` drift every plan because their `kubernetes_deployment` / `kubernetes_stateful_set` / `kubernetes_cron_job_v1` resources had no `lifecycle {}` block at all. Root cause (same as Wave 3A): Kyverno's admission webhook stamps `dns_config { option { name = "ndots"; value = "2" } }` on every pod's `spec.template.spec.dns_config` to prevent NxDomain search-domain flooding (see `k8s-ndots-search-domain-nxdomain-flood` skill). Without `ignore_changes` on every Terraform-managed pod-owner, Terraform repeatedly tries to strip the injected field. ## This change Extends the Wave 3A convention by sweeping EVERY `kubernetes_deployment`, `kubernetes_stateful_set`, `kubernetes_daemon_set`, `kubernetes_cron_job_v1`, `kubernetes_job_v1` (+ their `_v1` variants) in the repo and ensuring each carries the right `ignore_changes` path: - **kubernetes_deployment / stateful_set / daemon_set / job_v1**: `spec[0].template[0].spec[0].dns_config` - **kubernetes_cron_job_v1**: `spec[0].job_template[0].spec[0].template[0].spec[0].dns_config` (extra `job_template[0]` nesting — the CronJob's PodTemplateSpec is one level deeper) Each injection / extension is tagged `# KYVERNO_LIFECYCLE_V1: Kyverno admission webhook mutates dns_config with ndots=2` inline so the suppression is discoverable via `rg 'KYVERNO_LIFECYCLE_V1' stacks/`. Two insertion paths are handled by a Python pass (`/tmp/add_dns_config_ignore.py`): 1. **No existing `lifecycle {}`**: inject a brand-new block just before the resource's closing `}`. 108 new blocks on 93 files. 2. **Existing `lifecycle {}` (usually for `DRIFT_WORKAROUND: CI owns image tag` from Wave 4, commit a62b43d1)**: extend its `ignore_changes` list with the dns_config path. Handles both inline (`= [x]`) and multiline (`= [\n x,\n]`) forms; ensures the last pre-existing list item carries a trailing comma so the extended list is valid HCL. 34 extensions. The script skips anything already mentioning `dns_config` inside an `ignore_changes`, so re-running is a no-op. ## Scale - 142 total lifecycle injections/extensions - 93 `.tf` files touched - 108 brand-new `lifecycle {}` blocks + 34 extensions of existing ones - Every Tier 0 and Tier 1 stack with a pod-owning resource is covered - Together with Wave 3A's 27 pre-existing markers → **169 greppable `KYVERNO_LIFECYCLE_V1` dns_config sites across the repo** ## What is NOT in this change - `stacks/trading-bot/main.tf` — entirely commented-out block (`/* … */`). Python script touched the file, reverted manually. - `_template/main.tf.example` skeleton — kept minimal on purpose; any future stack created from it should either inherit the Wave 3A one-line form or add its own on first `kubernetes_deployment`. - `terraform fmt` fixes to pre-existing alignment issues in meshcentral, nvidia/modules/nvidia, vault — unrelated to this commit. Left for a separate fmt-only pass. - Non-pod resources (`kubernetes_service`, `kubernetes_secret`, `kubernetes_manifest`, etc.) — they don't own pods so they don't get Kyverno dns_config mutation. ## Verification Random sample post-commit: ``` $ cd stacks/navidrome && ../../scripts/tg plan → No changes. $ cd stacks/f1-stream && ../../scripts/tg plan → No changes. $ cd stacks/frigate && ../../scripts/tg plan → No changes. $ rg -c 'KYVERNO_LIFECYCLE_V1' stacks/ --include='*.tf' --include='*.tf.example' \ | awk -F: '{s+=$2} END {print s}' 169 ``` ## Reproduce locally 1. `git pull` 2. `rg 'KYVERNO_LIFECYCLE_V1' stacks/ | wc -l` → 169+ 3. `cd stacks/navidrome && ../../scripts/tg plan` → expect 0 drift on the deployment's dns_config field. Refs: code-seq (Wave 3B dns_config class closed; kubernetes_manifest annotation class handled separately in 8d94688d for tls_secret) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-18 21:19:48 +00:00
lifecycle {
# KYVERNO_LIFECYCLE_V1: Kyverno admission webhook mutates dns_config with ndots=2
ignore_changes = [spec[0].template[0].spec[0].dns_config]
}
}
resource "kubernetes_service" "grampsweb" {
metadata {
name = "grampsweb"
namespace = kubernetes_namespace.grampsweb.metadata[0].name
labels = {
app = "grampsweb"
}
}
spec {
selector = {
app = "grampsweb"
}
port {
name = "http"
port = 80
target_port = 5000
}
}
}
module "ingress" {
source = "../../modules/kubernetes/ingress_factory"
namespace = kubernetes_namespace.grampsweb.metadata[0].name
name = "family"
service_name = "grampsweb"
tls_secret_name = var.tls_secret_name
max_body_size = "500m"
ingress_factory: replace `protected` bool with `auth` enum + audit pass across 100 stacks Phase 3+4 of default-deny ingress plan. Replaces the `protected = bool` (default false → unprotected) variable in `modules/kubernetes/ingress_factory` with `auth = string` enum (default "required" → fail-closed). Touches every ingress_factory caller so the audit decision is recorded explicitly in code. ingress_factory (Phase 3): - `auth = "required"`: standard Authentik forward-auth (the legacy `protected = true` semantic). - `auth = "public"`: forward-auth via the new `authentik-forward-auth-public` middleware → dedicated public outpost → guest auto-bind. Logged-in users keep their real identity. - `auth = "none"`: no Authentik middleware. For Anubis-fronted content, native client APIs (Git, /v2/, WebDAV), webhook receivers, the Authentik outpost itself. - `effective_anti_ai` default flips ON only when `auth = "none"` (auth-gated ingresses don't need anti-AI noise; the auth flow already discourages bots). Audit pass (Phase 4) across 96 ingress_factory call sites: - 49 explicit `protected = true` → `auth = "required"` - 8 explicit `protected = false` → `auth = "none"` (5) or `auth = "public"` (3) - 64 previously-default (no protected line) → `auth = "required"` ADDED, then reviewed individually: * 9 Anubis-fronted (blog, www, kms, travel, f1, cyberchef, jsoncrack, homepage, wrongmove UI, privatebin) → `auth = "none"` * 22 native-client / programmatic surfaces (Forgejo Git+/v2/, webhook handler, claude-memory MCP, Nextcloud WebDAV, Matrix, Vault CLI/OIDC, xray VPN, ntfy, woodpecker webhooks, n8n triggers, ntfy push, dawarich location ingestion, immich frame kiosk, headscale CP, send anonymous drops, rybbit beacon, vaultwarden API, Authentik UI itself + outposts) → `auth = "none"` * Remaining ~33 → `auth = "required"` confirmed (admin tools, internal UIs, services without app-level auth) - Smoke-test promotions to `auth = "public"`: fire-planner public UI, k8s-portal API, insta2spotify callback. Three call sites in wrapper modules (`stacks/freedify/factory/`, `stacks/reverse-proxy/modules/reverse_proxy/`) keep their internal `protected` bool — they translate to `auth` internally, out of scope for this rename. Behavior change: previously-default ingresses now fail closed (require Authentik login) unless explicitly flipped to `auth = "none"` or `auth = "public"`. This is the audit goal — no more accidentally-unprotected surfaces. Sites that were intentionally public (Anubis content, native APIs, webhooks) are now explicitly recorded as `auth = "none"`. Drive-by: `modules/create-vm/main.tf` picked up cosmetic alignment via `terraform fmt -recursive` during the audit. Behavior-neutral. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-10 18:53:49 +00:00
auth = "required"
external_monitor = false
extra_annotations = {
"gethomepage.dev/enabled" = "true"
"gethomepage.dev/name" = "GrampsWeb"
"gethomepage.dev/description" = "Family tree"
"gethomepage.dev/icon" = "gramps-web.png"
"gethomepage.dev/group" = "Other"
"gethomepage.dev/pod-selector" = ""
}
}