Installing configuration containers

Make sure that you complete the preparation steps that are listed in Preparing to install IBM Business Automation Configuration Container.

Before you install Business Automation Configuration Container, use the following checks to make sure that you have everything in place:

1. Check the health of the IBM Cloud Private cluster by looking at the dashboard.
2. Check that the IBM Digital Business Automation for Multicloud images are in the IBM Cloud Private registry. The ibacc-master container image is used to install Business Automation Configuration Container. The following container images are used by the configuration container to install the products and run initialization and verification jobs.
   • bai-ibacc-job
   • baw-cam
   • ibacc-icp
   • ibacc-initialize
   • ibacc-verify
   • odm-ibacc-job
   •  New in 18.0.1  ibacc-navigator
3. Check that the ibm-dba-multicloud-prod tile (helm chart) is in the catalog.
4. Log in to your IBM Cloud Private cluster from the command line.

   cloudctl login -a https://cluster_CA_domain:8443 --skip-ssl-validation

   Where cluster_CA_domain is the certificate authority (CA) domain name. If you did not specify a CA domain, the default value is mycluster.icp. The skip-ssl-validation parameter disables the SSL validation process. SSL validation is omitted in the example to do without a trusted certificate in development environments. The self-signed SSL certificate causes an error when using the cloudctl CLI.

   If you want to install into a specified namespace, you need to run the command with the -n parameter. The following example specifies the name of the namespace as my-icp-space.

   cloudctl login -a https://cluster_CA_domain:8443 --skip-ssl-validation \
   -u admin -p admin -c id-mycluster-account -n my-icp-space

5. Optional: Create an image pulling secret, if one does not exist.

   The following command provides an example:

   kubectl create secret docker-registry admin.registrykey --docker-server=mycluster.icp:8500 --docker-username=admin --docker-password=admin --docker-email=<user-email>

   If you deploy to a non-default namespace, follow the instructions here Creating imagePullSecrets for a specific namespace.

6. Optional: If you want to use the container images in all namespaces or limit the images to a specific namespace, you can set an image scope. For more information, see Changing image scope.
7. Optional: If the container images are in a different namespace to the target deployment, open the cluster image policy by running the kubectl edit command on the default policy file. Then, add the registries that can deploy in the namespace (my-icp-space) to the list of repositories, and save the .yaml file.

   kubectl edit ClusterImagePolicy ibmcloud-default-cluster-image-policy

   apiVersion: securityenforcement.admission.cloud.ibm.com/v1beta1
   kind: ClusterImagePolicy
   metadata:
     ...
   spec:
     repositories:
     - name: mycluster.icp:8500/my-icp-space/*
     - name: quay.io/kubernetes_incubator/* 
     - name: mycluster.icp:8500/ibmcom/*

   The default policy includes certain repositories that you must leave in place so that your cluster is configured correctly. The policy allows all images from the specified container registries to be deployed into my-icp-space without enforcement.

   If you do not want to use the IBM Cloud Private catalog Helm tile in the Admin console, you can install Business Automation Configuration Container from the command line with the helm install command. In this case:

   1. Add the IBM Cloud Private local-charts repository to your Helm client, as follows.

      sudo helm repo add local-charts https://mycluster.icp:8443/helm-repo/charts --ca-file $HELM_HOME/ca.pem --cert-file $HELM_HOME/cert.pem --key-file $HELM_HOME/key.pem

      The repository local-charts contains the deployable Helm charts. It can now be used as the source from which to install Helm charts into the cluster.

   2. Use the helm install command to deploy the chart with release name my-dbamc-release, as follows.

       New in 18.0.2 

      helm install --name my-dbamc-release local-charts/ibm-dba-multicloud-prod --tls --version 2.1.0 

       For 18.0.1 

      helm install --name my-dbamc-release local-charts/ibm-dba-multicloud-prod --tls --version 2.0.0 

       For 18.0.0 

      helm install --name my-dbamc-release local-charts/ibm-dba-multicloud-prod --tls --version 1.0.0