Now that you've got some semblance of an idea between the difference of a load balancer and an ingress
controller.
Let's take a look at the actual implementation this ingress controller and low balancer stuff that we're
going to use inside of our cluster.
So we are going to making use of a project called Ingress engine x.
This is a project or a open source library that's going to create a load balancer service in cyber cluster
plus an ingress automatically before we take a look at any documentation around ingress engine x.
I want to give you a very quick and extremely important note.
We are going to be using a project called Ingress engine X.
There is another extremely similar project with an almost identical name but it is not what we are using.
These are two very different projects.
They are provided by different organizations.
The second one is called Cuban eddies ingress.
So whenever you start to look at documentation or blog posts whatever else.
Make sure that whatever you're reading is related to ingress engine X and not Cuban eddies ingress.
As a matter of fact if I open up a new tab right now and do a search for Cuban eddies ingress and then
scroll down a little bit you're going to see that some of the top results here.
Here's some to get hub repos right here.
The first one that I see is ingress engine x.
That is what we are using.
We are not making use of humanity's ingress but they're right next to each other.
Really easy to click on one or the other.
Just make sure you're always looking at ingress engine X. That's long and short of it.
All right.
So then might let's take a look at some documentation around ingress engine X so I can open up a new
tab and do a search for ingress engine X and I should see hopefully as the first result or so to get
hub repo for ingress engine X.
Again make sure you're looking at ingress engine X..
I'm gonna go to that github repo and then right here at the very top and the description is a link to
the official documentation.
I believe there's also one of the Read me down here as well.
Yeah we can take a look at say getting started and you'll see a page like this.
So make sure you come to deployment and there's going to be an installation guide on how to get started.
Now I've got to be honest with you my very frank notes on ingress engine X the documentation page here
is not the best in the world.
It turns out that once you start doing some more advanced stuff there's just it's just a little bit
hard to interpret this documentation sometimes.
I'm just gonna leave it there.
If you start to read this stuff and you're getting a little bit confused you are not alone at all.
You can take a look at the installation guide you're going to see a couple of notes on here.
These notes change all the time.
So if you see a different set of notes an eye that is totally ok whenever you get started with ingress
engine X there's going to be what is called a mandatory command up here.
So if we want to use ingress engine X inside of our cluster we have to run this mandatory command no
matter what.
After that there are going to be a series of provider specific commands.
So if you're using Docker for Mac for example or Docker for windows you will run this additional command
right here.
If you're using many cube you'll run that command right there and there's a set of additional commands
depending upon your provider on here as well rather than just taking these commands and executing them
inside of our terminal.
I want to really understand what these commands are doing.
I'm going to copy one right here and I'm going to go to my code editor really quickly just open up an
empty page and paste that command in to take a look at this command that they're asking us to run it
is QC DL apply dash F and then we are providing a U or L you're L that you would see right here is to
a Yemen file.
So this entire installation command is very similar to these same commands we've already been running
recently just taking a config file and throwing it into our cluster the exact same thing you and I have
been doing throughout this entire Cuban entity section.
I'm going to take this Your L and open it up inside of my browser you're going to see that when you
get start with Cuban eddies there are going to be a lot of add ons other packages you want to use inside
your cluster and a lot of them are going to be installed or added in by doing the same kind of cubes
GTL apply dash F and then some you're out to a config file.
I highly recommend that before you just take that entire command and throw it into your terminal.
I really recommend you take a look at that config file and understand what you are getting so in this
case we can see what is going to happen if we run that command.
This is the config file these are the changes that will be implemented inside of our cluster you'll
see that there are a couple of different config sections in here that look somewhat similar to the ones
that we've already been writing.
The big difference is that they are creating different kinds of objects than the ones we've been looking
at so far.
So this one create something called a namespace.
We've got a config map a service account cluster all lot of different kinds of objects beyond what we've
looked at so far.
But most importantly I'm going to scroll down a little bit here is the bottom those scrolls grow scroll
and down here you're going to see that there is a can pick section for a deployment.
Well we know what a deployment is a deployment something that creates and manages a set of pods.
Take a look closely at this thing and you'll notice that it's creating something that is called an ingress
and connects ingress controller.
So this ingress controller thing right here is essentially what we were just discussing back inside
this diagram.
So it's this ingress controller that's going to have a set of routing rules inside of it and it's going
to make sure that incoming traffic gets sent off to inappropriate pod.
That was the first config file that the installation guide was asking us to run.
That was the mandatory command.
I now want to take a look at the other config file that we're being asked to run if you're using Docker
for Mac.
It's going to take just that config file to you all right there.
And again paste it into my browser but this is what we get when we run the docker for macro Docker for
Windows specific installation.
We get just this very simple config file right here and take a look at what it creates.
It makes a service of type load balancer.
So this is the other part of what we just saw inside this diagram.
This is the thing that's going to somehow provision an outside load balancer and it's going to somehow
get traffic in to our cluster specifically at that ingress controller thing so between these two different
can pick files that we just looked at.
We're essentially implementing this diagram that you see right here OK.
So now that we've got a better idea of what these different installation commands are doing.
Let's go ahead and run them so no matter what you're going to make sure that you now run this mandatory
command right here.
So we're going to copy that link or commands will then go back over to our terminal pasted in and run
it well then see a bunch of stuff being created.
Now for me I see a lot of stuff being unchanged because I've already got engine X ingress controller
installed inside my cluster I'll then go back over and because I am using Docker for Mac or if you are
using Docker for windows you're still going to use the same command right here.
I'm going to copy that command and run that one as well.
And I see unchanged but you're probably gonna see something that says service created or what have you.
And then of course if you're using a mini cube instead you will follow these directions right here.
You do not have to do the for development.
That's just if you are developing ingress engine X. If you are a mini cube you'll just do standard usage
OK.
That is it for the initial setup.
Now we've added these things into our cluster but we have not yet set up any routing rules or anything
like that around our ingress controller.
So we still have a little bit of work to do.
Let's take a pause right here in the next video we'll start to understand how we can tell the ingress
controller how to route traffic off to our different set of pods.