# LoadBalancer Services using Kubernetes in Docker (kind) DevFeed: [LoadBalancer Services using Kubernetes in Docker (kind)]() Original publisher: [Read original article]() Author: Owain Williams Published: 2022-09-20T20:08:29Z Content type: tutorial Language: en Sources: [Groupon Engineering -- Medium]() Topics: [Kubernetes](), [Docker](), [Orchestration](), [container](), [Development]() Tags: [container](), [development](), [docker](), [ingress](), [kind](), [kubernetes](), [load-balancer](), [orchestration]() ## AI overview This tutorial introduces Kubernetes and compares local options for experimenting with it, including Docker's single-node cluster, minikube, and kind. It explains that kind runs cluster nodes in containers and supports multi-node clusters, but the supplied text ends during cluster creation. ## Source excerpt Kubernetes is a very popular open-source container orchestration system for deploying, scaling, and updating your software, as well as automatically recovering from failures. If your code can be packaged into a container, e.g. via Docker, then it can run on Kubernetes, or k8s for short (which is sometimes pronounced 'kates' and refers to the 8 letters between the first and last letter). You can read more about it on the Kubernetes Documentation page. You can run a Kubernetes cluster in your own data centre as well as on many of the popular cloud providers, for example there's the Amazon Elastic Kubernetes Service (EKS), the Azure Kubernetes Service (AKS), and the Google Kubernetes Engine (GKE) to name a few. You can also create clusters that span your data centre and a cloud provider or even span multiple cloud providers. Here at Groupon, we have several Kubernetes clusters around the world hosted on both EKS and GKE. This is great for production, or even as a staging cluster, or shared development environment. But what if you just want to try it out and see what all the hype is about before you spend money on a new cluster? The good news is there are several options, if you've installed Docker you can enable a single-node Kubernetes cluster simply by ticking the option in the Docker settings. However, you will be tied to the version of Kubernetes that ships with your version of Docker. Another option is minikube which allows you to run specific versions of Kubernetes, or even multiple clusters with different versions. However, you'll still only be able to run single-node clusters. A single-node cluster is probably fine, and could well be all you ever need. But you won't be able to experiment with pods running on different nodes, and the various like-live scenarios that enable, for example using hostPath volumes with different files on each node. Before you fire up a load of VMs and try installing Kubernetes The Hard Way there is one more option, kind, which stands