1
00:00:00,000 --> 00:00:11,666
Hi, Let us understand how to change the default value from the values.yaml file when the release is

2
00:00:11,666 --> 00:00:15,199
getting released. Let's use the same example.

3
00:00:15,200 --> 00:00:17,466
I do have the values YAML file.

4
00:00:17,466 --> 00:00:24,899
Let me go ahead and do a dry run, and I want to replace the cost code with some other value, so I can

5
00:00:24,900 --> 00:00:31,266
use the set flag helm install dry run

6
00:00:31,266 --> 00:00:41,566
I want to run it in the debug mode and I'm going to set the key cost code to this specific value and

7
00:00:41,566 --> 00:00:48,099
the name of the release is and the chart resources to use from this specific folder.

8
00:00:48,100 --> 00:00:51,800
So what's going to do when the template is getting generated

9
00:00:51,800 --> 00:00:55,300
The value will be computed from the values.yaml file.

10
00:00:55,300 --> 00:01:01,300
And if any value is set within the command prompt, the set is going to get more precedence

11
00:01:01,300 --> 00:01:08,000
So what will happen, the value provided over here will be replaced within the computed values file.

12
00:01:08,000 --> 00:01:13,500
And that will be replaced within the templates.

13
00:01:13,500 --> 00:01:15,366
So this is what the computed value.

14
00:01:15,366 --> 00:01:20,499
The reason, because the user supplied this specific value using this set command.

15
00:01:20,500 --> 00:01:23,866
And it got replaced. This is the final computed value.

16
00:01:23,866 --> 00:01:26,099
And the same would get replaced. Many times

17
00:01:26,100 --> 00:01:31,866
I may want to do a release with some custom value, and I don't want to use that default value, for that

18
00:01:31,866 --> 00:01:36,999
particular purpose I can use this specific set and doing the installation also

19
00:01:37,000 --> 00:01:43,133
I can use the set. Let me go ahead and do a small demo helm install

20
00:01:43,133 --> 00:01:45,833
Name of the release and then release resources.

21
00:01:45,833 --> 00:01:53,133
Then --set key and the value that I want to replace with.

22
00:01:53,133 --> 00:01:57,533
It is done. Let me go ahead and get the manifest using the release name.

23
00:01:57,533 --> 00:02:05,433
helm get manifest and the name of the release valueseteg, so here its

24
00:02:05,433 --> 00:02:10,098
Using the new value that we provided as a part of the command prompt.

25
00:02:10,100 --> 00:02:16,033
And this would have done a deployment of a config maps so I can check the value of the config map as

26
00:02:16,033 --> 00:02:18,433
well within the config map

27
00:02:18,433 --> 00:02:25,566
Also, I do have the value that I passed along with the command prompt, so I can change the value thats provided

28
00:02:25,566 --> 00:02:29,899
as a part of the values YAML file as well during the deployment.

29
00:02:29,900 --> 00:02:35,733
This I will be using it whenever I wanted to do any custom deployment and change the value only

30
00:02:35,733 --> 00:02:38,333
for that specific release.

31
00:02:38,333 --> 00:02:44,566
Let me go ahead and delete this release helm uninstall name of the release

32
00:02:44,566 --> 00:02:50,032
So in a quick summary we have seen how to use the set flag as a part of the command prompt to change the

33
00:02:50,033 --> 00:02:52,966
values provided by the values yaml file.

