New! Use the 1Password Credential Broker to give CI/CD and other machine workflows short-lived access to secrets, without managing service account tokens.
The 1Password Connect and Operator Helm chart allows you to use Helm to deploy Connect, the Kubernetes Operator, or both.You can override configuration values in a chart with the helm install command using either the --values flag or the --set flag. You can also force a string value with the --set-string flag.For example, the following code block shows how to use the --set flag to set the connect.applicationName configuration value:
By default, installing a 1Password Helm chart also installs the OnePasswordItem database operations for CRD (Custom Resource Definition).If you don’t want to install the OnePasswordItem custom resource definitions (CRD), run helm install with the --skip-crds flag .
Denotes whether to deploy the 1Password Connect server. Set this value to false and operator.create to true to only deploy the Kubernetes Operator. See Deploy without Connect.
connect.replicas
integer
1
The number of replicas to run the 1Password Connect deployment.
connect.applicationName
string
"onepassword-connect"
The name of 1Password Connect application.
connect.host
string
"onepassword-connect"
The name of 1Password Connect host.
connect.api.imageRepository
string
"1password/connect-api
The 1Password Connect API repository.
connect.api.name
string
"connect-api"
The name of the 1Password Connect API container.
connect.api.resources
object
{}
The resources requests/limits for the 1Password Connect API pod.
connect.api.httpPort
integer
8080
The port the Connect API is served on when not using TLS.
connect.api.httpsPort
integer
8443
The port the Connect API is served on when using TLS.
connect.api.logLevel
string
info
The log level of the Connect API container. Valid options are trace, debug, info, warn, and error.
connect.credentials
jsonString
The contents of the 1password-credentials.json file for Connect. You can set it by adding --set-file connect.credentials=<path/to/1password-credentials.json> to your helm install command.
connect.credentials_base64
string
The base64-encoded contents of the 1password-credentials.json file for Connect. You can use this instead of connect.credentials if supplying raw JSON to connect.credentials lead to issues.
connect.credentialsKey
string
"1password-credentials.json"
The key for the 1Password Connect credentials (stored in the credentials secret). The credentials must be encoded as a base64 string.
connect.credentialsName
string
"op-credentials"
The name of Kubernetes Secret containing the 1Password Connect credentials.
connect.dataVolume.name
string
"shared-data"
The name of the shared volume used between 1Password Connect containers.
connect.dataVolume.type
string
"emptyDir"
The type of shared volume used between 1Password Connect containers.
connect.dataVolume.values
object
{}
Describes the fields and values for the configuration of the shared volume for 1Password Connect.
The 1Password Secrets Injector Helm chart allows you to use Helm to deploy the Kubernetes Secrets Injector.You can override configuration values in a chart with the helm install command using either the --values flag or the --set flag. You can also force a string value with the --set-string flag.For example, the following code block shows how to use the --set flag to set the injector.applicationName configuration value:
