Introduction This is the first part in our (at least) two parts describing how to get started with a hybrid Docker Swarm Mode cluster. In this first part, we will focus on deploying a hybrid cluster on Azure. Now, you can create yourself a hybrid cluster within any private network where you have a Windows Server 2016 with Containers and a Linux machine - it can be locally, with VirtualBox, Hyper-V or VMWare, or it can be on your cloud provider of choice.
Table of Contents Introduction Deploying a Kubernetes cluster on Azure Container Service Installing and configuring the Kubernetes CLI Deploying a Jenkins master on the cluster Configuring Jenkins to work with Kubernetes Configuring Jenkins to dinamically spawn agents (Docker containers) for builds What is happening behind the scenes? The Docker image for the slaves Conclusion Next Steps Feedback Introduction If you already know how to deploy a Kubernetes cluster, please jump ahead to creating the Jenkins service.
UPDATE - February 2017 This article describes the latest development of websocket-manager and how to use it in your application. While the general aspects provided in this article about creating a websockets middleware for Asp .Net Core are still valid, the specific information about the websocket-manager project have changed, since I updated a lot of parts. The version of the project described in this article can still be found in the blog-article branch on GitHub.
Introduction In this article, we will take the simplest ASP.NET Core application, run it with Docker locally, then create Continuous Integration and Continuous Deployment flows using a GitHub repository, Docker Cloud and an Azure virtual machine that will act as a node for Docker Cloud. If you don’t want to create an ASP.NET Core application but are interested in the CI/CD workflow, or if you already have a GitHub repository with a complete application with a Dockerfile, you might want to skip to the part we start creating the CI/CD workflow.