Update Helm release external-secrets to v0.16.1 - autoclosed #130
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate/external-secrets-0.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
0.15.1
->0.16.1
Release Notes
external-secrets/external-secrets (external-secrets)
v0.16.1
Compare Source
Image:
ghcr.io/external-secrets/external-secrets:v0.16.1
Image:
ghcr.io/external-secrets/external-secrets:v0.16.1-ubi
Image:
ghcr.io/external-secrets/external-secrets:v0.16.1-ubi-boringssl
What's Changed
Full Changelog: https://github.com/external-secrets/external-secrets/compare/v0.16.0...v0.16.1
Guide to Promoting to 0.16
Pre Upgrade checks
Make sure you are not using any
v1alpha1
resources across all of your infrastructure.You can do that by performing manual inspection on your manifests, tooling, etc.
Make sure there are no storedVersions on v1alpha1 for
externalsecrets
,clusterexternalsecrets
,secretstores
andclustersecretstores
crds:Run the following command:
If that command returns not safe, remove v1alpha1 from your stored versions. Make sure this status is persisted after you verify these commands.
Upgrading
CRDs as part of external-secrets installation
If you're installing external-secrets CRDs with helm (
installCRDs=true
- the default), all you need to do isThe same goes if you're using argocd or flux and managing crds directly with helm. The above should just work.
CRDs installed separately
If CRDs are installed separately, the first step you need to do is bump the crds:
Verify no error occurs. After that, you can freely migrate external-secrets to
v0.16.1
.Troubleshooting
conversion webhook for external-secrets.io/v1, Kind=ExternalSecret failed: the server could not find the requested resource
Root cause: the CRD installation process failed.
Double check your CRD installation process finished successfully
v0.16.0
Compare Source
Image:
ghcr.io/external-secrets/external-secrets:v0.16.0
Image:
ghcr.io/external-secrets/external-secrets:v0.16.0-ubi
Image:
ghcr.io/external-secrets/external-secrets:v0.16.0-ubi-boringssl
!!! warning
it is known v0.16.0 will not be an easy upgrade if you're not consuming from our official sources via helm.
we are improving the upgrade path for users depending on kustomize in
0.16.1
. Please be patient :)Guide to Promoting to 0.16
Pre Upgrade checks
Make sure you are not using any
v1alpha1
resources across all of your infrastructure.You can do that by performing manual inspection on your manifests, tooling, etc.
Make sure there are no storedVersions on v1alpha1 for
externalsecrets
,clusterexternalsecrets
,secretstores
andclustersecretstores
crds:Run the following command:
If that command returns not safe, remove v1alpha1 from your stored versions. Make sure this status is persisted after you verify these commands.
Upgrading
CRDs as part of external-secrets installation
If you're installing external-secrets CRDs with helm (
installCRDs=true
- the default), all you need to do isThe same goes if you're using argocd or flux and managing crds directly with helm. The above should just work.
CRDs installed separately
If CRDs are installed separately, the first step you need to do is bump the crds:
Verify no error occurs. After that, you can freely migrate external-secrets to
v0.16.1
.Troubleshooting
conversion webhook for external-secrets.io/v1, Kind=ExternalSecret failed: the server could not find the requested resource
Root cause: the CRD installation process failed.
Double check your CRD installation process finished successfully
spec.conversion.webhookClientConfig: Forbidden: should not be set when strategy is not set to Webhook
Use
0.16.1
as opposed to0.16.0
on your installation path. That should be fixed on this releaseMy issue is not here What do I do?
Add a message to https://github.com/external-secrets/external-secrets/issues/4662
BREAKING CHANGES
This release introduces quite a few breaking changes, including:
SecretStore/v1alpha1
,ExternalSecret/v1alpha1
and their cluster counterpartsExternalSecret/v1
andSecretStore/v1
and their cluster counterpartsv1
templating engineValueMaps
from Fake Secret Storeif you have any issues during your upgrade, please check https://github.com/external-secrets/external-secrets/issues/4662
What's Changed
95ea148
to3d0f463
by @dependabot in https://github.com/external-secrets/external-secrets/pull/460275e6700
to00eccd4
in /e2e by @dependabot in https://github.com/external-secrets/external-secrets/pull/46447772cb5
to7772cb5
by @dependabot in https://github.com/external-secrets/external-secrets/pull/4649New Contributors
Full Changelog: https://github.com/external-secrets/external-secrets/compare/v0.15.1...v0.16.0
Configuration
📅 Schedule: Branch creation - "* */1 * * *" in timezone US/Central, 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.
This PR has been generated by Renovate Bot.
a2d7e104b1
to8ac3db50b4
8ac3db50b4
to9463e7eb66
9463e7eb66
to033b68684c
033b68684c
to046e28af69
7d81441173
toa38f83e98a
a38f83e98a
to3a224faff9
Update Helm release external-secrets to v0.16.0to Update Helm release external-secrets to v0.16.1b210530d97
to8113692769
8113692769
toba30b7796b
ba30b7796b
to18423c3d34
18423c3d34
tof14f5768e1
f14f5768e1
to676a87bd0e
676a87bd0e
toe742a1e97f
e742a1e97f
to48b11c4363
48b11c4363
to67b31ffbe3
67b31ffbe3
toe682fa20cc
e682fa20cc
to2f34236887
2f34236887
to211a1b7a6f
211a1b7a6f
tob5ef6b9eb9
b5ef6b9eb9
to53174de8cb
53174de8cb
toa644296fe4
Update Helm release external-secrets to v0.16.1to Update Helm release external-secrets to v0.16.1 - autoclosedPull request closed