Exposing Dapr applications to external clients

At this stage of deploying the Biscotti Brutti Ma Buoni backend solution to Kubernetes, we have all the Dapr components and applications properly configured. However, without the proper configurations, no external calls can reach any of our service APIs.

Our objective is to expose the ASP.NET endpoints of the Dapr applications, starting with order-service, so that we can invoke the /order API method from our client machine. The following diagram shows what we are trying to achieve:

Figure 9.6 – The main components of a Kubernetes deployment

In the preceding diagram, the main Dapr services are depicted in Kubernetes alongside our Dapr applications. They are represented as Pods containing the ASP.NET container, along with the service code and the Dapr sidecar.

We need to configure our Kubernetes cluster with an ingress controller (IC). For this, we can use NGINX. A detailed step-by-step configuration...