Welcome back everybody.
In the next section we're going to be hosting our Kubernetes cluster on AWS.
So we don't actually need the cluster that's being hosted through Docker desktop anymore.
So if you say kubectl config current context it shows you the cluster that kubectl is interacting with.
In this case the local cluster that's being hosted through Docker desktop.
But in the next section that's going to change such that our kubectl commands are going to be pointing
to our cluster.
And so ideally we want to clean up all of the heavy resources that we have running in our local Kubernetes
cluster.
So if the first thing I want you to do is run helm list, dash, dash all dash namespaces, that's going
to show you all the helm releases that you have across all your namespaces.
Okay.
Then what I want you to do is uninstall the MongoDB community operator in MongoDB.
I've already gone ahead and done that because the MongoDB stateful sets were just so heavy and taxing
on my machine, and it was making my computer very, very sluggish.
So please do feel free to uninstall the community.
Operator.
So this should remove the operator.
This should remove the custom resource definition that you deployed.
It should remove all the native Kubernetes resources that were created as per whatever you defined in
your custom resource definition.
So anything involved with our MongoDB deployment, uh, should be removed by uninstalling the helm release.
Um, might as well also remove the great submission API, uh, as well as the great submission portal.
Okay, so make sure that you specify the respective namespace where each, uh, helm release is in in
order to properly uninstall it.
Once you do that, you should be good to go.
I've already gone ahead and done that.
Um, after we deploy, after we host our cluster on AWS, then we're going to completely remove the
Kubernetes cluster that we have locally.
So for now, don't worry about completely uninstalling everything.
Let's just remove the most taxing processes first so that we're ready in the next section to host another
cluster on AWS and interact with that instead.
Okay, I'll see you in the next one.