Fix Incorrect Kubernetes Port Annotation for Management Interface

[BrunoSena97]

resolves #37904

Changes include:

• Updated the createAnnotations method in the KindProcessor class to check if the management interface is enabled and if the annotation key is "prometheus.io/port".
• If both conditions are true, the method now produces a new KubernetesAnnotationBuildItem with the key k, the value managementPort, and the target KIND.
• Otherwise, it produces a new KubernetesAnnotationBuildItem with the key k, the value v, and the target KIND.

[gsmet]

@iocanel could you have a look at this one?

[iocanel]

Thank you very much for taking a stub at it.

Is there a reason why this is specific to kind. My understanding is that this is something that should be applied to all targets and not just kind. So, I think that a better place for this might be somewhere around here:

quarkus/extensions/kubernetes/vanilla/deployment/src/main/java/io/quarkus/kubernetes/deployment/KubernetesCommonHelper.java

Line 1006 in b8e7635

metricsConfiguration.ifPresent(m -> {

.

More specifically, I would just ensure that this line:

quarkus/extensions/kubernetes/vanilla/deployment/src/main/java/io/quarkus/kubernetes/deployment/KubernetesCommonHelper.java

Line 1026 in b8e7635

config.getPrometheusConfig().port.orElse(prefix + "/port"), "" + port.get().getContainerPort(),

uses the right port.

Finally, we definitely need an integration test for this. Do let me know if you need a pointer for that.

[gsmet]

@BrunoSena97 are you willing to pursue this? Thanks!

[cescoffier]

@BrunoSena97 Are you having a look to @iocanel 's review?

[cescoffier]

@iocanel What should be do here? Do we want this feature?

[iocanel]

@cescoffier: I think that we do. I would keep this open, just in case someone will pick this up.