Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products

PowerProtect Data Manager 19.10 Kubernetes User Guide

Pull images from Docker Hub as authenticated user if Docker pull limits reached

PowerProtect container images are hosted in Docker Hub. If the Kubernetes cluster is unable to pull images from Docker Hub because of Docker pull limits, it might be required to pull images from Docker Hub as an authenticated user.

Perform the following steps to pull the images from Docker Hub:

  1. Create an imagePullSecret in the powerprotect namespace that contains the Docker user credentials. For example:
    kubectl create secret docker-registry secretname --docker-server=DOCKER_REGISTRY_SERVER --docker-username=DOCKER_USER --docker-password=DOCKER_PASSWORD --docker-email=DOCKER_EMAIL -n powerprotect
  2. Update the PowerProtect Data Manager deployment in the powerprotect namespace to add a reference to the imagePullSecret created in the previous step:
    1. Run the command kubectl edit deployment powerprotect-controller -n powerprotect
    2. Review the output for the following lines:
                   spec:
                         containers:
    3. Add the following lines:
                   spec:
                         imagePullSecrets:                          <--- New line
                         - name:  <secret name>                <---- New line
                         containers:
    4. Repeat these steps for the Velero deployment in the velero-ppdm namespace,

The article at https://www.docker.com/increase-rate-limits provides more information about Docker rate limits and creating a Docker user account.


Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\