openshift-terraform

[luqmanbarry]

Type of repository request

New set of repositories

Requested name for the repository

rosa-classic-terraform, rosa-hcp-terraform, aro-classic-terraform, openshift-day2-gitops

Repository Description

rosa-classic-terraform: Terraform modules for provisioning ROSA Classic clusters.
rosa-hcp-terraform: Terraform modules for provisioning ROSA HCP clusters.
aro-classic-terraform: Terraform modules for provisioning ARO classic clusters.
openshift-day2-gitops: OpenShift GitOps app of apps pattern for cluster configuration.

Associated CoP

The CoP this repository is associated with.

Admin Access

luqmanbarry, Andrew Block, TBD

Write Access

TBD

Read Access

TBD

Additional details

Any additional information or context to provide for this request.

---

Review request:

cc: @redhat-cop/container-cop-core

[garethahealy]

re: openshift-day2-gitops - we already have:

• https://github.com/redhat-cop/helm-charts
• https://github.com/redhat-cop/gitops-catalog

which contain day2 and probably some other repos which are not obvious in their name but contain day2. do we need a 3rd...

[luqmanbarry]

Please check this repo out. IMO this one is more comprehensive than some of the stuff we already have. Besides it's been tested on customer environments

[garethahealy]

Besides it's been tested on customer environments

Those repos are used by consultants/customers daily, so I don't see your point.

IMO this one is more comprehensive than some of the stuff we already have

So let's improve them, instead of creating another repo for people to get confused over which to use and when.

My point is: should we be duplicating or re-using? I think re-use/improve.

• https://gitlab.consulting.redhat.com/openshift-terraform-guides/aro-classic/-/tree/main/gitops/modules/splunk-log-forwarder?ref_type=heads
• https://github.com/redhat-cop/helm-charts/tree/main/charts/openshift-logforwarding-splunk

Thats just one example of duplication, but am sure there's much more.

[luqmanbarry]

• https://github.com/redhat-cop/helm-charts/tree/main/charts/openshift-logforwarding-splunk
  uses the ClusterLogForwarder operator which did not work in the customer environment (ARO). Even RH support asked us to find alternatives.

What's in the GitLab uses the Splunk OTEL helm chart.

[luqmanbarry]

Lets take this offline, compare, improve what's already there, and add what's new.