kind

The nodes here are fake, they won't actually run your software. For CI/CD clusters I would recommend kind (https://github.com/kubernetes-sigs/kind).

kind (kubernetes inside docker) does this by building a specialized container that includes and uses systemd as the entrypoint: https://github.com/kubernetes-sigs/kind/blob/main/images/bas... You could run this as a standalone container docker run --rm -d --name my-node --volume=/lib/modules:/lib/modules:ro --volume=/var --volume=/kind --privileged docker.io/kindest/node:v1.25.3 then exec in and use it like a vm. it comes with containerd installed and running but you could also install docker docker exec -it my-node bash

From the kind readme[1]... > kind was primarily designed for testing Kubernetes itself, but may be used for local development or CI. minikube was designed for those who want a local kubernetes environment for development. It didn't work well for testing Kubernetes itself which led to kind. They had two different, though slightly overlapping, goals. [1] https://github.com/kubernetes-sigs/kind

FWIW: That project was started as an internal tool with a playful acronym and then went from obscure to well-known enough to making renaming a somewhat regrettable concept rather quickly just due to momentum. I think we'd have named it differently if we were aiming for widespread usage :-) We had no reason to worry about making it popular, the effort was staffed to improve developing Kubernetes itself. As for googling, I recommend adding keywords like "kubernetes" and for issues searching the repo itself or reaching out to the community for help https://github.com/kubernetes-sigs/kind#community That tool is written in "Go" which also somewhat famously doesn't search well without changing your terms up a bit.

Not quite fake: but this might be close enough? https://github.com/kubernetes-sigs/kind Alternatively you could create a CRI plugin that does what you want. https://github.com/kubernetes/kubernetes/blob/242a97307b3407...

You can! KinD[0] is a project to do just that, although production workloads are an explicit non-goal. [0]: https://github.com/kubernetes-sigs/kind

“kind” is a example in my day to day, how do I run an ephemeral kube cluster in ci to deploy and test my app against without dind/kind? I want N clusters running on 1 host to support many CI jobs. https://github.com/kubernetes-sigs/kind https://github.com/bsycorp/kind

I've not tried it but I don't think minikube would work inside WSL as it needs a VM layer (I suppose technically it could with nested virtualization). TBH for throwaway Kubernetes cluster in WSL, I'd recommend kind (https://github.com/kubernetes-sigs/kind) it works just fine with WSL/Docker for Windows.

There are a lot of projects these days that aim to use Kubernetes as a docker-compose environment. I personally use http://skaffold.dev/ with either a local Kubernetes cluster built with https://github.com/rancher/k3d or https://github.com/kubernetes-sigs/kind. I think there's a very easy argument to be made that says that running K8s locally is overkill, but what I will say is that if you run your applications locally in K8s, that's one step closer to having your local environment mirror the production environment. Couple that with things like running https://github.com/localstack/localstack locally and you get even closer.

Author here. At the last two companies I've worked at we really needed—and didn't have—a solution for spinning up throwaway Kubernetes clusters that we could, for example, easily and reliably test our deployment process in. Kind (https://github.com/kubernetes-sigs/kind) does a pretty good job of addressing that but requires setting up a bunch of infrastructure that needs to be maintained and doesn't easily work in a containerised CI environment. Krucible is an attempt at solving those problems by allowing you to spin up Kubernetes clusters via an API quickly and affordably. Krucible is still in its early stages but I wanted to show it to the community and get feedback. Happy to answer any questions.

loses all the data because you have to start a new cluster? The data should be persisted... If this refers to https://github.com/kubernetes-sigs/kind/issues/148, the good news is that we're most of the way there and I'm going back to work on this now, ideally out in a v0.8 in the next week or so.

Sure. I cheated. I specifically didn't feel like setting up extraPortMappings (https://github.com/kubernetes-sigs/kind/issues/808), and then create an ingress controller (https://kind.sigs.k8s.io/docs/user/ingress/). Not difficult, just not turnkey availability like the other two.

unfortunately not. figuring this out would make a lot of people happy, but it doesn't rank highly for our current use cases versus other work. https://github.com/kubernetes-sigs/kind/issues/763