Working with the PlainID Docker Hub

PlainID uses a private Docker Hub to manage and maintain images required for deployments. PlainID provides users with the PlainID Docker Hub permissions, enabling them to authenticate and receive access to images while processing the installation.
Refer to your organization's relevant deployment procedures to ensure that an authentication process is added and executed accurately.

Standalone Deployment

Authentication to the PlainID Docker Hub Private Repository is not required for the Standalone Deployment.

Permissions

Before starting the process, ensure you have an account with permissions to pull PlainID images from our Docker Hub. If you do not have permissions, create a Docker Hub account and contact PlainID Support to acquire the relevant permissions for the private repository.

Helm Installation

For Customers deploying using the out of the box Helm installation follow the steps below to create an image pull secret and place it in the relevant Kubernetes namespace:

Create an Image Pull Secret.
In the values-custom.yaml file, add the following properties and replace the my-image-pull-secret with your own:

imagePullSecrets:
  - name: "my-image-pull-secret"

These properties can also be found in the examples/values-custom.image-pull-secrets.yaml file in the PAA Helm Chart.

Optional: If deploying the Redis container image preconfigured in the PlainID Helm Chart instead of using a managed Redis solution, we recommend adding the configuration block below to enable authenticated users to pull the image. This helps avoid pull rate limits associated with unauthenticated users.

redis:
  global:
    imagePullSecrets:
      - "my-image-pull-secret"
  image:
    pullSecrets:
      - "my-image-pull-secret"

redis-ha:
  imagePullSecrets:
    - name: "my-image-pull-secret"

Deploy or redeploy the PAA Helm Chart or Kubernetes YAML files as needed.

Access to the PlainID Docker Hub private repository is a required step for authenticated deployments. Ensure that your Docker Hub credentials are properly configured and that the image pull secret is added to your Kubernetes environment before deployment. This setup ensures uninterrupted access to PlainID-maintained images, prevents pull rate limitations, and guarantees that all deployed containers use the most up-to-date and verified versions provided by PlainID.

For any permission-related issues, contact PlainID Support before proceeding with your deployment.