update: remove two SA which does not seem valid

[zdtsw]

Description

https://issues.redhat.com/browse/RHOAIENG-13411

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

[VaishnaviHire]

Is this something that was added for user workload monitoring?

[zdtsw]

should not be, in odh 2.0.0 alread have these

opendatahub-operator/components/modelmeshserving/modelmeshserving.go

Line 40 in 2329956

err := common.UpdatePodSecurityRolebinding(cli, []string{"modelmesh", "modelmesh-controller", "odh-model-controller", "odh-prometheus-operator", "prometheus-custom"}, namespace)

[zdtsw]

@VedantMahabaleshwarkar if you know this ^?

[VedantMahabaleshwarkar]

should be fine to remove odh-prometheus-operator and prometheus-custom IIRC. But it's been a while, if there is a way to ensure the SRE stack (for managed RHOAI) is working for modelmesh alerts with this change then it should be fine. I'm 90% certain these aren't needed for the SRE stack but it would be good to get that confirmation.

[zdtsw]

we could do a downstream build and let QE test on a managed cluster, see how it goes