claude-botandClaude Opus 5.5
790e258894
Namespace, CRD (Flux prune disabled so a prune never cascades into deleting every Kuma monitor via finalizers), cluster RBAC matching the controller-gen role, Recreate Deployment of the first master build (2026-10-19-0545) under image automation, and a default-deny CiliumNetworkPolicy allowing only DNS, the kube-apiserver and kuma.renner.uno:443 out, kubelet probes in. The Kuma login comes from its own OpenBao path infrastructure/kuma-sync (a copy of the single Kuma admin account) rather than reading infrastructure/uptime-kuma. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
24 lines
545 B
YAML
24 lines
545 B
YAML
---
|
|
# Uptime Kuma login for kuma-sync; OpenBao homelab/infrastructure/kuma-sync.
|
|
apiVersion: external-secrets.io/v1
|
|
kind: ExternalSecret
|
|
metadata:
|
|
name: kuma-sync-kuma
|
|
namespace: kuma-sync
|
|
spec:
|
|
refreshInterval: 1h
|
|
secretStoreRef:
|
|
kind: ClusterSecretStore
|
|
name: openbao
|
|
target:
|
|
name: kuma-sync-kuma
|
|
data:
|
|
- secretKey: username
|
|
remoteRef:
|
|
key: infrastructure/kuma-sync
|
|
property: username
|
|
- secretKey: password
|
|
remoteRef:
|
|
key: infrastructure/kuma-sync
|
|
property: password
|