Using global parameter in helm without running master chart
Multi tool use
up vote
0
down vote
favorite
I have this structure of helm charts:
-chart A-
-chart A1
-chart A2
-chart B-
-chart B1
-chart B2
-chart C-
-chart C1
-chart C3
What I need is a global parameter or environment variable that I can apply to all charts without having a master chart above all charts.
So when I will run helm install I wouldnt have to pass this parameter using --set to all "main" charts (A,B,C).
Is this possible?
kubernetes-helm helm
add a comment |
up vote
0
down vote
favorite
I have this structure of helm charts:
-chart A-
-chart A1
-chart A2
-chart B-
-chart B1
-chart B2
-chart C-
-chart C1
-chart C3
What I need is a global parameter or environment variable that I can apply to all charts without having a master chart above all charts.
So when I will run helm install I wouldnt have to pass this parameter using --set to all "main" charts (A,B,C).
Is this possible?
kubernetes-helm helm
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have this structure of helm charts:
-chart A-
-chart A1
-chart A2
-chart B-
-chart B1
-chart B2
-chart C-
-chart C1
-chart C3
What I need is a global parameter or environment variable that I can apply to all charts without having a master chart above all charts.
So when I will run helm install I wouldnt have to pass this parameter using --set to all "main" charts (A,B,C).
Is this possible?
kubernetes-helm helm
I have this structure of helm charts:
-chart A-
-chart A1
-chart A2
-chart B-
-chart B1
-chart B2
-chart C-
-chart C1
-chart C3
What I need is a global parameter or environment variable that I can apply to all charts without having a master chart above all charts.
So when I will run helm install I wouldnt have to pass this parameter using --set to all "main" charts (A,B,C).
Is this possible?
kubernetes-helm helm
kubernetes-helm helm
edited Nov 11 at 9:25
asked Nov 9 at 16:47
Shachar Hamuzim Rajuan
1,47311941
1,47311941
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
up vote
1
down vote
accepted
You can give multiple --set
and -f
options to helm install
, and so the best solution available is to write your "global" settings into a file and always pass a -f global-settings.yaml
option to helm install
(along with whatever other chart-specific settings and values files you have).
If everything you're installing is in a single namespace, depending on what the settings actually do, it may work to put them into a shared ConfigMap. This is a little trickier to manage (you probably need to manually run kubectl
commands), and there are many things you can do with Helm values that you couldn't with a shared ConfigMap. But, it's "automatic" in the way you suggest in the question; you don't need any Helm options at all to use it.
add a comment |
up vote
1
down vote
You might want to consider using a xxx.yaml
file to override your charts default properties and template this file with that environment variable. I think that approach is much more maintainable than using --set
cli option.
Another approach is using something like Landscaper, listed on the Helm documentation, to template your charts ins an easy way
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
You can give multiple --set
and -f
options to helm install
, and so the best solution available is to write your "global" settings into a file and always pass a -f global-settings.yaml
option to helm install
(along with whatever other chart-specific settings and values files you have).
If everything you're installing is in a single namespace, depending on what the settings actually do, it may work to put them into a shared ConfigMap. This is a little trickier to manage (you probably need to manually run kubectl
commands), and there are many things you can do with Helm values that you couldn't with a shared ConfigMap. But, it's "automatic" in the way you suggest in the question; you don't need any Helm options at all to use it.
add a comment |
up vote
1
down vote
accepted
You can give multiple --set
and -f
options to helm install
, and so the best solution available is to write your "global" settings into a file and always pass a -f global-settings.yaml
option to helm install
(along with whatever other chart-specific settings and values files you have).
If everything you're installing is in a single namespace, depending on what the settings actually do, it may work to put them into a shared ConfigMap. This is a little trickier to manage (you probably need to manually run kubectl
commands), and there are many things you can do with Helm values that you couldn't with a shared ConfigMap. But, it's "automatic" in the way you suggest in the question; you don't need any Helm options at all to use it.
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
You can give multiple --set
and -f
options to helm install
, and so the best solution available is to write your "global" settings into a file and always pass a -f global-settings.yaml
option to helm install
(along with whatever other chart-specific settings and values files you have).
If everything you're installing is in a single namespace, depending on what the settings actually do, it may work to put them into a shared ConfigMap. This is a little trickier to manage (you probably need to manually run kubectl
commands), and there are many things you can do with Helm values that you couldn't with a shared ConfigMap. But, it's "automatic" in the way you suggest in the question; you don't need any Helm options at all to use it.
You can give multiple --set
and -f
options to helm install
, and so the best solution available is to write your "global" settings into a file and always pass a -f global-settings.yaml
option to helm install
(along with whatever other chart-specific settings and values files you have).
If everything you're installing is in a single namespace, depending on what the settings actually do, it may work to put them into a shared ConfigMap. This is a little trickier to manage (you probably need to manually run kubectl
commands), and there are many things you can do with Helm values that you couldn't with a shared ConfigMap. But, it's "automatic" in the way you suggest in the question; you don't need any Helm options at all to use it.
answered Nov 11 at 1:43
David Maze
7,6892820
7,6892820
add a comment |
add a comment |
up vote
1
down vote
You might want to consider using a xxx.yaml
file to override your charts default properties and template this file with that environment variable. I think that approach is much more maintainable than using --set
cli option.
Another approach is using something like Landscaper, listed on the Helm documentation, to template your charts ins an easy way
add a comment |
up vote
1
down vote
You might want to consider using a xxx.yaml
file to override your charts default properties and template this file with that environment variable. I think that approach is much more maintainable than using --set
cli option.
Another approach is using something like Landscaper, listed on the Helm documentation, to template your charts ins an easy way
add a comment |
up vote
1
down vote
up vote
1
down vote
You might want to consider using a xxx.yaml
file to override your charts default properties and template this file with that environment variable. I think that approach is much more maintainable than using --set
cli option.
Another approach is using something like Landscaper, listed on the Helm documentation, to template your charts ins an easy way
You might want to consider using a xxx.yaml
file to override your charts default properties and template this file with that environment variable. I think that approach is much more maintainable than using --set
cli option.
Another approach is using something like Landscaper, listed on the Helm documentation, to template your charts ins an easy way
answered Nov 11 at 15:34
Carlos
211
211
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53230007%2fusing-global-parameter-in-helm-without-running-master-chart%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
3P 3fxe,jR4DzD,GkzqAds,DqOPTT,6zA6znWa7RDD3 nwMHUUFenezqPKALHKqL6,rR n,oeCtX4TGWcuai77vpnI1tiq08