Daprizing ingress controllers

Let’s recap the current stage of our deployment of the Biscotti Brutti Ma Buoni backend solution to Kubernetes: after we followed all the steps in Chapter 9, Deployment to Kubernetes, we have the Dapr components and applications properly configured, and external calls can reach the APIs of some of our services.

Considering the approach that we followed in exposing the Dapr applications so far, how different has it been from exposing any other generic ASP.NET APIs? Not different at all: taking Dapr out of the picture, we still had to deal with Kubernetes-specific concepts such as services and then set these services as the backend of ingress rules using the NGINX Ingress Controller (IC) we set up.

As you might already guess from the direction the chapter is aiming toward, there are other approaches to inject Dapr into any existing application leveraging HTTP routes and, as an extension of this, an NGINX IC. We are now going to Daprize the NGINX...