WIP: refactor: refactor monitoring session

[capri-xiyue]

What type of PR is this?

/kind cleanup

What this PR does / why we need it:
gke needs to be removed in monitoring session

Which issue(s) this PR fixes:

Fixes #

Does this PR introduce a user-facing change?:

there is no `inferenceExtension.monitoring.gke` in `inferencePool` helm chart

[netlify]

✅ Deploy Preview for gateway-api-inference-extension ready!

Name	Link
🔨 Latest commit	67a1f40
🔍 Latest deploy log	https://app.netlify.com/projects/gateway-api-inference-extension/deploys/69273793c7f5620008bc94f4
😎 Deploy Preview	https://deploy-preview-1906--gateway-api-inference-extension.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: capri-xiyue
Once this PR has been reviewed and has the lgtm label, please assign ahg-g for approval. For more information see the 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

[liu-cong]

cc @JeffLuoo Did we decide to deprecate monitoring.gke.enabled and use provider:gke to enable GKE monitoring?

@capri-xiyue Note we set monitoring.gke in llm-d user guides today, but I assume deprecating it just means monitoring.gke becomes a noop right?

[liu-cong]

note this is only used in GKE (and therefore it was in gke.yaml)

[nirrozenbaum]

+1. for resources that are gke specific, it's preferred to have it in a separate gke.yaml file.
now we just need to change the conditional, so instead of checking gke.enabled, we might check for provider.name == gke

[ahg-g]

cc @JeffLuoo Did we decide to deprecate monitoring.gke.enabled and use provider:gke to enable GKE monitoring?

Yes, there is already a deprecation note. We need to update the guides in GKE, the previous release now supports both, so we can safely migrate the guide.