update: monitoring stack only apply if it is managed cluster + do not create monitoring namespace for non-Managed offering

[zdtsw]

Description

• keep managed cluster logic as-is
• create redhat-ods-monitoring namespace only for managed cluster if dsci set monitoring to enabled (in most case / default case this will be enabled)
• remove existing role rolebinding and servicemonitor during upgrade if it is self-managed : as cleanup from previous releases
• keep redhat-ods-monitroing namespace in self-managed if it has been created from previous release
• do not apply role rolebinding networkpolicy and servicemonitor in clean install for self-managed, should only be done if it is managed cluster

ref: https://issues.redhat.com/browse/RHOAIENG-2761

partially related to https://issues.redhat.com/browse/RHOAIRFE-422
so we do not need to consider monitoring case

How Has This Been Tested?

Screenshot or short clip

Merge criteria

• You have read the contributors guide.
• Commit messages are meaningful - have a clear and concise summary and detailed explanation of what was changed and why.
• Pull Request contains a description of the solution, a link to the JIRA issue, and to any dependent or related Pull Request.
• Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
• The developer has manually tested the changes and verified that the changes work

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from zdtsw. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 12 lines in your changes missing coverage. Please review.

Please upload report for BASE (incubation@0b4b1f4). Learn more about missing BASE report.

Files with missing lines	Patch %	Lines
controllers/dscinitialization/utils.go	0.00%	7 Missing and 1 partial ⚠️
.../dscinitialization/dscinitialization_controller.go	0.00%	4 Missing ⚠️

Additional details and impacted files

@@              Coverage Diff              @@
##             incubation    #1321   +/-   ##
=============================================
  Coverage              ?   18.28%           
=============================================
  Files                 ?       30           
  Lines                 ?     3391           
  Branches              ?        0           
=============================================
  Hits                  ?      620           
  Misses                ?     2703           
  Partials              ?       68           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[VaishnaviHire]

Do we know if other components do not reference or use this in self-managed as part of workload-monitoring?

[zdtsw]

Do we know if other components do not reference or use this in self-managed as part of workload-monitoring?

i do not believe any component is using redhat-ods-monitoring namespace but let me get confirm from teams first.

[zdtsw]

Do we know if other components do not reference or use this in self-managed as part of workload-monitoring?

asked here: https://redhat-internal.slack.com/archives/C05NXTEHLGY/p1731914889336659
component confirmed they do not use it