You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,13 +1,15 @@
1
-
# Techzone Deployer for the Maximo Operator
1
+
# Techzone Deployer for the Maximo
2
2
3
-
This repository contains a Tekton pipelines to deploy the [Maximo Operator](https://github.com/cloud-native-toolkit/operator-masauto) that packages[mas-ansible](https://ibm-mas.github.io/ansible-devops/).
3
+
This repository contains a Tekton pipelines to deploy Maximo using[mas-ansible](https://ibm-mas.github.io/ansible-devops/).
4
4
5
5
## Pre-requisites
6
6
7
7
### Deployer Cluster
8
8
9
9
An IBM Technology Zone `deployer` cluster is assumed to be configured with an appropriate Red Hat OpenShift version for the Maximo version you wish to deploy, with appropriate sizing. Refer to [Maximo Product Documentation](https://www.ibm.com/docs/en/mas-cd/continuous-delivery?topic=planning) for more information.
10
10
11
+
A deployer cluster can be created by installing the Deployer Operator
12
+
11
13
A `deployer` cluster is configured with the following items:
12
14
13
15
- ExternalSecrets operator deployed with a ClusterSecretStore configured.
@@ -51,8 +53,6 @@ the pipeline runs the MAS DevOps playbooks and can be modified or extended using
51
53
52
54
Consult the documentation for MAS DevOps [here](https://ibm-mas.github.io/ansible-devops/)
0 commit comments