Containers

You may well be aware of technology such as Helm and the creation of Helm Charts to manage applications on Kubernetes. It’s a great solution if you want your container to be consumed by the general public, but what if you want a reusable YAML file to deploy your services internally. We can easily have a template YAML file stored in a Git repository as part of Azure DevOps that can be used in our release pipelines and change placeholders based on variables set in our pipeline....

In this post, we take a look at how to make sure you .NET Core Web API containers work well in auto-scalaing scenarios on Azure Kubernetes Service. When you first access a newly released .NET Core Web API, even locally, does not have to be in a container, you will notice the first request is slow. You can see this with the following output, it’s just from a brand new scaffolded project using the ....

In order to test locally, you will also need Docker Desktop installed on your machine. This should be done before you create your Visual Studio project below. To start, we need some application code. Using Visual Studio, create a new project, for this walkthrough, I will be using an ASP.NET Core Web Application, I will also be publishing my source code in GitHub, this repository is already cloned locally to my machine....