Use ACM to manage pipelines in the demo namespace on the core cluster

[grdryn]

My thinking is that it might mean fewer different setup steps, and might guard from people accidentally (or intentionally) making manual changes to those resources in that namespace (we would typically manually roll out to separate namespaces for dev/test).

It would also mean that we wouldn't need to remember to manually roll out changes when a PR related to the pipelines is merged

[adelton]

Would Tekton Triggers and webhooks be an alternative approach for that?

[grdryn]

Possibly 🤔 While we could probably easily have tekton triggers for when PRs get merged, I'm not sure about when any of the k8s resources get changed manually/accidentally?

My thinking is that while we already have ACM periodically (or on demand) synchronizing resources to clusters from the state described in a Git repo, that's what would be useful in this case too, in my opinion.

We already have the manual bootstrap step of oc apply -k acm/registration. If we put the declarative application of the pipeline yamls there too, then it might also simplify the setup for the pipelines while also giving us continuous reconciliation.

WDYT?

[piotrpdev]

Maybe just merge #108 to solve this?

[grdryn]

Maybe just merge #108 to solve this?

#108 looks like it is trying to solve something else than this?

[piotrpdev]

Maybe just merge #108 to solve this?

#108 looks like it is trying to solve something else than this?

My bad, you're right 😅