You can use a private container repository to store the container images.

Importing LM Container Images 

Import the following LM Container images from Docker Hub into your container registry.

• LogicMonitor/argus
• logicmonitor/collectorset-controller
• logicmonitor/collector
• k8s.gcr.io/kube-state-metrics/kube-state-metrics
  Argus uses  k8s.gcr.io/kube-state-metrics/kube-state-metrics Kubernetes container image to deploy Kube State Metrics for metrics collection.

Setting LM Container Helm Configuration for Private Repository

You must add the registry URL in the global section of the configuration.yaml file as follows:

Example: Global Image Registry

global:
  image:
    registry: "<name of the registry>"

You can also use a different repository for different components of LM Container. You must add the following configurations:
Example: For Different Registries

argus:
  image:
    registry: "<name of the registry>"
  collector:
    image:
      registry: "<name of the registry>"
collectorset-controller:
  image:
    registry: "<name of the registry>"

Pulling Images from a Private Repository using ImagePullSecrets

Private container registries allow only authenticated clients to pull images from it. You can store the authorization token used to communicate with the registry as a Kubernetes secret. For more information, see the Kubernetes guide on Pulling an Image from a Private Registry.

You can add the image pull secret names in LM Container Helm Chart and apply configuration using the Helm upgrade command. 

Image Pull Secrets
global:
  imagePullSecrets: []

Ensure the image pull secrets are present in the namespace as mentioned in the LM Container namespace.

If you want to point to different image pull secrets for each component, you must set the following configurations:

Image Pull Secrets
argus:
  imagePullSecrets: []
collectorset-controller:
  imagePullSecrets: []