Downloading the Certified Container Software for Online Cluster

Before you install IBM Certified Container Software for IBM® Sterling Control Center Monitor, ensure that the installation files are available on your client system.

For passing database drivers or other files to container, there are multiple ways to provide those files to container:

Creating PVC for user inputs using below sample file

kind: PersistentVolumeClaim
apiVersion: v1
metadata:
  name: sccm-pvc-ui
  labels:
    app.kubernetes.io/name: sccm
    app.kubernetes.io/instance: sccm
spec:
  # Disable dynamic provisioning
  storageClassName: <Storage Class Name>
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: "2Gi"

Create user input PVC using file using commands

# kubectl create -f pvc-ui.yaml -n ibm-sccm

Creating wrapper image over existing image using below Dockerfile

Create a directory using below command:
# mkdir wrapper_image_data
# cd wrapper_image_data
Place following files to the created directory:
  1. All files to be passed to container, including database drivers
  2. Dockerfile with below content:
    #Dockerfile
    FROM  <docker image name>
    COPY --chown=$CONTAINER_USER  <all file names with space between them> /app/CC/user_inputs/
    RUN chmod 775 /app/CC/user_inputs/*
    
  3. Invoke the following command to create wrapper image:
    # docker build -f Dockerfile -t <wrapper image name with tag>.

    Now, new image will be created, this image will be used in deployment.

Creating init container image using below Dockerfile

Invoke the following command to create a init-dockerfile.

FROM registry.access.redhat.com/ubi8/ubi
		RUN mkdir -p /jdbc_drivers/
		COPY --chown=$CONTAINER_USER <all file names with space between them> /jdbc_drivers/
		RUN chmod -R 775 /jdbc_drivers/
Invoke the following command to create init container image:
# docker build -f init-dockerfile -t <container image name> .

This image needs to be pushed inside local registry for accessing inside cluster.

Now, this image will be used in init container image section for passing files including database drivers inside container.