Closed nullptr0000 closed 11 months ago
Thanks for reporting! The resolution of ports was indeed wrong. This is caused by the definition of this mapping by Quarkus/Dekorate. For now, https://github.com/quarkiverse/quarkus-helm/pull/296 should fix it.
Using Quarkus 3.5.0 or 3.5.1, and Quarkus-Helm 1.2.0
If a project is built with the option 'quarkus.management.enabled=true', the deployment.yaml generated is malformed, including a spurious ' | quote' against one port value, and only linking one out of the three probes to the management port.
The management port definition is correctly created, as is the value, and the startupProbe is linked to it so something is at least attempting to process it correctly.
The Quarkus generated kubernetes.yml elsewhere has the expected values. If the management port option is disabled the deployment.yaml is generated without any spurious ' | quote', and obviously without any references to the management port.
Generated yaml snippet:
Expected yaml snippet: