Have you tried setting up a Windows Kubernetes workload cluster and found it hard? Cluster API for Oracle Cloud Infrastructure (CAPOCI) has you covered! You can now easily launch a Windows workload cluster in OCI.
The ability to run different kinds of workloads is a big appeal of Kubernetes. We’ve found that getting Windows workloads up and running isn’t easy. We’ve spent time making this process easier at OCI with CAPOCI. Although the control plane can only run on Linux, with some limitations you can provision worker nodes to run either Windows or Linux in your workload cluster using CAPOCI.
We know that rewriting all projects from scratch as new technologies emerge isn’t feasible. We want to provide a path forward for Windows systems to run on Kubernetes at OCI, allowing our customers to adopt Kubernetes for all its great benefits, without requiring a rewrite of your software.
Using CAPOCI, you can unlock the following advantages that enhance your overall Kubernetes experience:
For a guide on how to set up a Windows workload cluster, see our CAPOCI book. It provides steps to get up and running and an advanced section on how to set up heterogeneous clusters, if you want to also run Linux in your workload cluster.
Having a Windows workload cluster up with little effort is amazing! The ability to have both Windows and Linux worker nodes in one cluster is the cherry on top of the Kubernetes cake (or pie)!
This configuration does add some complexity in cluster management, like ensuring that the correct workloads are scheduled for the appropriate OS. However, it also provides developer flexibility, allowing the use of a single cluster and pick the best platform for platform-specific applications. You get workload matching to the appropriate operating systems and intra-cluster communication. Finally, with a unified control plane, you get the benefit of resource efficiency and easier observability of your entire infrastructure.
For more information, see the following resources:
* CAPOCI open source repo
* Cluster API documentation
* CAPOCI documentation
* CAPOCI Slack channel
Previous Post
Next Post