1
00:00:00,000 --> 00:00:08,066
Hi, Let us understand how to do the rollback using the helm.

2
00:00:08,066 --> 00:00:12,099
Here I'm going to use the project that we used earlier for upgrade

3
00:00:12,100 --> 00:00:15,933
Let me go ahead and do an another upgrade. Before that let me check

4
00:00:15,933 --> 00:00:23,466
What are all the revisions available helm history and name of the deployment.

5
00:00:23,466 --> 00:00:30,699
So I do have two revisions, in that the revision two is deployed and the revision one is superseded.

6
00:00:30,700 --> 00:00:32,433
Now, I'm going to make another revision.

7
00:00:32,433 --> 00:00:37,233
Let me go ahead and make changes to the values.yaml file

8
00:00:37,233 --> 00:00:44,866
I'm making the replica count as three.

9
00:00:44,866 --> 00:00:51,766
Now, let me go ahead and make changes to the chart.yaml file

10
00:00:51,766 --> 00:00:58,766
I'm going to make change to the description.

11
00:00:58,766 --> 00:01:09,599
And change the version say I want to make this particular version as 1.1

12
00:01:09,600 --> 00:01:17,400
Now, I'm going to push this change into the repo, without pushing into the repo directly I can deploy the chart.

13
00:01:17,400 --> 00:01:23,533
But to understand the standard way of deployment I'm pushing it into the repository.

14
00:01:23,533 --> 00:01:28,166
Then to check whether it is available before that I need to do the

15
00:01:28,166 --> 00:01:36,232
upgrade and search the repository using helm search command helm search repo

16
00:01:36,233 --> 00:01:38,799
And I'm going to provide the -l option.

17
00:01:38,800 --> 00:01:41,766
where I'll get all the versions of the chart. Here I do

18
00:01:41,766 --> 00:01:48,532
have the latest version that we pushed into the repository that is 1.1.0

19
00:01:48,533 --> 00:01:51,966
Now I'm going to upgrade the helm deployment.

20
00:01:51,966 --> 00:01:58,332
Let me check what are all the deployments available helm list

21
00:01:58,333 --> 00:02:02,266
So this is the deployment and the revision that is running is two.

22
00:02:02,266 --> 00:02:03,732
I'm going to do an upgrade.

23
00:02:03,733 --> 00:02:10,066
helm upgrade and name of the helm deployment and the repository to use.

24
00:02:10,066 --> 00:02:17,666
So did the deployment and the revision got changed to three. Now I can check helm list.

25
00:02:17,666 --> 00:02:20,132
So the revision that is running is three.

26
00:02:20,133 --> 00:02:23,799
I can get the entire history of the helm deployment.

27
00:02:23,800 --> 00:02:29,833
This specific deployment using the helm history command, helm history and name of the deployment

28
00:02:29,833 --> 00:02:36,633
install upgrade rlbk-demo so I do have three revisions.

29
00:02:36,633 --> 00:02:39,333
Now the version that is running is three.

30
00:02:39,333 --> 00:02:45,566
I can confirm using cubectl command, cubectl get all

31
00:02:45,566 --> 00:02:48,499
So I do have three pods running. Now

32
00:02:48,500 --> 00:02:53,000
For some reason I realized this particular revision is not good.

33
00:02:53,000 --> 00:02:59,966
So I wanted to roll back to the revision two, so I can use the command helm rollback and name of

34
00:02:59,966 --> 00:03:03,532
the deployment and the revision that I wanted to rollback to.

35
00:03:03,533 --> 00:03:08,999
It's as simple as one simple command can roll back to the revision that I wanted.

36
00:03:09,000 --> 00:03:13,200
So the command is helm rollback and name of the deployment and the revision

37
00:03:13,200 --> 00:03:16,833
I wanted to rollback to. So the rollback is success.

38
00:03:16,833 --> 00:03:25,333
Now I can go ahead and check the history of this specific deployment, helm history

39
00:03:25,333 --> 00:03:34,466
And I do have the revision four and the revision four is rollbacked to two, so the revision that is deployed is four

40
00:03:34,466 --> 00:03:41,132
And that got rolled back to the revision two and within revision two we had two pods

41
00:03:41,133 --> 00:03:46,199
I can go ahead and check whether two pods are running

42
00:03:46,200 --> 00:03:49,166
cubectl get all I do have only two pods.

43
00:03:49,166 --> 00:03:55,099
So automatically it went ahead and made the changes to the required number of pods.

44
00:03:55,100 --> 00:04:02,300
So this is going to prove how easy it is to upgrade or rollback any deployment using helm package manager.

45
00:04:02,300 --> 00:04:08,333
And this is one of the biggest advantage and that's where helm is going to have the edge.

46
00:04:08,333 --> 00:04:13,799
So in a quick summary we have seen how to do the upgrade and rollback of a deployment using helm.