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.

Sign up for GitHub

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

Jump to bottom

chore(deps): update dependency https://github.com/external-secrets/external-secrets to v0.12.1 #580

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

chore(deps): update dependency https://github.com/external-secrets/external-secrets to v0.12.1 #580

wants to merge 1 commit into from

Conversation

public-glueops-renovatebot[bot]
Copy link
Contributor

@public-glueops-renovatebot public-glueops-renovatebot bot commented Dec 23, 2024 •
edited
Loading

This PR contains the following updates:

Package Update Change
https://github.com/external-secrets/external-secrets minor v0.9.20 -> v0.12.1

Release Notes

external-secrets/external-secrets (https://github.com/external-secrets/external-secrets)

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.12.0

Compare Source

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

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 using --enable-secrets-caching
    1. If you are using --enable-secrets-caching and want to decrease memory usage at the expense of slightly higher API usage, you can disable it and only enable --enable-managed-secrets-caching (which is the new default)
  2. In ALL cases (even when CreationPolicy is Merge), if a data key in the target Secret was created by the ExternalSecret, and it no longer exists in the template (or data/dataFrom), it will be removed from the target secret:
    1. This might cause some peoples secrets to be "cleaned of data keys" when updating to 0.11.
    2. Previously, the behaviour was undefined, and confusing because it was sort of broken when the template feature was added.
    3. The one exception is that ALL the data suddenly becomes empty and the DeletionPolicy is retain, in which case we will not even report and error, just change the SecretSynced message to explain that the secret was retained.
  3. When CreationPolicy is Owner, we now will NEVER retain any keys and fully calculate the "desired state" of the target secret each loop:
    1. This means that some peoples secrets might have keys removed when updating to 0.11.

Generators and ClusterGenerator

We added ClusterGenerators and Generator caching as well. This might create some problems in the way generators are defined now.

CRD Admission Restrictions

All of the CRDs now have proper kubebuilder markers for validation. This might surprise someone leaving out some data that was essentially actually required or expected in a certain format. This is now validated in #​4104.

Images

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

What's Changed

New Contributors

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

v0.10.7

Compare Source

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

What's Changed

New Contributors

Full Changelog: external-secrets/external-secrets@v0.10.6...v0.10.7

v0.10.6

Compare Source

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

What's Changed

New Contributors

Full Changelog: external-secrets/external-secrets@v0.10.5...v0.10.6

v0.10.5

Compare Source

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

What's Changed

New Contributors

Full Changelog: external-secrets/external-secrets@v0.10.4...v0.10.5

v0.10.4

Compare Source

WARNING: With this update, Pulumi has added projectID to it's required properties.

Image: oci.external-secrets.io/external-secrets/external-secrets:v0.10.4
Image: oci.external-secrets.io/external-secrets/external-secrets:v0.10.4-ubi
Image: oci.external-secrets.io/external-secrets/external-secrets:v0.10.4-ubi-boringssl

Default image registry change

From this version onwards, the default image registry name will be oci.external-secrets.io. While GHCR.io will keep on working for the foreseeable future, this change is to allow an eventual migration away from GHCR.

deprecation of GHCR - if performed, will be announced previous to its implementation and switch.

What's Changed

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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

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

This PR has been generated by Renovate Bot.

@public-glueops-renovatebot public-glueops-renovatebot bot changed the title chore(deps): update dependency https://github.com/external-secrets/external-secrets to v0.12.0 chore(deps): update dependency https://github.com/external-secrets/external-secrets to v0.12.1 Dec 23, 2024
@public-glueops-renovatebot public-glueops-renovatebot bot force-pushed the renovate/https-github.com-external-secrets-external-secrets-0.12.x branch from 466532d to 662411e Compare December 23, 2024 19:34
@sonarqubecloud SonarQubeCloud
Copy link

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
auto-update include-in-release-notes patch
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants