Techzone Deployer Cloud Pak for Security pipelines

This repository contains a set of Tekton pipelines to deploy IBM Cloud Pak for Security in an IBM Technology Zone deployer cluster.

Prerequisites

You will need an instance of IBM Verify. Once you have an instance of verify, you will need the API access. Grab the Client ID and Client secret for Verify.

To obtain a Client ID and Client secret from your Verify instance.

• If an API Client does not exist, create one. For more information, see API Access
• Go to Security > API Access and click the edit icon for the API client.
• Under API credentials, copy and store the Client ID and Client secret values.

An IBM Technology Zone deployer cluster is assumed to be configured with an appropriate Red Hat OpenShift version for the Cloud Pak for Security version you wish to deploy, with appropriate sizing. Refer to IBM Cloud Pak for Security documentation for more information.

A deployer cluster is configured with the following items:

• ExternalSecrets operator deployed with a ClusterSecretStore configured. The remote ExternalSecrets secret store must include an IBM Entitlement Key.
• Techzone Deployer Tekton tasks deployed (deploy YAML).
• OpenShift GitOps configured with One Touch Provisioning ArgoCD instance, and any relevant RBAC rules.
• OpenShift Pipelines operator deployed.
• OpenShift Data Foundation

Repository organisation

The top-level folders in this repository are for the different CP4S versions. In each top-level folder there will be a pipeline and a pipelinerun.

.
└── cp4s-version/
    ├── pipeline.yaml
    └── pipeline-run.yaml

Deployment Scripts

oc apply -f pipeline.yaml to install configure service account and install tasks and pipeline

oc create -f pipeline-run.yaml to kick off pipeline to install CP4S

CP Console info

If this is being deployed for a demo purpose (I.E on TechZone) you can follow these steps to get the login info.

In the OpenShift Cluster

• Go to Pipeline -> Pipelines
• Click on the PipelineRuns Tab
• Search for the pipeline run name that includes cp4s-deployer and click on it
• Wait for the pipelinerun to reach the Succeeded status
• Click the Logs Tab, then click on the task log for open-ldap
• You should see login details at the bottom of the logs, use these to login to the cp console