Spike: Investigate use of 1Password Kubernetes Operator to replace External Secrets Operator

[jadecarino]

Background

We currently use IBM Cloud Secrets Manager to store secrets and through the External Secrets operator those secrets can be provided to automation in our Kubernetes cluster. IBM Cloud Secrets Manager is unfortunately very expensive so we are investigating if we can replace it with a much cheaper secrets service. 1Password Teams is an option that I'll be investigating for this spike story.

We have been asked to complete this migration by the end of February. We have removed our dependency on IBM Cloud Secrets Manager in story #2548 so this following story will encompass setting up the 1Password Kubernetes Operator to sync secrets from 1Password into our Kubernetes Deployments.

Tasks

• Get access to the OMP 1Password account
• Set up Secrets Automation workflow
• Obtain 1password-credentials.json file and access token
• Deploy the Connect Server with the Kubernetes Operator
• Reference secrets in Deployments with 1Password secrets