Pre-Provisioned Override Files

Pre-provisioned environments require certain override files to work properly. The override files can contain HTTP Proxy info and other factors, including whether you want the image to be FIPS-enabled, NVIDIA optimized, and so on.

Those override files must also have a Secret that includes all of the overrides you wish to provide in one file.

Prior to DKP 2.6, you had to specify the proxy in the KIB override setup and then again in the dkp create cluster command, even though in this case they would always both use the exact same proxy setting. As of 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. More information about this flags is found on the Pre-provisioned Use HTTP Proxy page.

The nodes that get Kubernetes on them through CAPPP automatically get the HTTP proxy secrets that you set using the flags. You no longer have to put the proxy info in both the overrides AND the dkp create cluster command as an argument.

For example, if you wish to provide an override with Docker credentials and a different source for EPEL on a CentOS7 machine, you can create a file like this:

YAML

image_registries_with_auth:
- host: "registry-1.docker.io"
  username: "my-user"
  password: "my-password"
  auth: ""
  identityToken: ""

For RHEL Pre-provisioned using GPU, provide the following additional lines of information in your override file:

rhsm_user: ""

rhsm_password: ""

See Example below:

CODE

image_registries_with_auth:
- host: "registry-1.docker.io"
  username: "my-user"
  password: "my-password"
  auth: ""
  identityToken: ""
  
rhsm_user: ""
rhsm_password: ""

Next Topic

Using HTTP/S Proxy with KIB Images