In this post I describe some of the fundamental concepts that you'll need to be familiar with to deploy ASP.NET Core applications to Kubernetes. If there's anything that you don't agree with or looks incorrect, please do let me know in the comments! 🙂
Deploy asp.net application with docker and kubernetes series#
Note that although production-level support for Windows has been around for a while I'm only going to be considering Linux hosts for this series.Īnother 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. Scott Hanselman has also a recent 101 introduction to containers. I also have many other posts on my blog about using Docker with ASP.NET Core. NET developers, as well as multiple talks and videos on the subject. Steve Gordon has an excellent blog series on Docker for. This series does not focus on using Docker with ASP.NET Core in general. I won't touch on Project Tye in this series, though I'm sure I'll blog about it soon!
Since then Project Tye has arisen as a promising new way to deploy ASP.NET Core apps to Kubernetes. Important note: I started writing this blog series about a year ago, but it's been delayed for various reasons (ahem, procrastination).
Instead I'm going to focus on the app-developer's side, taking an application and deploying it to an existing cluster. 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. In this series I'll cover a variety of topics and things I've learned in deploying applications to Kubernetes. This post is the first in a series on deploying ASP.NET Core applications to Kubernetes.
0 kommentar(er)
