Preparing a Deployment Container

To perform CloudBlue Commerce deployment, you will need a Docker container that includes all necessary tools such as kubectl, Helm, and helmfile-deploy. Prepare this container by completing the following steps:

  1. Install Docker on your computer.

  2. Prepare your login and password for accessing the Docker registry at odindevops-a8n-docker-21-public.jfrog.io.

    Note: Contact your Technical Account Manager (TAM) to obtain these credentials.

  3. On your computer, create a kubeconfig file that contains the administrative credentials of your Kubernetes cluster.

  4. Make sure your config.yaml is in a directory on your computer.

  5. Log in to the Docker registry:

    docker login odindevops-a8n-docker-21-public.jfrog.io

    When asked, specify the login and password that you prepared.

  6. Pull the image that your deployment container will be based on:

    docker pull odindevops-a8n-docker-21-public.jfrog.io/platform-core/helmfile-deploy:master
  7. Create this container and start its interactive shell by running this command:

    docker run --rm -it -v PATH_TO_KUBECONFIG_FILE:/root/.kube/config -v YAML_CONFIG_DIRECTORY:/config --entrypoint /bin/bash odindevops-a8n-docker-21-public.jfrog.io/platform-core/helmfile-deploy:master

    where:

    • PATH_TO_KUBECONFIG_FILE is the full path to your kubeconfig file.

    • YAML_CONFIG_DIRECTORY is the full path to the directory that contains your config.yaml file.

    For example, if the full path to your kubeconfig file is D:\CBC\MyKubeconfig and your config.yaml file is in the D:\CBC\MyDeploymentConfig directory, you need to run a command like this:

    docker run --rm -it -v D:\CBC\MyKubeconfig:/root/.kube/config -v D:\CBC\MyDeploymentConfig:/config --entrypoint /bin/bash odindevops-a8n-docker-21-public.jfrog.io/platform-core/helmfile-deploy:master

After you prepare this container, you can start the deployment.

We use cookies to improve the usability of our site. By continuing to use this site and/or logging in, you are accepting the use of these cookies. For more information, visit our Privacy Policy.