Pulling images from private repositories

For development use cases, you can configure Sterling Intelligent Promising to pull middleware services such as Cassandra, Kafka, and Elasticsearch from your internal or private repository instead of public registries such as Docker Hub or Red Hat®.

1. Set the UsePublicImageRegistry property to false. This property disables the default behavior of pulling images from public repositories.
2. Pull the following middleware images from public registries, say docker hub.

   docker.io/apache/kafka:3.9.1
   docker.elastic.co/elasticsearch/elasticsearch:8.19.8
   docker.io/cassandra:4.1.0
   docker.elastic.co/kibana/kibana:8.19.8

3. After the images in step 2 are pulled, you can retag and push those to the internal or private repositories as stated in the following manner.

   <image_repository>/kafka:3.9.1
   <image_repository>/elasticsearch:8.19.8
   <image_repository>/cassandra:4.1.0
   <image_repository>/kibana:8.19.8

4. After the images in step 2 are pushed to internal or private repository, you can use the same repository in the image parameter.
5. Ensure the following middleware images are available in your internal repository by using the specified image names and versions.

   <image_repository>/kafka:3.9.1
   <image_repository>/elasticsearch:8.19.8
   <image_repository>/cassandra:4.1.0
   <image_repository>/kibana:8.19.8

   For more information about configuring image related properties, see image parameter.
   For more information about versions of middleware services, see Installing middleware services in a production environment.