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.

Preparing and applying the component files in the Kubernetes cluster

Preparing and applying the component files 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

Preparing and applying the component files in the Kubernetes cluster

“

- [Instructor] Up to now, we've been using the local Redis container in many of the components, but that will no longer be the case when we deploy the application in the Kubernetes cluster, of course. Since we're going to deploy a Redis container in Kubernetes, we need to replace localhost with the container's name. That's why I'm using Redis, as you can see here, or here. Also, there are some missing version elements that we need to add. That's the case here, for example, in the wisdom-configstore.yaml file. You can see that I included version v1. And also here, version v1. Regarding the Azure Key Vault authentication, I showed you how to use a certificate file and an Azure client secret. For this deployment I'm going to use the latter. It might be a good idea to store the Azure client secret in the Kubernetes SecretStore. So, let's do that. I'm going to create a new SecretStore named wisdomsecret, and I'm going to store this Azure client secret with the value that we had before here…

Contents