https://github.com/cloud-native-toolkit/deployer-cp4s
https://github.com/cloud-native-toolkit/deployer-cp4s
Last synced: 4 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/cloud-native-toolkit/deployer-cp4s
- Owner: cloud-native-toolkit
- Created: 2023-07-07T13:56:53.000Z (almost 3 years ago)
- Default Branch: main
- Last Pushed: 2024-10-08T15:21:19.000Z (over 1 year ago)
- Last Synced: 2025-06-22T03:02:55.526Z (12 months ago)
- Language: Shell
- Size: 51.8 KB
- Stars: 1
- Watchers: 11
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# 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](https://www.ibm.com/products/verify-identity). 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](https://docs.verify.ibm.com/verify/docs/native-applications?_gl=1*1t9rkn2*_ga*MTk1NDg5NjUzNi4xNjg5MjUyMTEx*_ga_FYECCCS21D*MTY4OTI1MjExMS4xLjEuMTY4OTI1MjM5Ny4wLjAuMA..)
- 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](https://www.ibm.com/docs/en/cloud-paks/cp-security/1.10) 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](https://github.com/cloud-native-toolkit/deployer-tekton-tasks/blob/main/argocd.yaml)).
- OpenShift GitOps configured with [One Touch Provisioning ArgoCD instance](https://github.com/one-touch-provisioning/otp-gitops), 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