3 ms·

In this realm, I’ve been happily using 1Password’s Operator for Kubernetes secrets. Feel free to ignore the Nix stuff, but I’ve outlined how I create entries w

In this realm, I’ve been happily using 1Password’s Operator for Kubernetes secrets. Feel free to ignore the Nix stuff, but I’ve outlined how I create entries with the 1Password CLI: https://github.com/heywoodlh/flakes/tree/main/kube#1password-usage-with-kubernetes-operator https://github.com/heywoodlh/flakes/tree/main/kube#1password... After a OnePasswordItem is created, a secret containing your fields and their values appears. It’s marvelous! (Integrations like this are why I switched away from Bitwarden to 1Password)

steveTheFiend 3y ago
I went this route too for organisations in onepassword. It wasn't right, there was no way to create a password / secret only the recipient could see. The org admin can always take access through their admin rights. You can't deliver to a personal vault. If it's changed I'll look again but support couldn't understand why it wasn't acceptable. Especially when your looking at the unseal keys for vault.