So as we need access to our Cuban and export from outside, we're going to configure interests role
for our Cubana service.
So let's go back to our cluster.
Let's clear this up and let's do keep still get service in here.
You see, we have a Cubana service, which is of cluster IP type.
This is basically an internal service.
It has no public IP address or no public or external access compared to a load balancer type of ingress
controller.
That is basically an external service type.
And here you see the difference is also that it has the cluster internal IP address, but it also has
an external IP address.
And this IP address here that you see is actually the same one as you saw right here.
So this is the same external IP address that the node balancer has, and this will be the entry point
in our cluster.
So in order to make this internal service accessible, we are going to create an ingress component which
will contain a rule for forwarding the request, come and get this IP address to on internal service
and then Kibwana application itself.
So let's go ahead and do that.
Let's create an ingress configuration file.
I already have an ingress file.
So as you see, it's a pretty simple structure.
We have a kind ingress and egress component and in the specification we have a list of rules.
So basically what this one rule here does is it tells Ingress Controller whenever a request comes in
directed to this specific host.
And we're going to specify the value here.
So please direct that request at this host and route path to a backend, which is an internal service.
And the service name is Kibwana honor service name in the port is part of the service, which is this
one right here.
So now they said the value of host host value cannot be an IP address.
It has to be a valid domain address.
In order to get that, we're going to go back to node, to our node balancer.
And if I click inside, along with the IP address here, I have the hostname of the node balancer.
So this is going to be our host value.
So whenever I type this, you're telling the browser request will enter my cluster because this yero
here maps to the IP address of the cluster node balancer or ingress controller, and that's why the
request will land in the cluster.
And once the request is there, in which controller will look at this role and it will see that the
request needs to be forwarded to keep honor service at Port five thousand six hundred one.
So, of course, when you have your own domain name, like my EB dot com or whatever you can configure
in the DNS settings, the forwarding to this or mapping of your domain name to this IP address so that
people can access the internal service using your domain name.
But we're going to use the one provided out of the box by LYNARD.
And now this creates or apply this ingress.
So from here it's through keeps the teleplay ingress and I can check the ingress components.
Using CubeSat, he'll get ingress.
And here I see the details, the address or the IP address of.
These hostname will also appear here.
So now let's actually copy that euro.
And enter it in the browser.
And here you see our Caivano dashboard also in a realistic case, you would have your domain name secure,
so you would want connection to always be through HTP.
S protocol.
And that's also pretty easy to configure using ingress.
So basically, provided that you have your domain names, secure certificate already, you can also
easily configure that in ingress using an attribute called Telx.
So basically you create a secret containing your certificate and then you reference it here.
So you have the hosts here and on the second line you have the secret name.
So it's pretty easy to do.
Important to note that these HTP is not actually the one that you see here.
This is the second level.
So basically the request coming from the browser to our host is by default, HTP.
So it's not configured here.
And this is basically forwarding between the Ingress controller and the service.
So internal request forwarding is through HTP protocol.
So not to confuse those two.