diff --git a/ee/ucp/user-access/cli.md b/ee/ucp/user-access/cli.md index 3ba6b13305..be62578917 100644 --- a/ee/ucp/user-access/cli.md +++ b/ee/ucp/user-access/cli.md @@ -85,19 +85,6 @@ and the `DOCKER_CERT_PATH` environment variable to use the client certificates that are included in the client bundle you downloaded. The utility scripts also run the `kubectl config` command to configure kubectl. -### Use client certificates with Docker contexts - -In Docker Enterprise 3.0, new files are contained in the UCP bundle. These changes support -the use of `.zip` files with `docker context import` and allow you to directly change -your context using the bundle `.zip` file. Navigate to the directory where you downloaded -the user bundle and use `docker context import` to add the new context: - -```bash -cd client-bundle && docker context import myucp ucp-bundle-$USER.zip" -``` - -> **Note**: Refer to [Working with Contexts](/engine/context/working-with-contexts/) -for more information on using Docker contexts. To confirm that your client tools are now communicating with UCP, run: @@ -124,8 +111,25 @@ kubectl config current-context +The expected Docker server version starts with `ucp/`, and the expected +kubectl context name starts with `ucp_`. + You can now use the Docker and kubectl clients to create resources in UCP. +### Use client certificates with Docker contexts + +In Docker Enterprise 3.0, new files are contained in the UCP bundle. These changes support +the use of `.zip` files with `docker context import` and allow you to directly change +your context using the bundle `.zip` file. Navigate to the directory where you downloaded +the user bundle and use `docker context import` to add the new context: + +```bash +cd client-bundle && docker context import myucp ucp-bundle-$USER.zip" +``` + +> **Note**: Refer to [Working with Contexts](/engine/context/working-with-contexts/) +for more information on using Docker contexts. + ## Client certificates for administrators UCP issues different types of certificates depending on the user: