Add monitoring port names to the harbor component deployments.

[rikuwe-christian-rieger]

We use grafana alloy with its pod discovery feature, it is way easier to identify the metrics ports if they are correctly named in the manifests.

[MinerYang]

Hi @rikuwe-christian-rieger ,

Thanks for connecting with us.
I am not familiar with pod discovering feature, when grafana enable pod discovery feature, is the container-port necessarily set?

[rikuwe-christian-rieger]

Hi @MinerYang,

We are using the monitoring scraping tool "alloy" from Grafana.
Alloy has a feature which is used to connect to the k8s api and retrieves all of the pods(discovery.kubernetes).
We then filter for all of the container ports which are named after something monitoring related e.g. "metrics" | "monitoring".
If there is no container port definition the auto port discovery does not work.
I figured you would welcome the additional definition for the container ports, because they are used in the service without explicit definition.