There are scenarios where it is both impractical and impossible to follow a traditional cloud provisioning model where the latest software is downloaded and provisioned on the fly. For scenarios like this, “pre-packaged” images are provided that contains the Operating System, Kubernetes cluster components, Kubernetes Mgmt Operator and critical 3rd party software addons.
For example - An on-premises location with limited Internet connectivity or a factory environment where clusters need to be provisioned on 100s of servers in a day. - An ephemeral QA environment where it is impractical to download the software repeatedly over the Internet.
With the pre-packaged image based provisioning option, it is possible to provision a fully operational, centrally managed upstream Kubernetes cluster in minutes without having to download anything over the network/Internet. It is important to note that this workflow still requires the cluster to be able to connect to the Controller for activation, registration and configuration.
This document describes the GUI based, step-by-step workflow for the provisioning and activation process. The entire workflow can be performed entirely programmatically using Controller’s REST APIs. This allows organizations to completely embed this into their workflows/processes requiring zero manual intervention.
- The user is familiar with vSphere and optionally Orchestration using CloudInit.
- You will perform the provisioning using the Web Console
- vSphere v5.5 or higher
One Time Tasks¶
Download OVA image¶
Download the provided OVA image and stage this in a location where the vSphere environment can access it for provisioning.
The pre-packaged OVA image is ~4 GB in size. This has to be downloaded only once. The same image can be reused as many times as necessary
The OVA image comprises the following components. These are frequently updated to ensure the image is kept current. These are also dynamically updated during provisioning.
|Operating System (64-bit Ubuntu 18.04 LTS)|
|k8s Mgmt Operator|
|Addons for Monitoring, Logging and Ingress Controller Components|
The following versioning and naming convention is used for the images. For example, “rafay-clusterimage-r1.3.0.ova” is the 1.3.0 release. This release is compatible with 1.3.0 or higher of the Controller.
Upon request, we can provide illustrative examples for Cloud Init templates that help streamline and automate a number of steps during the instantiation of the Operating System. Customers can customize and extend these to suit their specific requirements.
Specifically, the Cloud Init templates implement and automate the following steps:
- Configuration of CPU, Memory and Storage for the VM
- Day 0 network configuration
- Day 0 iptables config [currently inbound rules for tcp port 80 and 443 only]
- Automated execution of the conjurer binary for auto registration of the VM with the Controller