Value Statement

When use a custom Observability Hub or Alertmanager URL, the customers have to manually create 1 route in the hub for each one of them. As mentioned in the documentation ticket for the implementation (see https://issues.redhat.com/browse/ACM-11407), these routes are mostly a copy of the already existing ones, but with a host that matches the custom URL's and a different name.

This is needed for the intermediate component's host to be recognize by the hub's routers.

We should automate their creation to reduce the amount of manual steps needed by customers.

Definition of Done for Engineering Story Owner (Checklist)

• MCO automatically creates the required Route objects when using `spec.advanced.customObservabilityHubURL` or `spec.advanced.customAlertmanagerURL`

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the [Customer
  Portal_doc_issue template](
  https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
  and ensure doc acceptance criteria is met. Link the development issue to
  the doc issue.
• [ ] Provide input to the QE team, and ensure QE acceptance criteria
  (established between story owner and QE focal) are met.

Support Readiness

• [ ] The must-gather script has been updated.