From the course: Complete Guide to Dapr for .NET and Azure Developers: Building and Managing Microservices

Unlock this course with a free trial

Join today to access over 24,900 courses taught by industry experts.

Exposing the services in the Kubernetes cluster

Exposing the services in the Kubernetes cluster

From the course: Complete Guide to Dapr for .NET and Azure Developers: Building and Managing Microservices

Start my 1-month free trial Buy for my team

Exposing the services in the Kubernetes cluster

“

- [Instructor] Once the nginx ingress controller is installed, we'll expose the Wisdom Pet Medicine microservices to the outside world. For this, I've already created a folder named Ingresses, and inside this folder, we can find some JAMA files containing the configurations for these services. For example, let's open hospital, and we can see that this is an ingress resource. And here under paths, we can see that this is exposing hospital as the endpoint. In other words, this is going to be the public endpoint, and this is going to be connected to the hospital service that we deployed before. Similarly, we have pet api with pet as the endpoint, petaggregator, rescue, and finally, rescuequery. I also created apply-ingresses, so we can execute kubectl apply with all of those five files very easily. And finally, kubectl delete for testing purposes. Okay, let's open up the terminal. And here let's just execute apply-ingresses. So you can see that this is returning unchanged. And again…

Contents