WEBVTT

00:00.000 --> 00:00.870
Welcome back everybody.

00:00.870 --> 00:05.700
In the next section we're going to be hosting our Kubernetes cluster on AWS.

00:05.700 --> 00:12.390
So we don't actually need the cluster that's being hosted through Docker desktop anymore.

00:12.390 --> 00:20.160
So if you say kubectl config current context it shows you the cluster that kubectl is interacting with.

00:20.160 --> 00:24.450
In this case the local cluster that's being hosted through Docker desktop.

00:24.450 --> 00:29.910
But in the next section that's going to change such that our kubectl commands are going to be pointing

00:29.940 --> 00:30.990
to our cluster.

00:30.990 --> 00:38.690
And so ideally we want to clean up all of the heavy resources that we have running in our local Kubernetes

00:38.690 --> 00:39.110
cluster.

00:39.110 --> 00:46.010
So if the first thing I want you to do is run helm list, dash, dash all dash namespaces, that's going

00:46.010 --> 00:50.900
to show you all the helm releases that you have across all your namespaces.

00:50.900 --> 00:51.650
Okay.

00:51.650 --> 00:57.440
Then what I want you to do is uninstall the MongoDB community operator in MongoDB.

00:57.740 --> 01:05.290
I've already gone ahead and done that because the MongoDB stateful sets were just so heavy and taxing

01:05.290 --> 01:09.880
on my machine, and it was making my computer very, very sluggish.

01:09.880 --> 01:12.970
So please do feel free to uninstall the community.

01:12.970 --> 01:13.510
Operator.

01:13.510 --> 01:15.760
So this should remove the operator.

01:15.760 --> 01:19.630
This should remove the custom resource definition that you deployed.

01:19.630 --> 01:26.470
It should remove all the native Kubernetes resources that were created as per whatever you defined in

01:26.470 --> 01:27.820
your custom resource definition.

01:27.820 --> 01:34.950
So anything involved with our MongoDB deployment, uh, should be removed by uninstalling the helm release.

01:35.370 --> 01:41.430
Um, might as well also remove the great submission API, uh, as well as the great submission portal.

01:41.430 --> 01:47.490
Okay, so make sure that you specify the respective namespace where each, uh, helm release is in in

01:47.490 --> 01:49.380
order to properly uninstall it.

01:49.680 --> 01:52.620
Once you do that, you should be good to go.

01:52.620 --> 01:54.720
I've already gone ahead and done that.

01:55.200 --> 02:04.720
Um, after we deploy, after we host our cluster on AWS, then we're going to completely remove the

02:04.720 --> 02:06.640
Kubernetes cluster that we have locally.

02:06.640 --> 02:10.390
So for now, don't worry about completely uninstalling everything.

02:10.390 --> 02:17.800
Let's just remove the most taxing processes first so that we're ready in the next section to host another

02:17.800 --> 02:21.460
cluster on AWS and interact with that instead.

02:21.460 --> 02:23.770
Okay, I'll see you in the next one.