Duplicate prometheus port in cluster template

[bhampl]

/kind bug

What steps did you take and what happened:
I followed the Getting Started documentation in combination with the cluster API operator.

After applying a generated cluster (with the node-ipam flavor) I get the following warning in the capi-controller-manager log:

warning_handler.go:65] "spec.template.spec.containers[4].ports[0]: duplicate port name \"prometheus\" with spec.template.spec.containers[2].ports[1], services and probes that select ports by name will use spec.template.spec.containers[2].ports[1]" logger="KubeAPIWarningLogger"

What did you expect to happen:
There to be no warning and no duplicate prometheus ports definition.

Anything else you would like to add:
The reason for the warning is the duplicate prometheus port definition in the vsphere-csi-controller Deployment located in the csi-manifests ConfigMap of the cluster-template.yaml:

cluster-api-provider-vsphere/templates/cluster-template.yaml

Lines 815 to 817 in 7cc3899

	- containerPort: 2112
	name: prometheus
	protocol: TCP

cluster-api-provider-vsphere/templates/cluster-template.yaml

Lines 861 to 864 in 7cc3899

	ports:
	- containerPort: 2113
	name: prometheus
	protocol: TCP

The cluster-template-node-ipam.yaml has the same problem, I haven't checked the other templates.

Environment:

• Cluster-api-provider-vsphere version: v1.13.0
• Kubernetes version: (use kubectl version): v1.33.1
• OS (e.g. from /etc/os-release): Ubuntu 24.04

[sbueringer]

Thx for reporting, I opened a corresponding issue in CSI: kubernetes-sigs/vsphere-csi-driver#3385

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten