blumeops/argocd/apps/1password-connect.yaml
Erich Blume aae7726ecc Migrate 1Password Connect from Helm to kustomize (1.8.1 → 1.8.2)
Renders manifests from connect-helm-charts v2.4.1 as plain kustomize,
completing the no-helm-policy migration. All services now use kustomize.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-06 07:15:41 -07:00

31 lines
1.1 KiB
YAML

# 1Password Connect - Secrets Automation Server
# Provides REST API access to 1Password vault items for External Secrets Operator
#
# Manifests rendered from connect-helm-charts v2.4.1, maintained as plain kustomize.
#
# Prerequisites (one-time setup):
# 1. Create Connect server: op connect server create blumeops --vaults blumeops
# 2. Create token: op connect token create blumeops --server <server-id> --vault blumeops
# 3. Store credentials in 1Password item "1Password Connect" in blumeops vault
# 4. Bootstrap secret:
# kubectl --context=minikube-indri create namespace 1password
# op inject -i argocd/manifests/1password-connect/secret-credentials.yaml.tpl | \
# kubectl --context=minikube-indri apply -f -
#
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name: 1password-connect
namespace: argocd
spec:
project: default
source:
repoURL: ssh://forgejo@forge.ops.eblu.me:2222/eblume/blumeops.git
targetRevision: main
path: argocd/manifests/1password-connect
destination:
server: https://kubernetes.default.svc
namespace: 1password
syncPolicy:
syncOptions:
- CreateNamespace=true