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.

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

Kustomization failure. HelmRepository dry-run failed: .spec.provider: field not declared in schema #4862

Open
1 task done
kamalverma1 opened this issue Jun 28, 2024 · 1 comment

Comments

@kamalverma1
Copy link

Describe the bug

Hi I am using fluxcd helmchart version 2.13.0 and recently tried to upgrade the api version of HelmRepository from v1beta1 to v1. After updating the API version, the kustomization fails with the below error:

HelmRepository/<namespace>/<helmrelease_name> dry-run failed: .spec.provider: field not declared in schema

As I checked the .spec.provider parameter is not present in crd version v1beta1 but is present in v1beta2 and v1.

Steps to reproduce

  1. Install flux helmchart version 2.13.0.
  2. Apply a helmRepository Resource with v1beta1 version and update the version to v1.

Expected behavior

The updgrading of the flux api version from v1beta1 to v1 should work without error.

Screenshots and recordings

No response

OS / Distro

Linux

Flux version

2.3.0

Flux check

K8s version 1.29.4

Git provider

No response

Container Registry provider

No response

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@kamalverma1
Copy link
Author

After removing the default value "generic" of provider in helmrepository crd, the error was gone. I am not sure why is it added as a required field. And even if it is added as default, it should not how the error.

@kamalverma1 kamalverma1 changed the title Kustomization failure HelmRepository dry-run failed: .spec.provider: field not declared in schema Kustomization failure. HelmRepository dry-run failed: .spec.provider: field not declared in schema Jul 4, 2024
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

No branches or pull requests

1 participant