Introduction:
IBM Cloud Pak for Integration Asset Repository is an add-on to the IBM Cloud Pak for Integration (ICP4I) that allows the user to store, manage, retrieve and search integration assets within the IBM Cloud Pak for Integration and its capabilities.
Users of the Cloud Pak are able to utilise the Asset Repository to share integration assets across the platform capabilities. Storing assets, e.g. JSON schemas, within this repository allows them to be accessed directly within the user interface of certain Integration capabilities. For example, an OpenAPI specification asset stored in the repository can be directly imported within the IBM API Connect user interface.
Prerequisites:
1- A storage provider that supports Read Write Many (RWX) persistent volumes. We will use Glusterfs storage here.
2- A user with cluster administrator role is required to install the chart.
3- Red Hat OpenShift SecurityContextConstraints Requirements:
This chart requires a SecurityContextConstraints to be bound to the target namespace prior to installation. To meet this requirement there may be cluster-scoped, as well as namespace-scoped, pre- and post-actions that need to occur.
The predefined SecurityContextConstraints ibm-privileged-scc has been verified for this chart; if your target namespace is bound to this SecurityContextConstraints resource you can proceed to install the chart.
Run the following command to add the service account of the Integration server to the privileged scc:
oc adm policy add-scc-to-group ibm-privileged-scc system:service
Resources Required
This chart deploys in a HA configuration by default which has the following resource requirements:
4.25 CPUs
8.5 GB Memory
The number of replicas for certain components can be configured during install which would alter these requirements.
Image Pull Secret: If you are using a private Docker registry (including an ICP Docker registry), an image pull secret needs to be created before installing the chart. Here we will use OCP registry, so will create image pull secret. A default image pull secret gets created in each namespace with the name like 'default-dockercfg-<xxxxx>' to pull the images from the same namespace. So if your ImageStreams are in same namespace, you can use this secret created by default. If you are pulling from IBM container registry, use ibm entitlement key secret.