eblume/blumeops
1
1
Fork 0
Code Issues Pull requests Projects Releases 83 Packages Wiki Activity Actions
blumeops/docs/reference/services/1password.md
Erich Blume d02bf062af C0: review 1password reference card 
Added vault split (blumeops vs Personal), noted onepassword-connect
runs on both indri and ringtail, and lifted op CLI guidance from
agent memory into the card. Bumped last-reviewed.
2026-05-22 21:29:11 -07:00

2 KiB
Raw Blame History

title modified last-reviewed tags
1Password 2026-05-22 2026-05-22
service
secrets

1Password

Root credential store for all BlumeOps secrets. Kubernetes workloads read items via external-secrets; humans and agents read via the op CLI.

Vaults

Vault Purpose
blumeops Infrastructure secrets — referenced by ExternalSecret manifests and scripts.
Personal Human login credentials keyed by URL for autofill. Not consumed by infrastructure.

Kubernetes Integration

1Password Cloud
      |
      v
1Password Connect (namespace: 1password, deployed on both indri and ringtail)
      |
      v
External Secrets Operator (namespace: external-secrets)
      |
      v
Native Kubernetes Secrets

ClusterSecretStore: onepassword-blumeops (same name on both clusters).

Services reference 1Password items via ExternalSecret manifests. Both minikube-indri and k3s-ringtail run their own onepassword-connect deployment talking to the same vault.

Direct Access

Prefer op read "op://vault/item/field" over op item get --fields in scripts and IaC — op item get --fields wraps multi-line values in quotes, corrupting them. op item get without flags is fine for exploring item metadata.

If an item name contains special characters (e.g. parentheses), use the item ID instead of the name in the op:// path.

Disaster Recovery Backup

The mise run op-backup task encrypts a .1pux vault export and transfers it to indri for inclusion in borgmatic backups. See run-1password-backup for the step-by-step procedure and restore-1password-backup for disaster recovery.

Related