[WIP] Add monitoring controller for COO (Cluster Observability Operator)

[mayleighnmyers]

Implements a monitoring controller that creates ServiceMonitor and PodMonitor resources for IstioRevision objects. Key features:

• Uses monitoring.rhobs/v1 API group for COO compatibility
• Adds 'monitored-by: coo-prometheus' label for COO discovery
• Creates ServiceMonitor (default-istiod) for istiod metrics
• Creates PodMonitor (default-proxies) for istio-proxy metrics
• Sets proper owner references for automatic cleanup

Relates to: OSSM-13585

What type of PR is this?

• Enhancement / New Feature
• Bug Fix
• Refactor
• Optimization
• Test
• Documentation Update

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

Related Issue/PR #

Additional information:

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: mayleighnmyers / name: Mayleigh Tjapkes (42511f0, 4adeec0, 95feca9, b1cd237, c4cbbf0, e8bfa31)
• ✅ login: yxun / name: Yuanlin Xu (63ec0fe)

[istio-testing]

Hi @mayleighnmyers. Thanks for your PR.

I'm waiting for a istio-ecosystem or istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[istio-testing]

PR needs rebase.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[nrfox]

Hi @mayleighnmyers,

How would users control this if they wanted to opt in or out? What will the API be for this? You can either open an issue and we can discuss it there or better yet create a SEP for this. We need to discuss how this will integrate with the operator before we can move forward with this.

[mayleighnmyers]

Hi @mayleighnmyers,

How would users control this if they wanted to opt in or out? What will the API be for this? You can either open an issue and we can discuss it there or better yet create a SEP for this. We need to discuss how this will integrate with the operator before we can move forward with this.

So this is still in progress. Good call for the opt in/out. Something we can consider is adding a field either in the Istio CR or the istioRevision CR to allow users to opt in since right now it is currently always enabled. Yuanlin and I will be talking about this more in some future meeting when we have all ducks in a row. :)