Kubernetes now helps Windows machines as employee nodes. You can spin up a hybrid cluster and feature Windows workloads jogging in Windows pods, speaking to Linux workloads running in Linux pods.

TL;DR 

I have scripted all of the setup steps to create a three-node hybrid cluster, you will find them with commands at six-eyed/k8s-win

Now you could take older .NET Framework apps and run them in Kubernetes, which is going that will help you circulate them to the cloud and modernize the architecture.

You start by going for walks your antique monolithic app in a Windows container, then you step by step break functions out and run them in .NET Core on Linux containers. for more info Kubernetes Online Training

Organizations were taking that method with Docker Swarm for a few years now. I cowl it in my ebook Docker on Windows and in my Docker Windows Workshop. It's a completely successful manner to do migrations - breaking up monoliths to get the benefits of cloud-native architecture, without a full-on rewrite project.

Kubernetes on Windows: Cluster Options

Now you can do those migrations with Kubernetes, which will open up something interesting new patterns, and the option of running containerized Windows workloads in a managed Kubernetes service in the cloud.

     Cautionary Notes

  1. Windows help in Kubernetes is still quite new. The function went GA in Kubernetes 1.14, and the contemporary release is best 1.15. There are some things you need to be conscious of:
  2. cloud guide is in the early stages. You can spin up a hybrid Windows/Linux Kubernetes cluster in AKS, but right now it's in preview.
  3. Core components are in beta. Pod networking is a separate thing in Kubernetes, and the principle options - Calico and Flannel handiest have beta support for Windows nodes.
  4. Windows Server 2019 is the minimum version that helps Kubernetes. learn Kubernetes course from experts
  5. The developer experience isn't always optimal, mainly if you are used to using Docker Desktop. You can run Windows containers natively on Windows 10, and even run a single-node Docker Swarm on your computer to do stack deployments. Kubernetes needs a Linux grasp node, so your dev environment is going to be a couple of VMs.
  6. Kubernetes is complicated. It has a wider feature set than Docker Swarm but the cost of all the features is complexity. Application manifests in Kubernetes are about 4X the size of equivalent Docker Compose files, and there are way more abstractions between the entry point to your app and the container which ultimately does the work. Kubernetes has a master-worker architecture for the cluster. The control plane runs on the master, and right now those components are Linux-only. You can't have an all-Windows Kubernetes cluster. Your infrastructure setup will be one or more Linux masters, one or more Windows workers, and one or more Linux workers:
  7. For a development environment you can break out with one Linux grasp and one Windows worker, going for walks any Linux workloads at the grasp, but a further Linux employee is preferred. learn Kubernetes training helps you more to learn more techniques from industry experts.     You can spin up a managed Kubernetes cluster in the cloud. Azure and AWS both offer Windows nodes in preview for their Kubernetes services:1.Microsoft's AKS Windows preview
    2. Amazon's EKS Windows preview
    Kubernetes has a pluggable structure for core components like networking and DNS. The cloud services contend with all that for you, however, if you want to get deeper and check out the setup for yourself, you may build a nearby hybrid cluster with some VMs.
    Tasks for putting in place a neighborhood cluster
    There's already pretty good documentation on a way to set up a neighborhood Kubernetes cluster with Windows nodes, however, there may be a lot of guide steps. This puts up walks through the set up the usage of scripts that automate mile as possible.

The original resources are: 

  • initialize the Kubernetes master
  • install pod networking, using Flannel
  • add the Windows worker node
  • add the Linux worker node