KUBERNETES.md

Deploying on Kubernetes

I've tested the included YAML files with Azure Kubernetes Service (AKS). They should work with little or no modification in other Kubernetes environments like GKE or EKS.

I've included two options to deploy the application in Kubernetes and expose the app to the internet:

• Using a LoadBalancer service: This will expose a dedicated IP address for the service on AKS's Azure Load Balancer.
• Using an Ingress: This requires you to install an ingress controller before deploying the app, and exposes this app on dedicated FQDN. You can use Helm to install an Nginx ingress controller on AKS. Make sure to set your FQDN in ingress.yaml.

Deployment

Please make sure to specify a valid MongoDB connection string as secret ConnectionStrings__DefaultConnection in secrets.yaml. Note that the Kubernetes manifests do not include a MongoDB deployment. You will either need to have a running MongoDB instance outside of your Kubernetes cluster, or deploy MongoDB to your cluster.

If you want to use Application Insights, set ApplicationInsights__InstrumentationKey as well.

Next, open a terminal window with a shell that is configured to connect to your Kubernetes cluster and run the following commands depending on how you want to expose the BookLibrary application.

PowerShell

$ cd \path\to\BookLibrary-NetCore

bash

$ cd /path/to/BookLibrary-NetCore

LoadBalancer

From the solution's root folder, run

$ kubectl apply -f manifests/configmap.yaml
$ kubectl apply -f manifests/secrets.yaml
$ kubectl apply -f manifests/deployment-loadbalancer.yaml

to deploy the LoadBalancer version.
You can access the app at http://<LoadBalancer-IP>/.

Ingress

From the solution's root folder, run

$ kubectl apply -f manifests/configmap.yaml
$ kubectl apply -f manifests/secrets.yaml
$ kubectl apply -f manifests/deployment-clusterip.yaml
$ kubectl apply -f manifests/ingress.yaml

to deploy the Ingress version.
You can access the app at http://<FQDN>/.