Create image pull secret
Create image pull secret in the namespace where you are planning to deploy Asset Repository. Here we will depoy it in ‘integration’ namespace.¬†
Login to OCP using below command
oc login <OpenshiftURL> -u <username> -p <password>
For example OpenshiftURL is¬†https://prod-master.fyre.ibm.com:8443
Switch to ‘integration’¬†namespace using ‘oc project’ command:
oc project integration
Run below command to create the secret with the name ‘assetregistrysecret’
oc -n integration create secret docker-registry assetregistrysecret \
--docker-username=$(oc whoami) \
--docker-password=$(oc whoami -t) \
Email could be¬†any email address.
Install Asset Repository
Login to integration platform navigator and click on ‘Install asset repository’.
Enter the name of Helm release, target namespace and target cluster.
Specify Image pull secret and docker registry. By default “cp.icr.io/cp/icp4i/” would be populated in Docker registry. We will change it to private docker registry of OpenShift to pull images for asset repository. If you are installing for production uses, keep the ‘Production usage’ checkbox checked, else uncheck it.
Specify the platform navigator namespace. By default it would be ‘integration’, unless you had changed it in config.yaml while deploying CP4I.
‘Hostname of the ingress proxy to be configured’ should be set to hostname of the ingress proxy; e.g. in my case it is ‘icp-proxy.188.8.131.52.nip.io’. Note that¬†it is the value of ‘proxy-host’ under ‘router’ section in config.yaml.
Specify the glusterfs storage class name for ‘Cloudant metadata store storage class’.
By default ‘assetrepo’ is populated for ‘Ingress path’. You can modify it if required or leave it to default.
Specify the storage class for glusterfs for ‘Catalog remotes Storage Class’.¬†
You can leave all other parameters to default. Click on ‘Install’. It will take few minutes to install.¬†
After successful installation, you can see all the pods running for asset repository.
Navigate to the asset repository release in platform navigator.
Click on the release name of asset repository and it will navigate to the asset repository.
You can add assets to asset respository from local system or from different integration components or from remote GitHub repository etc. The assets can be shared in controlled manner with the help of proper ‘Access Control’ configurations.
In this recipe we learnt how to deploy Asset Repository in Cloud Pak for Integration. There are more features coming in Asset Repository very soon. Stay tuned !!!