Pull Observability Operator objects from separate location

Pull manifests from a separate location

Feature Request

Background

The Observability operator will be installed by default on OpenShift Dedicated clusters. We want to leverage the operator to monitor ISV metrics, however, there is still a need to configure the operator for a given ISV in the form of ServiceMonitors and PrometheusRules. Given that each ISV will have specific criteria from which to trigger alerts, record metrics, etc, we need a more automated form of configuration for the operator.

Description of proposed solution

Considering that users of this operator could exist in disconnected environments, we see two potential/necessary solutions for this problem. Adding the ability to pull manifests/objects from a remote url (manifestURL), and the ability to pull config from a secret or configmap.

The Kafka Observability Operator for reference. https://github.com/redhat-developer/observability-operator

Motivation

Low maintenance, repeatable configuration on OpenShift Dedicated environments.

thanks for the consideration

The issue names no repository files, tests, or entry points. Start by reviewing the operator's current configuration handling and the linked Kafka Observability Operator for reference; the work is done when the scope and behavior for manifestURL plus Secret or ConfigMap configuration are agreed, including disconnected environments.