Update Helm release connect to v2 by renovate[bot] · Pull Request #38 · wyattwalter/y8s

renovate · 2026-02-01T14:05:00Z

This PR contains the following updates:

Package	Update	Change
connect (source)	major	`1.7.1` → `2.3.0`

Release Notes

1Password/connect-helm-charts (connect)

`v2.3.0`

Compare Source

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

⚠️ Credentials (2.3.0):

If you were using the double base64–encoding workaround for the credentials secret (1password-credentials.json), that no longer works as this issue has been resolved. Credentials are now mounted as a file and work with the standard single base64 encoding that Kubernetes applies to Secret data. If you were double encoding the credentials you will need to update the secret.

Change for reference:

Fix credential secret when set from values with correct encoding and mount credentials as a file with OP_SESSION pointing to the path. (#196)

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: 1Password/connect-helm-charts@connect-2.2.1...connect-2.3.0

`v2.2.1`

Compare Source

Fixes

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

Full Changelog: 1Password/connect-helm-charts@connect-2.2.0...connect-2.2.1

`v2.2.0`

Compare Source

Features

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

New Contributors

@smallc2009 made their first contribution in #261

Full Changelog: 1Password/connect-helm-charts@connect-2.1.1...connect-2.2.0

`v2.1.1`

Compare Source

Fixes

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

Full Changelog: 1Password/connect-helm-charts@connect-2.1.0...connect-2.1.1

`v2.1.0`

Compare Source

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: 1Password/connect-helm-charts@connect-2.0.5...connect-2.1.0

`v2.0.5`

Compare Source

Features

Bump Connect version to v1.8.1

Full Changelog: 1Password/connect-helm-charts@connect-2.0.4...connect-2.0.5

`v2.0.4`

Compare Source

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: 1Password/connect-helm-charts@connect-2.0.3...connect-2.0.4

`v2.0.3`

Compare Source

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: 1Password/connect-helm-charts@connect-2.0.2...connect-2.0.3

`v2.0.2`

Compare Source

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: 1Password/connect-helm-charts@connect-2.0.1...connect-2.0.2

`v2.0.1`

Compare Source

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: 1Password/connect-helm-charts@connect-2.0.0...connect-2.0.1

`v2.0.0`

Compare Source

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}

`v1.17.1`

Compare Source

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

`v1.17.0`

Compare Source

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

`v1.16.0`

Compare Source

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

`v1.15.1`

Compare Source

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

`v1.15.0`

Compare Source

Features

Proxy Support or custom env #152
Bump operator version to 1.8.1

`v1.14.0`

Compare Source

Features

The default Operator version is updated to v1.8.0. Credits to @mmorejon for the contribution. {#168}
The default Connect version is updated to v1.7.2.

`v1.13.0`

Compare Source

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

`v1.12.1`

Compare Source

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

`v1.12.0`

Compare Source

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

`v1.11.0`

Compare Source

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

`v1.10.0`

Compare Source

Features

Add replicas definition to the Connect Deployment {#121, #128}
Use the latest 1password/operator version 1.6.0 {#128}

Fixes

Use '1Password Operator' term instead of '1Password Connect Operator' in the documentation {#128}

`v1.9.0`

Compare Source

Features

Enable a better interaction with 1Password Connect and Sync applications deployed. Credits to @klaus385 for contributing to this enhancement. {#107}

Fixes

Updated Connect to v1.5.7, which addresses some bugs and security enahncements.

`v1.8.1`

Compare Source

Fixes

Updated Connect to v1.5.6, which addresses some bugs.

`v1.8.0`

Compare Source

Features

Updated Kubernetes Operator to v1.5.0, which adds the type and status for the OnePasswordItem CRD. {#101}
Updated OnePasswordItem CRD to enable the new functionality added in the latest version of the Kubernetes Operator. Credits to @tomjohnburton for contributing to this enhancement. {#92, #102}

Fixes

Updated Connect to v1.5.4, which resolves some bugs. {#101}

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Update Helm release connect to v2

d18332b

renovate Bot force-pushed the renovate/connect-2.x branch from eb0962f to d18332b Compare February 10, 2026 01:35

Navigation Menu

Update Helm release connect to v2 - #38

Update Helm release connect to v2#38
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/connect-2.x

renovate Bot commented Feb 1, 2026 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Conversation

renovate Bot commented Feb 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

⚠️ Credentials (2.3.0):

Features

Fixes

New Contributors

Fixes

Features

New Contributors

Fixes

Features

Fixes

Features

What's Changed

What's Changed

New Contributors

Fixes

What's Changed

⚠️ Breaking changes

Features

Features

Features

Features

Fixes

Features

Fixes

Fixes

Features

Fixes

Configuration

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

renovate Bot commented Feb 1, 2026 •

edited

Loading