Configure the client bundle

This section explains how to configure the client certificate bundle to authenticate your requests with MKE using the Docker CLI and kubectl.

To configure the client certificate bundle:

1. Extract the client bundle .zip file into a directory, and use the appropriate utility script for your system:

   • For Linux:

     cd client-bundle && eval "$(<env.sh)"
     

   • For Windows (from an elevated PowerShell prompt):

     cd client-bundle && env.cmd
     

   The utility scripts do the following:

   • Update DOCKER_HOST to make the client tools communicate with your MKE deployment.

   • Update DOCKER_CERT_PATH to use the certificates included in the client bundle.

   • Configure kubectl with the kubectl config command.

     Note

     The kubeconfig file is named kube.yaml and is located in the unzipped client bundle directory.

2. Verify that your client tools communicate with MKE:

   docker version --format '{{.Server.Version}}'
   kubectl config current-context
   

   The expected Docker CLI server version starts with ucp/, and the expected kubectl context name starts with ucp_.

3. Optional. Change your context directly using the client certificate bundle .zip files. In the directory where you downloaded the user bundle, add the new context:

   cd client-bundle && docker context \
   import myucp ucp-docker-bundle.zip
   

Note

If you use the client certificate bundle with buildkit, make sure that builds are not accidentally scheduled on manager nodes. For more information, refer to Manage services node deployment.