Chart 2.3.0 mounts credentials as a file with standard k8s base64 encoding. The old double-encoding workaround (credentials-base64 in stringData) now produces invalid JSON. Use raw JSON (credentials-file) instead. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| README.md | ||
| secret-credentials.yaml.tpl | ||
| values.yaml | ||
1Password Connect
1Password Connect provides REST API access to 1Password vault items for External Secrets Operator.
Architecture
1Password Cloud
|
v
1Password Connect (this service)
|
v
External Secrets Operator
|
v
Native Kubernetes Secrets
Prerequisites (One-Time Setup)
Run these steps on the workstation (gilbert) before deploying:
1. Create Connect Server Credentials
# This creates the credentials file and outputs a server ID
op connect server create blumeops --vaults blumeops
# Save the 1password-credentials.json file contents
2. Create Access Token
# Replace <server-id> with the ID from step 1
op connect token create blumeops --server <server-id> --vault blumeops
# Save the token
3. Store Credentials in 1Password
Create a new item "1Password Connect" in the blumeops vault with:
credentials-filefield: Paste the contents of1password-credentials.json(raw JSON, NOT base64 encoded)tokenfield: Paste the access token
Note: Chart 2.3.0+ mounts credentials as a file with standard k8s base64 encoding. The old
credentials-base64field is no longer needed.
4. Create 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 -
Deployment
argocd app sync apps
argocd app sync 1password-connect
Verification
# Check pods are running
kubectl --context=minikube-indri -n 1password get pods
# Check logs
kubectl --context=minikube-indri -n 1password logs -l app=onepassword-connect
# Test API health (port-forward first)
kubectl --context=minikube-indri -n 1password port-forward svc/onepassword-connect 8080:8080 &
curl http://localhost:8080/health
Troubleshooting
Pods not starting
- Check the bootstrap secret exists:
kubectl --context=minikube-indri -n 1password get secret op-credentials - Verify credentials format in 1Password item
API returning 401
- Check the token secret:
kubectl --context=minikube-indri -n 1password get secret onepassword-token - Verify the token has access to the blumeops vault