Update Helm release connect to v2 #250
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.17.1
->2.0.5
Release Notes
1Password/connect-helm-charts (connect)
v2.0.5
Compare Source
A Helm chart for deploying 1Password Connect and the 1Password Connect Kubernetes Operator
v2.0.4
Compare Source
A Helm chart for deploying 1Password Connect and the 1Password Connect Kubernetes Operator
What's Changed
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
New Contributors
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
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
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
Previously, the Connect service was exposed externally by default using
NodePort
. In this release, the default service type has been changed toClusterIP
, 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
toNodePort
orLoadBalancer
in your Helm values.Features
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.
This PR was generated by Mend Renovate. View the repository job log.