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

helm CRD invalid due to templating variables #14

Open
warmfusion opened this issue Dec 5, 2024 · 2 comments · May be fixed by #16
Open

helm CRD invalid due to templating variables #14

warmfusion opened this issue Dec 5, 2024 · 2 comments · May be fixed by #16

Comments

@warmfusion
Copy link

(Copied from spotahome#700 (comment) )

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


Investigations in spotahome#700 shows that the issue relates to the introduction of template variables in the CRD which helm (by design) does not render.

As a consequence, the CRD output is invalid yaml.

The following lines should be removed from the CRD definition;

https://github.com/freshworks/redis-operator/blob/master/charts/redisoperator/crds/databases.spotahome.com_redisfailovers.yaml#L7-L9

@warmfusion
Copy link
Author

warmfusion referenced this issue Dec 5, 2024
pascaliske added a commit to pascaliske/redis-operator that referenced this issue Dec 20, 2024
@pascaliske
Copy link

Hi,

We also faced this issue with the latest release. So I created a PR to fix this: #16.

Hopefully we can get this merged & released soon after the holidays. 🙂

Merry Christmas! 🎅🏻

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 a pull request may close this issue.

2 participants