This is the very high level overview of the All-in-One Kubernetes Playground. For more details on how to use the playground, please refer to “The All-in-One Kubernetes Playground Usage Guide” or “All-in-One K8S Playground中文使用指南”.
This playground includes a set of shell scripts that can help you launch a single- or multi-node Kubernetes cluster on a single machine in minutes in a repeatable manner.
The below Kubernetes distributions are supported by this playground:
The below applications are deployed along with this playground for you to evaluate and use:
The below Kubernetes-related command line tools are integrated with this playground for you to evaluate and use:
The playground runs a set of private registries that can be used to mimic below public container regiestries:
By storing all images into private registries, it can boost your playground launch dramatically fast. You can even launch the playground without network connectivity! Furthermore, if you share the registries with your teammates, they all can benefit from that.
For more details, please refer to “Can I launch the playground without network?”, “Can I share private registries with others?”.
The below OSs are supported by this playground:
The playground provides a Vagrant Box out of the box that can be launched by a single line of command. Meanwhile, it can also be launched on your host machine directly.
For more details, please refer to “How to launch the playground?”.
To use the playground in command line, you can login from normal terminal, or use web terminal that allows you to log in to the playground in web browser.
For more details, please refer to “How to access the playground?”.
You can do a lot of things by using the built-in “Launch Utility”. You can even use the “Launch Utility” to create snapshot for the current running cluster, then restore from it later very quickly.
For more details, please refer to “What else can I do with the playground?”, “Restore cluster from snapshot”, and the “Launch Utility Usage Guide”.
You can customize the playground before or after its launch in many aspects to meet your very specific requirement, e.g. to change the Kubernetes distribution, Kubernetes version, the number of cluster nodes, the applications to be installed, and the Docker images to be pulled.
For more details, please refer to “Can I customize the playground?”, “What if images are changed?”.