Update Ironbank
This MR contains the following updates:
| Package | Update | Change |
|---|---|---|
| gluon | patch |
0.5.10 -> 0.5.12
|
| registry1.dso.mil/ironbank/opensource/external-secrets/external-secrets (source) | minor |
v0.10.4 -> v0.11.0
|
| registry1.dso.mil/ironbank/opensource/external-secrets/external-secrets (source) | minor |
0.10.4 -> 0.11.0
|
| registry1.dso.mil/ironbank/opensource/kubernetes/kubectl (source) | minor |
v1.29.6 -> v1.30.7
|
Complete MR checklist
Assignee
-
Followed upgrade instructions outlined in docs/DEVELOPMENT_MAINTENANCE.md -
Update Docs with new/updated steps as needed -
Tested and Validated Changes made with supporting info like logs or screenshots from test pipelines
Add supporting info below
Reviewer only
-
Tested and Validated changes
Configuration
-
If you want to rebase/retry this MR, check this box
This MR was automatically generated by Renovate Bot.
Upgrade Notices
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:
- This might cause some secrets to be "cleaned of data keys" when updating to 0.11.
- Previously, the behaviour was undefined, and confusing because it was sort of broken when the template feature was added.
- The one exception is that ALL the data suddenly becomes empty and the DeletionPolicy is retain, in which case ESO will not even report and error, just change the SecretSynced message to explain that the secret was retained.
When CreationPolicy is Owner, ESO now will NEVER retain any keys and fully calculate the "desired state" of the target secret each loop:
- This means that some secrets might have keys removed when updating to 0.11.