The settings portion has additional information on how to configure your environment.
This is the IP address of the machine where you are running docker and subsequently the kubam services. This IP address needs to be reachable from the same network that your blades access as well as the CIMC network. The reason for this is because:
While it may work with DHCP relay or other methods, really the simplest way is to make the install network, the CIMC network, and the UCS management network all be on the same network. We can always update this if required, but for now that’s the way it works. If you have an issue with that, open an issue
You’ll notice that KUBAM never asks you for a password for the servers you are installing. The reason for this is that we are trying to be more secure. As such, we only access our KUBAM nodes using SSH keypairs. To create SSH keypairs there is lots of documentation on how to do this.
When entering the public key into the SSH form, please be sure to add the
ssh-rsa portion before the key. For example, a properly entered key would be:
Note there should be no spaces.
In many enterprise environments the servers are behind a firewall and don’t have access to the public internet without a proxy server. KUBAM requires the ability to reach out to docker hub and other container and package repositories to download all the necessary components. For this we ask that you enter a proxy configuration. If you are in an open environment you may not need a proxy environment. The proxy server should be entered something like the following:
IP addresses for proxy servers may not work as expected.