Atmosera

Kubernetes, Dapr, and Azure Identity Example – Part I

Introduction

In this series of posts, we will walk you through setting up a static website (SPA), user authentication using Azure Active Directory (AAD), and simple authenticated services, all within a Kubernetes cluster using DAPR services.

The source code is located at https://github.com/dfbaskin/azure-and-dapr-identity-example. There are separate branches related to the different posts.

This example was built on my Windows 10 development machine, but should also work for other environments. The requirements for building this example on your local machine are:

Docker and Kubernetes – Docker is used to build the container images for deployment into the Kubernetes cluster.
Helm – To install the NGINX Ingress controller.
Powershell – Scripts included in the example are written in Powershell, which is available cross-platform. The scripts, however, are all fairly simple and could easily be migrated to the scripting language of your choice if so desired.
.NET Core v5 SDK – The Web API is created using C# and the .NET runtime.
Node JS – The front end application is written using React and TypeScript and Node is used to build it.

Microservices

Kubernetes works by examining the desired configuration of services and other resources (usually declared in text .yaml files) and then working to make changes to a deployment environment to match this configuration. This is useful when using a microservices-based architecture where many smaller, more independent services cooperate to execute the overall application functionality.

DAPR provides additional services useful to a microservices architecture. Using a sidecar architecture, DAPR provides an abstraction on top of important operations used by microservices. This helps developers to focus more on coding business value rather than dealing with infrastructure.

The example application, in its final form, implements the following configuration:

The first few posts describe setting up components within Kubernetes. After that, we’ll incorporate DAPR functionality.

Setting up Local TLS Certificate

Because this example will be using with the https protocol and TLS termination, it is important to set up our development environment so that browsers can recognize the certificates used by the example application.

In the repository, there is a Powershell script, tools/certs/add-local-testing-cert.ps1, that can be used to generate a certificate to be used locally. This certificate will be used by the example application, but it must also be inserted into your root certificate store so that running a browser on your machine will recognize and accept the certificate as valid.

The cert is mapped to the domain, testing.local. So this domain will also need to be added to your hosts file to ensure that the local machine maps to this domain name: