This Helm chart deploys 1Password Connect and optionally the Kubernetes operator plugin for 1Password Connect. There is no option to deploy the operator using this Helm chart without also deploying 1Password Connect.
Use cases
Deploying the operator without deploying 1Password Connect is useful when deploying multiple operators connected to a single 1Password Connect server. This is not currently possible using Helm.
Proposed solution
Add a new chart value and some corresponding logic to disable the 1Password Connect deployment, defaulting to the current behaviour to deploy 1Password Connect only.
Is there a workaround to accomplish this today?
It is currently possible to deploy the operator on its own (see https://github.com/1Password/onepassword-operator), but not by using Helm. The only semi-plausible workaround I can think of is to deploy Connect with 0 replicas.
Summary
This Helm chart deploys 1Password Connect and optionally the Kubernetes operator plugin for 1Password Connect. There is no option to deploy the operator using this Helm chart without also deploying 1Password Connect.
Use cases
Deploying the operator without deploying 1Password Connect is useful when deploying multiple operators connected to a single 1Password Connect server. This is not currently possible using Helm.
Proposed solution
Add a new chart value and some corresponding logic to disable the 1Password Connect deployment, defaulting to the current behaviour to deploy 1Password Connect only.
Is there a workaround to accomplish this today?
It is currently possible to deploy the operator on its own (see https://github.com/1Password/onepassword-operator), but not by using Helm. The only semi-plausible workaround I can think of is to deploy Connect with 0 replicas.
References & Prior Work
How we optionally deploy the operator: