So at this point, we deployed our
Kubernetes-managed application to this EKS cluster.
We got two different kinds of pods running in there.
Two different kinds of deployments
and therefore also different services attached to them.
One of the services, the auth-service is clustered internal.
The other service uses a load balancer,
which was created automatically by AWS as you saw.
We're letting these services communicate with each other,
with help off this automatic domain name,
which has generated.
And we're using a volume, we're using an EFS volume,
using that CSI volume type Kubernetes offers.
And with that we got all the core topics,
which I had a close look in detail over the last sections
applied in action on this real cluster here hosted by AWS.
Now it's time to practice.
And for that, attached, you find a brand new
auth-api, tasks-api, and users-api folder in the attachment,
because I made some code changes in all these apis.
And I added the brand new tasks-api.
And your task will now be to add this task-api
to the Kubernetes cluster.
So start from scratch there, add a new deployment
and a new service.
The tasks-api should be reachable from the outside world.
It should not be clustered internal,
but ensure that the tasks-api is able to talk
to the auth-api.
And you can use the docker-compose file,
which you find the attached as well,
as inspiration on how to set up your tasks deployment.
Here you see the environment variables
which are used in the tasks code,
and of course you should provide these variables
with appropriate values
for your Kubernetes configuration as well.
In addition, I also want to highlight that I had a typo
in the auth-api address environment variable
in the past here in the users-api.
And I fixed that typo now in the users-api code.
So you should also fix it in your docker-compose.yaml file.
And in your users.yaml file
in the Kubernetes folder.
There, where we provide the auth-api address
environment variable make sure it's written like this,
with two S at the end,
not with three as I accidentally had before.
One important note about this challenge by the way,
as I mentioned, it's not just about the tasks-api folder.
I also tweaked some code in users-api and auth-api.
So make sure you also rebuild these images
and you push the updated images to docker hub,
and you then replace your current deployments
with the new ones,
so that all the code changes are picked up.
But with that, that's your challenge.
That's a challenge by me for you.
Add this tasks-api as a new deployment
to this existing Kubernetes EKS cluster.
In the next lecture, we're going to do it together.