homelab-k3s/apps/searxng/secret.example.yaml
jasonwitty 8afac39d03 Import manifests reverse-engineered from live cluster
Captured 2026-07-26 from rpi-master (k3s v1.30.3) and cleaned of runtime
fields. Six apps as per-app kustomizations: vaultwarden, searxng,
home-assistant, nginx, pihole(+unbound), unified-streaming.

Intentional divergences from live state:
- pihole WEBPASSWORD and USP_LICENSE_KEY moved from inline plaintext env
  to secretKeyRef (secrets gitignored; templates in secret.example.yaml)
- HA ingress defaultBackend fixed (pointed at nonexistent service)
- unifiedstreaming-svc kept as ClusterIP (LoadBalancer could never bind
  port 80 behind svclb-traefik)

Validated against the live cluster with kubectl apply --dry-run=server:
no immutable-field conflicts; one-time kubectl replace procedure for the
two env->secretKeyRef migrations documented in README.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-26 02:13:56 -07:00

15 lines
395 B
YAML

# Copy to secret.yaml (gitignored), set a real secret_key, and apply once:
# kubectl apply -f secret.yaml
# The secret already exists in the cluster; this file only documents its shape.
apiVersion: v1
kind: Secret
metadata:
name: searxng-1723974683-config
namespace: default
type: Opaque
stringData:
settings.yml: |
server:
secret_key: CHANGE-ME
use_default_settings: true