Please see Kublr-in-a-Box for new installation guide.
Kublr-in-a-Box is a simple and convenient demo version of Kublr, running in Vagrant, that allows you set-up Kubernetes clusters. You can also use Kublr-in-a-Box to install a non-production licensed version of the full Kublr Platform.
The virtual machine should start up and ask for an External IP:
==> default: Running provisioner: shell... Virtual machine needs know you external IP for the machine in order to do proper installation of baremetal clusters. External IP:
Please provide the IP address of your local machine in your local network, so your on-premise nodes are able to connect to this IP address while deploying a cluster.
Wait while the Kublr-in-a-Box virtual machine starts up. It should end with the following output:
... default: Kubectl config file is available in current directory. default: default: The following links are available: default: Kublr HTTPS: https://localhost:9443/ admin / kublrbox default: Kublr HTTP: http://localhost:9080/ admin / kublrbox default: Keycloak HTTPS: https://localhost:9443/auth/admin/kublr-ui/console admin / kublrbox default: Keycloak HTTP: http://localhost:9080/auth/admin/kublr-ui/console admin / kublrbox default: K8s: https://localhost:7443/api/v1/namespaces/kube-system/services/kubernetes-dashboard/proxy/#!/pod?namespace=kublr
Open your favorite browser and navigate to http://localhost:9080/ Use following credentials to access Kublr-in-a-Box UI:
Now you are good to go with Kublr-in-a-Box.
If you no longer need Kublr-in-a-Box, you can clean up resources:
Open terminal with the current directory pointing to the downloaded Vagrantfile file and launch the following commands:
vagrant destroy -f || rm -rf Vagrantfile ==> default: Forcing shutdown of VM... ==> default: Destroying VM and associated drives...
To remove installed Kublr Vagrant boxes:
Print the list of all installed Kublr boxes:
vagrant box list | grep kublr kublr-321 (virtualbox, 0) kublr-322 (virtualbox, 0)
Run the removal command for each box you want to remove:
vagrant box remove kublr-321 Removing box 'kublr-321' (v0) with provider 'virtualbox'... vagrant box remove kublr-322 Removing box 'kublr-322' (v0) with provider 'virtualbox'...
If you receive a “The installation failed” error message while installing the VirtualBox, follow these instructions:
If your virtual machine crashes with the message like this:
Stderr: VBoxManage.exe: error: The virtual machine 'kublr' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\xxx\VirtualBox VMs\kublr\Logs\VBoxHardening.log' VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine
Double check that you are using Virtualbox 5.2 or later. VirtualBox 5.1 is not supported. If problem still persists on VirtualBox 5.2, please contact a Kublr representative.
If Vagrant is already installed, you may experience following errors:
Ignoring ffi-1.9.14 because its extensions are not built. Try: gem pristine ffi --version 1.9.14 Ignoring nokogiri-126.96.36.199 because its extensions are not built. Try: gem pristine nokogiri --version 188.8.131.52 Ignoring unf_ext-0.0.7.2 because its extensions are not built. Try: gem pristine unf_ext --version 0.0.7.2 Ignoring ffi-1.9.14 because its extensions are not built. Try: gem pristine ffi --version 1.9.14 Ignoring nokogiri-184.108.40.206 because its extensions are not built. Try: gem pristine nokogiri --version 220.127.116.11 Ignoring unf_ext-0.0.7.2 because its extensions are not built. Try: gem pristine unf_ext --version 0.0.7.2 Installing the 'vagrant-disksize' plugin. This can take a few minutes... Bundler, the underlying system Vagrant uses to install plugins, reported an error. The error is shown below. These errors are usually caused by misconfigured plugin installations or transient network issues. The error from Bundler is: conflicting dependencies ffi (= 1.9.18) and ffi (= 1.9.14) Activated ffi-1.9.14 which does not match conflicting dependency (= 1.9.18) Conflicting dependency chains: ffi (= 1.9.14), 1.9.14 activated versus: ffi (= 1.9.18) Gems matching ffi (= 1.9.18): ffi-1.9.18
On Windows with the latest version of Vagrant (2.1.2) you may see the error as:
C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/bin/vagrant:47:in `=': Invalid argument - ruby_setenv(VAGRANT_NO_PLUGINS)(E from C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/bin/vagrant:47:in `block in <main>' from C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/bin/vagrant:36:in `each_index' from C:/HashiCorp/Vagrant/embedded/gems/2.1.2/gems/vagrant-2.1.2/bin/vagrant:36:in `<main>'
Open Vagrantfile and find the line:
required_plugins = (plagin-name)
There are list of plugins that you need to install
To fix the issue, run the command not in directory with Vagrantfile (up to the level above):
vagrant plugin install plagin-name
Some non-standard browser extensions or plugins (not installed by default) aren’t compatible with the Kublr Control Plane. In this case, please use the browser in incognito mode (plugins are automatically disabled) or temporary disable the plugins.
More details can be found at: https://github.com/hashicorp/vagrant/issues/8783.
Please upgrade Microsoft PowerShell to version 5.0. https://www.microsoft.com/en-us/download/details.aspx?id=50395
Please contact your IT department to resolve the issue.
For questions or troubleshooting please contact contact us
We welcome your feedback. After all, Kublr was created to simplify your Kubernetes experience.
Questions? Suggestions? Need help? Contact us.