WEBVTT

00:00.330 --> 00:04.320
Now, we've seen how we can use Helme template that will be really useful is to see what would happen

00:04.320 --> 00:11.400
if we tried to deploy it so we can do is use Helme template and pipe the output and is a couple of ways

00:11.400 --> 00:14.040
we could go about doonas everyone into YAML file.

00:14.310 --> 00:17.190
We could just simply redirect the output into YAML false.

00:17.200 --> 00:22.200
We call this templated yaml and we should see the output.

00:24.170 --> 00:25.310
And we'll see here.

00:26.780 --> 00:32.330
And already I'm getting at underscore or an invitation saying something's missing since we got a good

00:32.330 --> 00:32.930
spot to go.

00:32.960 --> 00:34.680
OK, well, we can tell there's something missing here.

00:35.090 --> 00:36.330
We need to go ahead and sort that out.

00:36.830 --> 00:42.800
But as one last trick we can use, which actually simulates deploying it, the command we can use to

00:42.800 --> 00:48.620
simulate deploying it is going to be held template full stop for the context.

00:49.370 --> 00:53.180
We're going to pipe it to tubercle create.

00:55.640 --> 00:56.450
The chef.

00:57.750 --> 01:03.270
And in Dash, let me make my terminal bigger so you can see this come out, so we do is we get Helme

01:03.270 --> 01:05.510
template that's going to pipe out a YAML file.

01:06.180 --> 01:12.420
And what we'll do is pass into Cuba and we're going to pass in the dash f flat straight from file.

01:12.420 --> 01:14.930
And the dash is representing standard input.

01:14.940 --> 01:19.300
So we take the output from Helme template and possibly execute creates it on the fly.

01:19.590 --> 01:21.040
Now for go ahead and enter.

01:21.750 --> 01:25.740
Now we can see the deployment and it's got no names have seen double quotes.

01:25.950 --> 01:30.210
Is invalid metadata name required value that we've seen before.

01:30.220 --> 01:34.050
We sometimes get an error withheld when it goes to install, but it's not particularly useful that we

01:34.050 --> 01:38.570
saw, which is very generic and they need to start right away.

01:38.580 --> 01:41.060
I could see, OK, the name is missing for the deployment.

01:41.910 --> 01:50.940
So now if I go back and we it stops deployments, the name that will resolve the issue, we don't know

01:50.970 --> 01:54.460
its deployment name is because we don't have a look at values YAML file.

01:55.110 --> 01:56.270
Let me close my terminal now.

02:02.990 --> 02:04.480
Let me go ahead and close my turn.

02:04.610 --> 02:09.590
It's easy to see, you know, its deployment dot name and now that will work.

02:10.490 --> 02:15.230
So these are some really powerful troubleshooting techniques you can use with help, and I'll help you

02:15.230 --> 02:17.390
identify any issues you might have.

02:20.560 --> 02:25.300
These are some really powerful troubleshooting techniques you can use of help, and I recommend for

02:25.300 --> 02:30.310
up, of course, have a good using these if you run into any issues and if you're working in an industry,

02:30.550 --> 02:32.110
these are going to save you a lot of time.

02:32.510 --> 02:34.240
So this wraps up the troubleshooting section.

02:34.510 --> 02:36.140
Let's jump in to the next section.

02:36.190 --> 02:37.480
I'll look forward to seeing you there.