Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update helm release external-secrets to v0.14.3 #375

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

corylwtsn
Copy link
Owner

@corylwtsn corylwtsn commented Sep 25, 2024

This PR contains the following updates:

Package Update Change OpenSSF
external-secrets minor 0.10.3 -> 0.14.3 OpenSSF Scorecard

Release Notes

external-secrets/external-secrets (external-secrets)

v0.14.3

Compare Source

Image: ghcr.io/external-secrets/external-secrets:v0.14.3
Image: ghcr.io/external-secrets/external-secrets:v0.14.3-ubi
Image: ghcr.io/external-secrets/external-secrets:v0.14.3-ubi-boringssl

What's Changed

New Contributors

Full Changelog: external-secrets/external-secrets@v0.14.2...v0.14.3

v0.14.2

Compare Source

Image: ghcr.io/external-secrets/external-secrets:v0.14.2
Image: ghcr.io/external-secrets/external-secrets:v0.14.2-ubi
Image: ghcr.io/external-secrets/external-secrets:v0.14.2-ubi-boringssl

What's Changed

New Contributors

Full Changelog: external-secrets/external-secrets@v0.14.1...v0.14.2

v0.14.1

Compare Source

Image: ghcr.io/external-secrets/external-secrets:v0.14.1
Image: ghcr.io/external-secrets/external-secrets:v0.14.1-ubi
Image: ghcr.io/external-secrets/external-secrets:v0.14.1-ubi-boringssl

What's Changed

New Contributors

Full Changelog: external-secrets/external-secrets@v0.14.0...v0.14.1

v0.14.0

Compare Source

Potential Breaking Change

Stateful Generators have been introduced with:

While normally this isn't a problem, external secrets controller and push secrets controller have been changed.

If any normal operation that should work encounters a problem, please don't hesitate to open an issue. Please also include that the problem appeared after switching to this version. Thank you!

Image: ghcr.io/external-secrets/external-secrets:v0.14.0
Image: ghcr.io/external-secrets/external-secrets:v0.14.0-ubi
Image: ghcr.io/external-secrets/external-secrets:v0.14.0-ubi-boringssl

What's Changed

New Contributors

Full Changelog: external-secrets/external-secrets@v0.13.0...v0.14.0

v0.13.0

Compare Source

Image: ghcr.io/external-secrets/external-secrets:v0.13.0
Image: ghcr.io/external-secrets/external-secrets:v0.13.0-ubi
Image: ghcr.io/external-secrets/external-secrets:v0.13.0-ubi-boringssl

BREAKING CHANGES

https://github.com/external-secrets/external-secrets/pull/4262 introduces a breaking change in the METADATA structure for the AWS PARAMETER STORE.

What's Changed

New Contributors

Full Changelog: external-secrets/external-secrets@v0.12.1...v0.13.0

v0.12.1

Compare Source

RELEASE VERSION

My apologies, when creating the release, 0.12.0 failed. The branch and tag however, have been created and I was unable to delete them. Thus, the version has been increased to 0.12.1 after the fix and now that's the current version. I hand updated the release notes to include everyone into the changes.

BREAKING CHANGES

The following breaking changes have been introduced into this release:

  • Permission update for AWS provider adding BulkFetch when getting multiple secrets ( significant API reduce but comes with adding a permission for bulk endpoint )
  • fixed a typo for a generator in the json tag where before it was ecrRAuthorizationTokenSpec with an extra R
  • We standardized the GCP Secrets Manager Metadata structure for PushSecrets ( be aware that existing manifests will stop working until updated to the standardized version ) for more info see https://github.com/external-secrets/external-secrets/pull/4210

Images

Image: ghcr.io/external-secrets/external-secrets:v0.12.1
Image: ghcr.io/external-secrets/external-secrets:v0.12.1-ubi
Image: ghcr.io/external-secrets/external-secrets:v0.12.1-ubi-boringssl

What's Changed

Full Changelog: external-secrets/external-secrets@v0.11.0...v0.12.1

v0.11.0

Compare Source

Deprecation of OLM Releases

As of 0.11.0 is the last release available for OLM until further notice. Depending on the way this goes, we might still have OLM support (ideally with a properly built operator for that), but for sure in a different support scheme as to not overload maintainers anymore.
Also a valid note - you can still use 0.11.0 OLM release and the newest ESO images, you just need to set image.tag appropriately in your setup.

Kubernetes API load and significant decrease

A new way of reconciling external secrets has been added with pull request #​4086.

This significantly reduces the number of API calls that we make to the kubernetes API server.

  1. Memory usage might increase if you are not already usin

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 is behind base branch, 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 has been generated by Renovate Bot.

@corylwtsn corylwtsn force-pushed the renovate/external-secrets-0.x branch 30 times, most recently from f84fe7c to 5bb602d Compare October 1, 2024 05:00
@corylwtsn corylwtsn force-pushed the renovate/external-secrets-0.x branch 10 times, most recently from 19e0b19 to 532edf3 Compare February 26, 2025 14:01
@corylwtsn corylwtsn changed the title chore(deps): update helm release external-secrets to v0.14.2 chore(deps): update helm release external-secrets to v0.14.3 Feb 26, 2025
@corylwtsn corylwtsn force-pushed the renovate/external-secrets-0.x branch 17 times, most recently from 5deb56a to 4518252 Compare March 3, 2025 14:02
@corylwtsn corylwtsn force-pushed the renovate/external-secrets-0.x branch from 4518252 to b52eebb Compare March 3, 2025 15:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants