A Helm chart for deploying 1Password Connect and the 1Password Connect Kubernetes Operator

Features

• Connect Helm chart supports operator.allowEmptyValues value to configure the Operator's --allow-empty-values flag. Empty secret field values are skipped by default. (#264)
• Connect Helm chart supports configurable securityContext and is Pod Security Standards (Restricted) compliant, so it can run in restricted namespaces without Pod Security Admission warnings. (#192, #210, #223)
• README values tables are now auto-generated from values.yaml for consistency. (#268)
• Connect Helm chart supports operator trust for self-signed or internal CA certificates via operator.tls.trust.secret. (#171, #200)

Fixes

• Connect Helm chart now uses operator.serviceAccountToken.key for the operator’s service account token instead of operator.token.key. (#266)
• Connect Helm chart supports a custom ServiceAccount for the Connect deployment, allowing a dedicated or pre-existing service account to be specified. (#249)
• Fix expired dev Slack link in README. {#265}
• Hide the credentials warning when connect.credentials_base64 is set, since credentials are already provided. (#84)
• Fix credential secret when set from values with correct encoding and mount credentials as a file with OP_SESSION pointing to the path. (#196)
• 1Password Operator image is updated to v1.11.0 to brings fixes for the operator.

New Contributors

• @grhawk made their first contribution in #196
• @rishiy15 made their first contribution in #265
• @at-platform24 made their first contribution in #248
• @3deep5me made their first contribution in #223
• @applejag made their first contribution in #210
• @colstrom made their first contribution in #184
• @jeremyj made their first contribution in #175
• @craigmiller160 made their first contribution in #200

Full Changelog: connect-2.2.1...connect-2.3.0