Zum Inhalt springen
Produkte

// Deployment-Referenz

Optional add-ons (manifests)

Everything here is opt-in. The base is a working hub on its own; add these as your setup needs them. Each file is independent — apply only the ones you want.

Add-on File(s) When you need it
Ingress + TLS ingress.yaml Exposing the UI/agents beyond a trusted LAN. Do this before exposing Fleeger — login and agent traffic must be HTTPS. The edge answers it with a 503 until set_real_ip_from names the controller (Fleeger on Kubernetes — plain manifests).
NodePort access edge-nodeport.yaml Quick LAN/homelab access with no ingress controller (plaintext HTTP — trusted networks only). Replaces the base edge Service.
Cluster monitoring Monitoring the hub's own cluster (bundled core-agent) Letting the hub watch its own cluster via a ServiceAccount + read-only RBAC (the bundled core-agent).
Network segmentation network-policies.yaml Defense-in-depth: default-deny ingress + per-service allow rules. CNI-specific and untested — validate first.
Scheduled backups backup-cronjob.yaml Nightly SurrealDB dumps to S3 + the backup-success metric the dead-man's-switch alert watches.
S3 set restore restore-s3-pod.yaml Restoring a set the backup CronJob wrote to S3 with scripts/restore.sh: a pod of the backup image with the S3 credentials and the backup signing key's public keys, and no signing key, plus a claim for the download and the pre-restore set. Never restore from the CronJob's own pod, which holds the private key. Steps at the top of the file; for a Helm install, its header lists what to change.
Platform restore restore-pod.yaml Restoring a .fbk backup: a pod (and a claim for the archive and the pre-restore backup) to run inventory-svc backup restore in, with the services scaled to zero. Steps at the top of the file. Fits a hub from deploy/k8s once its image is set to the inventory-svc image the hub runs; for a Helm install, its header lists what to change.

Apply an add-on with, e.g.:

kubectl -n fleeger apply -f deploy/k8s/optional/ingress.yaml

Most files have REPLACE-ME placeholders or an inline "EDIT BEFORE APPLYING" note — read the top of each file first.

For exposing Fleeger to remote agents (agents running at other locations), see the "Reaching agents" section of Deploying Fleeger on Kubernetes. For running an agent yourself, see Running a spoke-agent with plain manifests.

// Zusammenarbeit

Bereit, Ihre digitale Infrastruktur zu bauen?

Ob individuelle Automatisierung für Ihr Unternehmen oder ein durchgeplantes Netzwerk für Ihr Zuhause — lassen Sie uns über das Projekt sprechen.