connect-2.2.1

Fixes

• 1Password Operator image is updated to v1.10.1 to brings fixes for the operator.

Full Changelog: connect-2.2.0...connect-2.2.1

connect-2.2.0

Features

• Support --enable-annotations in operator deployment by @smallc2009 in #261

New Contributors

• @smallc2009 made their first contribution in #261

Full Changelog: connect-2.1.1...connect-2.2.0

connect-2.1.1

Fixes

• Fix release workflow to publish charts to GHCR. (#258)

Full Changelog: connect-2.1.0...connect-2.1.1

connect-2.1.0

Features

• Helm charts are now available to install via OCI registry. (#221)

Fixes

• Custom env vars can be set to Connect's sync container now. (#197)
• Numeric values can be passed as custom env variables in Connect chart. (#255)

Full Changelog: connect-2.0.5...connect-2.1.0

connect-2.0.5

Features

• Bump Connect version to v1.8.1

Full Changelog: connect-2.0.4...connect-2.0.5

connect-2.0.4

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

What's Changed

• Prepare release v2.0.4 by @volodymyrZotov in #245

Full Changelog: connect-2.0.3...connect-2.0.4

connect-2.0.3

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

What's Changed

• connect: allow specifying test image and disabling tests by @paulfantom in #241
• Prepare release v2.0.3 for connect chart by @paulfantom in #242

New Contributors

• @paulfantom made their first contribution in #241 🎉

Full Changelog: connect-2.0.2...connect-2.0.3

connect-2.0.2

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

Fixes

• Updated Operator version to include fix for panic when handling 1Password items with files (onepassword-operator#209).

Full Changelog: connect-2.0.1...connect-2.0.2

connect-2.0.1

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

What's Changed

• Make it possible to upgrade connect chart to v2.0.x without providing token value by @volodymyrZotov in #232
• Prepare release v2.0.1 by @volodymyrZotov in #234

Full Changelog: connect-2.0.0...connect-2.0.1

connect-2.0.0

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

⚠️ Breaking changes

• Default Connect service type changed to ClusterIP. (#194)

Previously, the Connect service was exposed externally by default using NodePort. In this release, the default service type has been changed to ClusterIP, meaning Connect is now only accessible from within the cluster unless explicitly configured otherwise.
While exposing Connect via NodePort is not inherently insecure—since Connect requires a valid bearer token for all API access—this change aligns with the principle of least privilege and reduces unnecessary external surface area by default.
If you require external access to Connect, you can still set connect.serviceType to NodePort or LoadBalancer in your Helm values.

Features

• Add support for configuring the operator to use a 1Password Service Account. {#226}