Using KIB with Pre-provisioned Environments

In Pre-provisioned environments, KIB runs automatically inside the bootstrap cluster, against the list of nodes that you define. Whereas with other providers, you run KIB outside the cluster manually to build your images.

For Pre-provisioned, you define a set of nodes that already exist. During the cluster creation process, KIB is built into DKP and automatically runs the machine configuration process (which KIB uses to build images for other providers) against the set of nodes that you defined. This results in your pre-existing or pre-provisioned nodes being configured properly. The remainder of the cluster provisioning happens automatically after that.

• In a Pre-provisioned environment, you have existing machines and DKP consumes them to form a cluster.

• When you have another provisioner (for example, cloud providers such AWS, vSphere and others), you build images with KIB and DKP consumes the images to provision machines and form a cluster.

Prior to DKP 2.6, you had to specify the HTTP proxy in the KIB override setup and then again in the dkp create cluster command. After DKP 2.6, an HTTP proxy gets created from the Konvoy flags for the control plane proxy and workers proxy values. The flags in the DKP command for Pre-provisioned clusters populate a Secret automatically in the bootstrap cluster. That Secret has a known name that the Pre-provisioned controller finds and applies when it runs the KIB provisioning job.