Clarify metrics collection from typha in operator based installations

We want to follow https://docs.tigera.io/calico/latest/operations/monitor/monitor-component-metrics and noticed that the operator already creates a service called calico-typha-metrics when we set typhaMetricsPort in our Installation resource. This operator managed service is different from the one defined in https://docs.tigera.io/calico/latest/operations/monitor/monitor-component-metrics#creating-a-service-to-expose-typha-metrics and we are wondering which one to use?

Expected Behavior

Operator should not create the service? Or documentation should not specify that we are supposed to create it ourself?

Current Behavior

Operator creates a service and we are creating one following the documentation.

Possible Solution

Update documentation so that it points out that the operator creates services for calico-typha-metrics.

Since the operator already creates a service for calico-kube-controllers-metrics as well, it would be even nicer if it would create one for felix as well?

Steps to Reproduce (for bugs)

1. Install calico w/ operator
2. Follow guide at https://docs.tigera.io/calico/latest/operations/monitor/monitor-component-metrics
3. Call kubectl --namespace calico-system get services
4. See services called calico-typha-metrics (operator managed) and typha-metrics-svc (self-managed)

Context

Everything works fine, we just spend some time on figuring out what is happening.

Your Environment

• Calico version: 3.30.2
• Calico dataplane (bpf, nftables, iptables, windows etc.): iptables
• Orchestrator version (e.g. kubernetes, openshift, etc.): kubernetes
• Operating System and version: Ubuntu 24.04
• Link to your project (optional):