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

useJenkinsProxy is not rendered in template #1075

Open
RIHELO opened this issue Apr 23, 2024 · 0 comments
Open

useJenkinsProxy is not rendered in template #1075

RIHELO opened this issue Apr 23, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@RIHELO
Copy link

RIHELO commented Apr 23, 2024

Describe the bug

I downloaded the latest Chart.yaml
I downloaded and updated the values.yaml
The value in particular that is not rendered is under:
jenkins
clouds
- kubernetes
useJenkinsProxy: true

After I run helm template jenkins jenkins/jenkins --namespace test -f values.yaml > output.yaml
The output.yaml does not contain the useJenkinsProxy: true

Version of Helm and Kubernetes

- Helm: v3.13.3
- Kubernetes: v1.27.9

Chart version

2.440.3-jdk17

What happened?

1. Download Chart.yaml
2. Download values.yaml
3. Edit the values.yaml file and add the useJenkinsProxy: true like below:
jenkins
  clouds
    - kubernetes
      useJenkinsProxy: true
4. Run: 
helm template jenkins jenkins/jenkins --namespace test  -f values.yaml > output.yaml

5. grep useJenkinsProxy output.yaml returns nothing, so this param is not rendered.

What you expected to happen?

I expected the output.yaml to contain the useJenkinsProxy: true.
In fact when I edit the output.yaml file and add the useJenkinsProxy: true and apply then it is configured correctly.

How to reproduce it

Same steps as in the What happened question.

Anything else we need to know?

No response

@RIHELO RIHELO added the bug Something isn't working label Apr 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant