Pushing Docker images to the Docker registry

About this task

The Component Pack Helm charts use a Docker registry to pull the Docker images to run the associated pods. The required Docker images are included in the Component Pack installation package; as part of the Component Pack deployment process, you must push the Docker images to your Docker registry.

Procedure

Determine which Docker images you need for your Component Pack deployment.

Table 1 lists the Docker images required by the Helm chart that installs each of the Component Pack offerings.

Table 1. Docker images required by each Helm chart
Helm chart	Repository/image
`bootstrap`	connections/bootstrap
`infrastructure`	connections/appregistry-client connections/appregistry-service connections/middleware/haproxy connections/middleware/mongodb connections/middleware/mongodb-rs-setup connections/middleware/redis connections/middleware/redis-sentinel
`orientme`	connections/analysis-service connections/community-suggestions connections/indexing-service connections/itm-services connections/mail-service connections/middleware-graphql connections/orient-web-client connections/people/people-datamigration connections/people/people-idmapping connections/people/people-relationship connections/people/people-scoring connections/retrieval-service connections/middleware/solr-basic connections/userprefs-service connections/middleware/zookeeper
`elasticsearch`	connections/elasticsearch
`mw-proxy`	connections/mw-proxy
`elasticstack`	connections/elasticsearch-curator connections/filebeat connections/kibana connections/logstash
`sanity`	connections/sanity
`sanity-watcher`	connections/sanity-watcher
`cnx-ingress`	connections/cnx-ingress
`kudos-boards-cp`	connections/user connections/boards connections/core connections/licence connections/notification connections/provider connections/webfront connections/minio connections/activity-migration

Note: If you are using Amazon ECR, then before you can push the Docker images, you must create the repository to store them. Use Table 1 to determine the required repository for each of the images.

Run the following command to push the images to the Docker registry.
1. Extract the Component Pack installation package to a temporary location.
2. Navigate to the following directory within the extracted Component Pack installation package:
```
extractedFolder/microservices_connections/hybridcloud/support 
```
3. Replace the existing script file setupImages.sh in extractedFolder/microservices_connections/hybridcloud/support with the file attached in HCL support article KB0074465. Then run the following command:
```
./setupImages.sh -dr Docker_registry -u Your_user_name -p Your_password -st Stack_options
```
  where:
  - Docker_registry is the name of your Docker registry (include the port if applicable)
  - Your_user_name is the user name for your Docker registry
  - Your_password is the password for your Docker registry
  - Stack_options is a comma-separated list that indicates which components you want to deploy:
    
    customizer
    
    elasticsearch
    
    orientme
    
    kudos-boards
    
    If you omit this flag, all images for all components are pushed to the registry.
  Note: If you have a non-authenticated Docker registry, just enter dummy values in for username and password. Docker always asks for credentials, so you must include the -u and -p flags even for a non-authenticated registry.
  For example, the following command uploads the Docker images for Customizer and Elasticsearch to a local Docker registry:
```
./setupImages.sh -dr localhost:5000 -u admin -p MyPassw0rd -st customizer,elasticsearch
```