Skip to content

Fix: Change external-secrets api version #237

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

Merged

Conversation

dmatviichuk
Copy link
Contributor

Fixes "The Kubernetes API could not find version "v1beta1" of external-secrets.io/ExternalSecret for requested resource retool-dev/vault-external-secrets. Version "v1" of external-secrets.io/ExternalSecret is installed on the destination cluster."

@dmatviichuk dmatviichuk force-pushed the bump-external-secrets-api-version branch from 1ef8e75 to bcdb152 Compare May 28, 2025 17:19
@jjlgao
Copy link
Contributor

jjlgao commented May 29, 2025

It seems this might be cluster-dependent, we may not be able to merge this as-is. We may want to add an if statement checking the externalsecrets CRD version on the cluster for this like we do here:

{{- if and .Values.psp.create (.Capabilities.APIVersions.Has "policy/v1beta1") }}

Thanks for the catch!

@dmatviichuk dmatviichuk force-pushed the bump-external-secrets-api-version branch from bcdb152 to 9080ad9 Compare June 13, 2025 20:49
@dmatviichuk dmatviichuk force-pushed the bump-external-secrets-api-version branch from d27fb14 to 501e7e5 Compare June 13, 2025 20:58
@dmatviichuk
Copy link
Contributor Author

@jjlgao it is fixed now and all checks are passed, please review

Copy link
Contributor

@jjlgao jjlgao left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the update!

@jjlgao jjlgao merged commit 09ec70f into tryretool:main Jun 13, 2025
12 checks passed
@jjlgao
Copy link
Contributor

jjlgao commented Jun 13, 2025

Just a heads up, I'll wait until we have a few other changes before we release a new version. If it's urgent for you to pull and use this change, happy to do so earlier.

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