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
Unable to Deploy (Manifest) Redis 6.4.0 Chart #4109
Comments
Just to clarify - this error looks like it comes from the deploy stage. Could you post the pipeline JSON and the execution JSON if that's not the case? Issues similar to this have been the subject of some conversation during recent Kubernetes SIG mettings. We're doing a bit of work for 1.13 around SpEL interpretation in bake and deploy stages to try and help handle cases like these. |
Sorry, you're absolutely correct - it's from Deploy. I'll update. |
This issue hasn't been updated in 45 days, so we are tagging it as 'stale'. If you want to remove this label, comment:
|
This issue is tagged as 'stale' and hasn't been updated in 45 days, so we are tagging it as 'to-be-closed'. It will be closed in 45 days unless updates are made. If you want to remove this label, comment:
|
Same issue here. I'm deploying an app with a simple bash script as ConfigMap. It goes through helm but fails in spinnaker.
|
Same issue. Running spinnaker 1.14.9 on kops cluster and stable/redis 8.1.2. |
@spinnakerbot remove-label stale |
@spinnakerbot remove-label to-be-closed |
My step to reproduce:
|
This issue hasn't been updated in 45 days, so we are tagging it as 'stale'. If you want to remove this label, comment:
|
@spinnakerbot remove-label stale |
Hi all! I'm going to close this as a workaround to this issue was released with Spinnaker 1.13 -- more details on this PR. |
Hello, this seems to be happening again on Spinnaker 1.25.4. |
Issue Summary:
Running Deploy (Manifest) on Redis 6.4.0 chart as part of a deployment breaks due to characters within the manifest being interpreted wrongly by the SPEL parser.
Cloud Provider(s):
Kubernetes v2
Environment:
Kops cluster running Spinnaker 1.12.5.
Feature Area (if this issue is UI/UX related, please tag
@spinnaker/ui-ux-team
):CloudDriver
Description:
Previous versions of the redis chart didn't include the
{ARGS[@]}
line and hence had no issues, but with this update the deploy stage now breaks.Since what they're doing is presumably legitimate Helm templating, Spinnaker should support deploying it - or at least provide some option to ignore certain files from being SPEL-parsed.
Steps to Reproduce:
Additional Details:
The text was updated successfully, but these errors were encountered: