Deploy the full ESO stack on ringtail, matching the indri pattern: - 4 ArgoCD apps (1password-connect, external-secrets-crds, external-secrets, external-secrets-config) targeting ringtail k3s cluster - ExternalSecret for forgejo-runner-amd64 token (replaces Ansible-managed secret) - Ansible playbook bootstraps 1Password Connect credentials instead of directly managing runner tokens Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
24 lines
730 B
YAML
24 lines
730 B
YAML
# External Secrets Configuration for ringtail k3s cluster
|
|
# Same ClusterSecretStore manifests as indri, different destination
|
|
#
|
|
# Prerequisites:
|
|
# - 1password-connect-ringtail is deployed and healthy
|
|
# - external-secrets-ringtail operator is deployed and CRDs are installed
|
|
#
|
|
apiVersion: argoproj.io/v1alpha1
|
|
kind: Application
|
|
metadata:
|
|
name: external-secrets-config-ringtail
|
|
namespace: argocd
|
|
spec:
|
|
project: default
|
|
source:
|
|
repoURL: ssh://forgejo@forge.ops.eblu.me:2222/eblume/blumeops.git
|
|
targetRevision: main
|
|
path: argocd/manifests/external-secrets
|
|
destination:
|
|
server: https://ringtail.tail8d86e.ts.net:6443
|
|
namespace: external-secrets
|
|
syncPolicy:
|
|
syncOptions:
|
|
- CreateNamespace=true
|