Create tekton pipeline for performing zmodstack configurations after cluster installations

[ivandov]

Description

Currently the ansible automation that's being developed to deploy and configure the zmodstack products is triggered as part of the ARM and Cloudformation installation process.

This is problematic in a few ways:

• If an error occurs during the product deployments, then re-triggering this automation can be tricky from the OCP boot node.
• If a user wants to configure zmodstack products on a new OCP cluster that was provisioned manually or through ROSA/ARO, then running the ansible automation requires users to execute ansible from their local machine.

Potential Solutions

1. Create a tekton Pipeline YAML that executes the existing ansible playbook
2. Accept user-supplied inputs for setting up the OCP global pull secret and IBM Operator Catalog
3. Accept user-supplied inputs for which products to be installed

Additional Context

The tekton pipeline and any associated tasks or kubernetes resources should be applied by default into a newly provisioned OCP cluster after #54 is implemented.

---

Associated Work Items

• [x] #54
• [x] Create Tekton Task for zoscb install, calling existing Ansible role - #97
• [x] Create Tekton Task for zosconnect install, calling existing Ansible role - #97
• [ ] Create Tekton Task for wazi-devspaces install, calling existing Ansible role

[midhun6989]

@ivandov Could you clarify if a new Ansible role for Tekton Pipelines, say tekton / pipelines has to be created in the ocp monorepo at here?

[ivandov]

I think I'd like to follow the same logic described in #54 for this scenario. Use an ocp role under the ocp/ansible/roles folder and create an additional task for applying the tekton resources (Pipelines, Tasks, etc) after OCP Pipelines is installed.