In this series I cover a variety of topics and things I've learned in deploying ASP.NET Core applications to Kubernetes. I'm not an expert on Kubernetes by any means, so I'm not going to go deep into a lot of the technical aspects, or describe setting up a Kubernetes cluster. Instead I'm going to focus on the app-developer's side, taking an application and deploying it to an existing cluster.
This series does not focus on using Docker with ASP.NET Core in general. Steve Gordon has an excellent blog series on Docker for .NET developers, as well as multiple talks and videos on the subject. I also have many other posts on my blog about using Docker with ASP.NET Core. Scott Hanselman has also a recent 101 introduction to containers. Note that although production-level support for Windows was announced recently, I'm only going to be considering Linux hosts for this series.
Another important point is that I don't consider myself a Kubernetes expert by any means! The approaches I describe in this series are very much taken from my own experience of deploying ASP.NET Core applications to a Kubernetes cluster. If there's anything that you don't agree with or looks incorrect, please do let me know in the comments! 🙂
You may also be interested in Project Tye. This is a (currently) experimental tool for .NET projects "that makes developing, testing, and deploying microservices and distributed applications easier". It aims to hide a lot of the complexities involved in Kubernetes from you. Nevertheless, I think a lot of the topics I cover in this series are either good background to have, or are issues that apply whether you're using Tye or deploying "natively" to Kubernetes.