lburgazzoli opened a new issue, #5467: URL: https://github.com/apache/camel-k/issues/5467
### What happened? The [maven_command](https://github.com/apache/camel-k/blob/37fb7043855f895a269f939518f93eb0e6534725/pkg/util/maven/maven_command.go) sets mavne's artifact and execution threads to the value of `GOMAXPROCS` however, The Go runtime doesn’t know it’s running in k8s hence, `GOMAXPROCS` reports the number of cores on the node: https://github.com/apache/camel-k/blob/37fb7043855f895a269f939518f93eb0e6534725/pkg/util/maven/maven_command.go#L92-L98 This seems to be wrong an could potential lead to misbehavior as `maven` is configured to use more resources than what is actually available for the `Pod`. ### Steps to reproduce 1. start minikube with i.e. half of the cores available 2. observe an integration build logs 3. you should see that the maven's `-T` flag has a value greater than the number of the configured cores ### Relevant log output _No response_ ### Camel K version _No response_ -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
