1 00:00:00,000 --> 00:00:05,000 Hi, Lets understand about 2 00:00:05,000 --> 00:00:12,266 Get and status option available within helm. Once the service is deployed within the cluster using helm 3 00:00:12,266 --> 00:00:15,099 I can get the status using the status command 4 00:00:15,100 --> 00:00:22,766 or I can get more information using the get command. Let's see some options using get as well as status. 5 00:00:22,766 --> 00:00:29,499 Let's check what are all the list of deployments available using helm list. So this is the deployment. 6 00:00:29,500 --> 00:00:39,200 Let me get the deployment name and I can use the command helm get notes 7 00:00:39,200 --> 00:00:44,966 So that will get me the notes mentioned for this particular deployment. In case after the deployment 8 00:00:44,966 --> 00:00:48,432 if you missed a specific note, I can go ahead and get the notes 9 00:00:48,433 --> 00:00:55,633 Once again, by running this command helm get notes and then the deployment name as well as we can get 10 00:00:55,633 --> 00:01:01,666 What are all the values that were passed using the command prompt while starting this particular service, 11 00:01:01,666 --> 00:01:06,832 using the command helm get values and name of the service. 12 00:01:06,833 --> 00:01:11,666 as such while doing the specific deployment, we did not pass any user defined values. 13 00:01:11,666 --> 00:01:16,099 So nothing getting listed and how the templates were rendered 14 00:01:16,100 --> 00:01:27,966 I can get the rendered template using the command get manifest, helm get manifest and name of the deployment. 15 00:01:27,966 --> 00:01:29,966 So that's going to get us the 16 00:01:29,966 --> 00:01:36,199 rendered manifest, by merging the template and the values and what was used to do the deployment 17 00:01:36,200 --> 00:01:38,866 of the entity within the kubernetes cluster. 18 00:01:38,866 --> 00:01:46,332 This will be useful to do the debugging in case if any of the deployed services not behaving as expected. 19 00:01:46,333 --> 00:01:52,533 And in case if I have added any hooks as a part of the deployment, I can use the command get hooks 20 00:01:52,533 --> 00:01:58,499 And then the deployment name. In this case, if you remember earlier we discussed about the test condition 21 00:01:58,500 --> 00:02:02,300 that was a hook because it was added as a hook within the annotation 22 00:02:02,300 --> 00:02:07,466 And only that specific hook is getting listed and what is a hook. 23 00:02:07,466 --> 00:02:10,265 We have a detailed discussion in a separate lecture. 24 00:02:10,265 --> 00:02:12,199 And this particular command get hooked 25 00:02:12,200 --> 00:02:18,500 It's going to list all the hooks that were attached as a part of that specific deployment. 26 00:02:18,500 --> 00:02:28,733 I can get all this information that is notes, values, manifest and hook using the command get all. 27 00:02:28,733 --> 00:02:31,766 helm get all and name of the deployment 28 00:02:31,766 --> 00:02:38,232 where I will be getting the notes, values, manifest and hook. 29 00:02:38,233 --> 00:02:44,166 So this is one way of verifying what got deployed and what values were deployed as a part of the services 30 00:02:44,166 --> 00:02:51,266 as well as I can get a quick status about that specific deployment using the command helm status and name of the deployment. 31 00:02:51,266 --> 00:02:56,799 That's going to provide me the status of what provision is deployed and what is the status, in which 32 00:02:56,800 --> 00:03:02,566 namespace it was deployed, when it was deployed and what was the test suite that is hooked as a part 33 00:03:02,566 --> 00:03:06,599 of this specific deployment and whether that was invoked or not 34 00:03:06,600 --> 00:03:09,000 And the notes along with that specific deployment. 35 00:03:09,000 --> 00:03:14,533 So basically, it's going to give a quick summary on what was deployed and its current status. 36 00:03:14,533 --> 00:03:19,899 So this is a quick summary on how to use the get and status command to understand about the deployment.