forked from spotahome/redis-operator
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Comments
Helm explicitly does not support templating in CRD resources. |
pascaliske
added a commit
to pascaliske/redis-operator
that referenced
this issue
Dec 20, 2024
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
(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:
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
The text was updated successfully, but these errors were encountered: