First published on MSDN on Oct 24, 2017
Authored by Mahesh Kshirsagar (AzureCAT). Reviewed by Brendon Burns (Distinguished Engineer, R&D Compute Dev), Wasim Bloch (AzureCAT), and Kimmo Forss (AzureCAT). Edited by Ed Price (AzureCAT patterns & practices).
This material has been added to a full eBook, Kubernetes Objects on Microsoft Azure.
Interest in Kubernetes as a container orchestrator is growing rapidly. The capabilities it offers are very exhaustive. As more and more enterprises adopt a containers/microservices-based architecture, a container orchestrator has become necessary in order to provide wide-ranging options to manage containerized workloads. While Docker has provided an excellent ecosystem to get started with containers, Kubernetes has really pushed the boundaries of this ecosystem. It provides many options to manage containerized workloads. However, these many options can also overwhelm beginners easily. This blog series is an attempt to demystify Kubernetes by focusing on a real-life scenario of deploying a basic multitiered application using pods and controllers. Along the path, I will include some of the decision criteria for Kubernetes. This includes helping determine the right Kubernetes objects for running workloads in Azure. I will illustrate various deployment options by deploying a 2-tier workload on Kubernetes. The concepts can be easily extended to multitier architecture implementations. The workload discussed in this blog series consists of a front-end web application running ASP.Net Core 1.0 (with little bit of SignalR). The backend consists of a SQL Server container running on Linux. The blog series includes the following posts:
The source code used is available at the following GitHub locations:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.