Adds 8 Tier 7 (Security/Policy) HelmReleases per
docs/BOOTSTRAP-KIT-EXPANSION-PLAN.md §2.5 — three cluster copies
(_template, omantel.omani.works, otech.omani.works).
Slots:
27 bp-kyverno dependsOn: bp-cilium (admission policy engine)
28 bp-reloader dependsOn: (none) (configmap/secret-rotation glue)
29 bp-vpa dependsOn: (none) (vertical autoscaler)
30 bp-trivy dependsOn: bp-cert-manager (static scanner / operator)
31 bp-falco dependsOn: bp-cilium (runtime threat detection / eBPF)
32 bp-sigstore dependsOn: bp-cert-manager (cosign admission verifier)
33 bp-syft-grype dependsOn: bp-cert-manager (SBOM + vulnerability matcher)
34 bp-velero dependsOn: bp-seaweedfs (backup; SeaweedFS-backed)
Conventions followed:
- HR shape mirrors the post-PR-250 event-driven pattern:
install.disableWait + upgrade.disableWait, no blanket spec.timeout.
- SOVEREIGN_FQDN substitution: `_template` carries the literal
`${SOVEREIGN_FQDN}` placeholder; cluster copies have it expanded
to the per-Sovereign FQDN at provisioning time (matches slot 11/12
convention introduced by PR #168).
- bp-reloader and bp-vpa intentionally have no dependsOn — they are
fully independent infrastructure helpers per the plan's §2.5.
- kustomization.yaml entries appended in numeric order (slots 15–26
intentionally empty — reserved for W2.K1 storage+DB and W2.K2
observability; W2.K3 ships independently).
Validation:
- `kubectl kustomize clusters/_template/bootstrap-kit/` OK
- `kubectl kustomize clusters/omantel.omani.works/bootstrap-kit/` OK
- `kubectl kustomize clusters/otech.omani.works/bootstrap-kit/` OK
(each: 22 HelmReleases, 22 HelmRepositories, 19 Namespaces)
- All 24 new HR YAML files parse as 3 docs (Namespace + HelmRepository
+ HelmRelease).
Charts and OCI artifacts: charts already present at platform/<name>/
(kyverno, reloader, trivy, falco, sigstore, syft-grype, velero — all
v1.0.0 umbrella charts). Note: platform/vpa/ currently has README.md
only — chart authoring is tracked separately and does not block this
HR-shape PR (Flux will retry until the OCI artifact lands).
Refs docs/BOOTSTRAP-KIT-EXPANSION-PLAN.md §2.5, §3.1 (W2.K3 row),
§4.2 (kustomization merge protocol).
Co-authored-by: hatiyildiz <269457768+hatiyildiz@users.noreply.github.com>
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
73 lines
2.2 KiB
YAML
73 lines
2.2 KiB
YAML
# bp-velero — Catalyst bootstrap-kit Blueprint #34 (W2.K3, Tier 7 — Security/Policy).
|
|
# Per-host-cluster backup engine. Catalyst-Zero pins backups to SeaweedFS
|
|
# (the unified S3 layer, slot 18) so backup data never leaves the
|
|
# Sovereign at install time; per-Sovereign archival to a cloud backend
|
|
# is wired in post-bootstrap via Crossplane.
|
|
#
|
|
# Wrapper chart: platform/velero/chart/ (umbrella over upstream
|
|
# vmware-tanzu/velero chart, Catalyst-curated values under the `velero:`
|
|
# key — `seaweedfs` BackupStorageLocation provider, no cloud plugin
|
|
# pinned at install time).
|
|
# Reconciled by: Flux on the new Sovereign's k3s control plane.
|
|
#
|
|
# dependsOn:
|
|
# - bp-seaweedfs — Velero's BackupStorageLocation points at the
|
|
# in-cluster SeaweedFS S3 endpoint (`seaweedfs.seaweedfs.svc:8333`)
|
|
# and reads the `seaweedfs-s3-credentials` Secret SeaweedFS renders
|
|
# during install. Without bp-seaweedfs Ready, the BSL Phase sits
|
|
# `Unavailable` and Velero's first reconcile fails — every backup
|
|
# CR queues with the same error until the dep lands.
|
|
|
|
---
|
|
apiVersion: v1
|
|
kind: Namespace
|
|
metadata:
|
|
name: velero
|
|
labels:
|
|
catalyst.openova.io/sovereign: omantel.omani.works
|
|
---
|
|
apiVersion: source.toolkit.fluxcd.io/v1beta2
|
|
kind: HelmRepository
|
|
metadata:
|
|
name: bp-velero
|
|
namespace: flux-system
|
|
spec:
|
|
type: oci
|
|
interval: 15m
|
|
url: oci://ghcr.io/openova-io
|
|
secretRef:
|
|
name: ghcr-pull
|
|
---
|
|
apiVersion: helm.toolkit.fluxcd.io/v2
|
|
kind: HelmRelease
|
|
metadata:
|
|
name: bp-velero
|
|
namespace: flux-system
|
|
spec:
|
|
interval: 15m
|
|
releaseName: velero
|
|
targetNamespace: velero
|
|
dependsOn:
|
|
- name: bp-seaweedfs
|
|
chart:
|
|
spec:
|
|
chart: bp-velero
|
|
version: 1.0.0
|
|
sourceRef:
|
|
kind: HelmRepository
|
|
name: bp-velero
|
|
namespace: flux-system
|
|
# Event-driven install: Velero's Deployment Ready depends on the
|
|
# node-agent DaemonSet rolling out and the BackupStorageLocation
|
|
# reaching `Available` — both runtime-convergence events that Flux
|
|
# observes via the BSL CR phase, not via Helm `--wait`. disableWait
|
|
# keeps the HR's Ready signal aligned with manifest apply.
|
|
install:
|
|
disableWait: true
|
|
remediation:
|
|
retries: 3
|
|
upgrade:
|
|
disableWait: true
|
|
remediation:
|
|
retries: 3
|