![]() ![]() The one we need is the “ nf”, which contains the configuration for our newly created local cluster (and set Kubectl to use it). vagrant/provisioners/ansible/inventory/artifacts vagrant folder in order to access it: cd. When the process completes, and the cluster is successfully created, we could use the configuration automatically injected in the artifacts folder. In addition, the Vagrantfile contains all the necessary specifications for the spawned VMs (so it allows us to configure the network, VM’s image, its properties, etc…). Inner YAML files allow customization of whatever is desired for the planned cluster. When invoked without customizations, it is grabbing a sample configuration that is located in /inventory/sample. This command will spawn the VMs, install Kubernetes on them, and configure the networking. Once everything has been correctly installed, we can start Vagrant: vagrant up Let’s clone the official repo: git clone Īfterward, moving into the cloned repo, we can start the installation of the tools required: cd kubespray & pip3 install -r requirements.txt # OR cd kubespray & pip install -r requirements.txt What is supposed to be already installed: It comes with Ansible playbooks (deploy, upgrade, utils and extras) and with plenty of tests. ![]() There are few open-source solutions to achieve the task of deploying Production-Ready Kubernetes clusters, but I selected Kubespray. ![]() For development purposes, it would be great to have a Kubernetes Production Cluster locally, and with this article, I am going through the basic setup in order to start using a good one. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |