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

Issue while applying helm chart #700

Closed
tornado67 opened this issue Jul 12, 2024 · 4 comments
Closed

Issue while applying helm chart #700

tornado67 opened this issue Jul 12, 2024 · 4 comments
Labels

Comments

@tornado67
Copy link

tornado67 commented Jul 12, 2024

Expected behaviour

A redis operator has to be installed successfully.

Actual behaviour

Fails out of the box.
Command
helm install redis-operator redis-operator/redis-operator

fails with the following error:

PS C:\Users\user\Documents\projects\p1\cicd> helm install redis-operator redis-operator/redis-operator
Error: INSTALLATION FAILED: failed to install CRD crds/databases.spotahome.com_redisfailovers.yaml: error parsing : error converting YAML to JSON: yaml: line 4: did not find expected node content

Steps to reproduce the behaviour

Execute helm install redis-operator redis-operator/redis-operator

Environment

EKS cluster platform version eks.7
K8s version - 1.29

@cehoffman
Copy link

This was introduced between the 3.2.9 and 3.3.0 chart versions. I just tried updating the chart and got a similar error to above.

@warmfusion
Copy link

I ran into this problem, but it's a side-effect of Helm's specific design and not a bug persay.

Helm explicitly does not support templating in CRD resources.

https://helm.sh/docs/chart_best_practices/custom_resource_definitions/#:~:text=This%20is%20also%20the%20reason%20behind%20removing%20templating%20support%20from%20CRDs.

warmfusion referenced this issue Aug 8, 2024
Copy link

This issue is stale because it has been open for 45 days with no activity.

@github-actions github-actions bot added the stale label Sep 23, 2024
Copy link

github-actions bot commented Oct 7, 2024

This issue was closed because it has been inactive for 14 days since being marked as stale.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants