Evynglais opened a new issue, #6014:
URL: https://github.com/apache/camel-k/issues/6014

   ### What happened?
   
   Using the Prometheus trait with a Knative Camel-K integration results in an 
invalid PodMonitor configuration (a port that doesn't exist).
   
   ### Steps to reproduce
   
   1. Deploy a Camel-K integration as a Knative service, with `--trait 
prometheus.enabled=true`.
   ```yaml
   kamel run "${SCRIPT_DIR}"/pre.ingress.camel.yaml --name pre-ingress \
       --trait knative-service.min-scale=1 \
       --trait prometheus.enabled=true \
       --property quarkus.kubernetes-config.enabled=true \
       --property quarkus.kubernetes-config.config-maps=pre.ingress.ibm.config
   ```
   2. Observe the target group on Prometheus; it will be empty.
   
![image](https://github.com/user-attachments/assets/713b982a-2b01-4f73-92f3-761c1a7dfe32)
   3. Observe the podmonitor created by Camel-K; it will reference port 'h2c' 
which doesn't exist.
   
![image](https://github.com/user-attachments/assets/81e4a75b-9fdb-4f88-8369-12518237af6a)
   
   Actual ports:
   
![image](https://github.com/user-attachments/assets/eb9a5811-6c4e-48d2-aa0d-78826ce45cb6)
   
![image](https://github.com/user-attachments/assets/adf0dcd7-0a28-4a9b-9448-afb49b4d7806)
   
   
   
   ### Relevant log output
   
   _No response_
   
   ### Camel K version
   
   2.5.0


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to