Extend the operator to make the monitoring settings configurable

[erickuiper]

Is your feature request related to a problem? Please describe:
The current monitoring setup of cdi is based on static values with namespace: monitoring and serviceaccount: prometheus-k8s. This only works for OpenShift environmentments.

Describe the solution you'd like:
Extend the Operator config with the same properties of the KubeVirt config as described here.

Describe alternatives you've considered:
As a workaround we configured a manual rolebinding to match our environment, but we would like to do this using the operator.

Additional context:
Add any other context or screenshots about the feature request here.

[akalenyu]

there's an operator environment variable MONITORING_NAMESPACE if that helps. we only default to "monitoring" if that is unspecified

containerized-data-importer/pkg/operator/controller/prometheus.go

Lines 183 to 189 in bd7d028

	func getMonitoringNamespace() string {
	if ns := os.Getenv("MONITORING_NAMESPACE"); ns != "" {
	return ns
	}
	return defaultMonitoringNs
	}

[erickuiper]

Great that we can overwrite the namespace, but the service account name is static. We use Grafana stack and allow to scrape, so we need to use the alloy service account.

containerized-data-importer/pkg/operator/controller/prometheus.go

Lines 173 to 177 in b6b7468

	Subjects: []rbacv1.Subject{
	{
	Kind: "ServiceAccount",
	Namespace: monitoringNamespace,
	Name: "prometheus-k8s",

[akalenyu]

In that case we could extend the env vars (would really prefer to avoid bloating the API for that)

[erickuiper]

I'm ok with using environment variables if I can apply them as part of the operator spec. The reason for proposing the API extension is only to align with the kubevirt operator.

…

On Wed, Jun 25, 2025 at 11:53 AM Alex Kalenyuk ***@***.***> wrote: *akalenyu* left a comment (kubevirt/containerized-data-importer#3800) <#3800 (comment)> In that case we could extend the env vars (would really prefer to avoid bloating the API for that) — Reply to this email directly, view it on GitHub <#3800 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APNUT6LSX6JF6ZHBC7B65LT3FJWRLAVCNFSM6AAAAACACTB7R6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTAMBUGE2TGNRTGM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[kubevirt-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale