Skip to content

Update Helm release external-secrets to v0.16.1 #715

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
Merged
ricsanfre merged 1 commit into from
May 2, 2025
Merged

Update Helm release external-secrets to v0.16.1 #715

ricsanfre merged 1 commit into from
May 2, 2025

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Mar 21, 2025 •
edited
Loading

This PR contains the following updates:

Package Update Change
external-secrets minor 0.14.4 -> 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: external-secrets/external-secrets@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 and clustersecretstores crds:

Run the following command:

kubectl get crd \
    externalsecrets.external-secrets.io\
    secretstores.external-secrets.io\
    clustersecretstores.external-secrets.io\
    clusterexternalsecrets.external-secrets.io\
    -o jsonpath='{.items[*].status.storedVersions[?(@​=="v1alpha1")]}' | \
    grep -q v1alpha1 && echo "NOT SAFE! REMOVE v1alpha1 FROM YOUR STORED VERSIONS" || echo "Safe to Continue"

If that command returns not safe, remove v1alpha1 from your stored versions. Make sure this status is persisted after you verify these commands.

kubectl patch --subresource=status crd externalsecrets.external-secrets.io --type=json -p='[{"op": "replace", "path": "/status/storedVersions", "value": ["v1", "v1beta1"]}]' 
kubectl patch --subresource=status crd secretstores.external-secrets.io --type=json -p='[{"op": "replace", "path": "/status/storedVersions", "value": ["v1", "v1beta1"]}]' 
kubectl patch --subresource=status crd clusterexternalsecrets.external-secrets.io --type=json -p='[{"op": "replace", "path": "/status/storedVersions", "value": ["v1", "v1beta1"]}]' 
kubectl patch --subresource=status crd clustersecretstores.external-secrets.io --type=json -p='[{"op": "replace", "path": "/status/storedVersions", "value": ["v1", "v1beta1"]}]'

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 is

helm repo update
helm upgrade <your_app_name> external-secrets/external-secrets --version 0.16.1

The 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:

kubectl apply -f https://raw.githubusercontent.com/external-secrets/external-secrets/v0.16.1/deploy/crds/bundle.yaml

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 and clustersecretstores crds:

Run the following command:

kubectl get crd \
    externalsecrets.external-secrets.io\
    secretstores.external-secrets.io\
    clustersecretstores.external-secrets.io\
    clusterexternalsecrets.external-secrets.io\
    -o jsonpath='{.items[*].status.storedVersions[?(@&#8203;=="valpha1")]}' | \
    grep -q v1alpha1 && echo "NOT SAFE! REMOVE v1alpha1 FROM YOUR STORED VERSIONS" || echo "Safe to Continue"

If that command returns not safe, remove v1alpha1 from your stored versions. Make sure this status is persisted after you verify these commands.

kubectl patch --subresource=status crd externalsecrets.external-secrets.io --type=json -p='[{"op": "replace", "path": "/status/storedVersions", "value": ["v1", "v1beta1"]}]' 
kubectl patch --subresource=status crd secretstores.external-secrets.io --type=json -p='[{"op": "replace", "path": "/status/storedVersions", "value": ["v1", "v1beta1"]}]' 
kubectl patch --subresource=status crd clusterexternalsecrets.external-secrets.io --type=json -p='[{"op": "replace", "path": "/status/storedVersions", "value": ["v1", "v1beta1"]}]' 
kubectl patch --subresource=status crd clustersecretstores.external-secrets.io --type=json -p='[{"op": "replace", "path": "/status/storedVersions", "value": ["v1", "v1beta1"]}]'

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 is

helm repo update
helm upgrade <your_app_name> external-secrets/external-secrets --version 0.16.1

The 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:

kubectl apply -f https://raw.githubusercontent.com/external-secrets/external-secrets/v0.16.1/deploy/crds/bundle.yaml

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 to 0.16.0 on your installation path. That should be fixed on this release

My 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:

  • Removal of Conversion Webhooks and SecretStore/v1alpha1, ExternalSecret/v1alpha1 and their cluster counterparts
  • Promotion of ExternalSecret/v1 and SecretStore/v1 and their cluster counterparts
  • Removal of v1 templating engine
  • Removal of ValueMaps from Fake Secret Store

if you have any issues during your upgrade, please check https://github.com/external-secrets/external-secrets/issues/4662

What's Changed

New Contributors

Full Changelog: external-secrets/external-secrets@v0.15.1...v0.16.0

v0.15.1

Compare Source

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

v0.15.0

Compare Source

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

What's Changed

New Contributors

Full Changelog: external-secrets/external-secrets@v0.14.4...v0.15.0

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.

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

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot changed the title Update Helm release external-secrets to v0.15.0 Update Helm release external-secrets to v0.15.1 Mar 28, 2025
@renovate renovate bot force-pushed the renovate/external-secrets-0.x branch from ab21619 to a0943dd Compare March 28, 2025 22:07
@renovate renovate bot force-pushed the renovate/external-secrets-0.x branch from a0943dd to f8c4868 Compare April 14, 2025 18:57
@renovate renovate bot changed the title Update Helm release external-secrets to v0.15.1 Update Helm release external-secrets to v0.16.0 Apr 14, 2025
@renovate renovate bot force-pushed the renovate/external-secrets-0.x branch from f8c4868 to 88da37c Compare April 16, 2025 15:47
@renovate renovate bot changed the title Update Helm release external-secrets to v0.16.0 Update Helm release external-secrets to v0.16.1 Apr 16, 2025
@renovate renovate bot force-pushed the renovate/external-secrets-0.x branch from 88da37c to 0d63c79 Compare May 2, 2025 07:52
@renovate renovate bot force-pushed the renovate/external-secrets-0.x branch from 0d63c79 to 6742e04 Compare May 2, 2025 08:49
@ricsanfre ricsanfre merged commit fd80768 into master May 2, 2025
1 check passed
@renovate renovate bot deleted the renovate/external-secrets-0.x branch May 2, 2025 10:11
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

renovate/helm type/minor

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@ricsanfre