squakez commented on issue #4396: URL: https://github.com/apache/camel-k/issues/4396#issuecomment-1572006338
Steps to reproduce from a clean cluster state: ``` $ kamel install # version 1.12.0 $ kamel install --operator-image=camelk/camel-k:1.12.1 --maven-repository=https://repository.apache.org/content/repositories/orgapachecamel-1565 --olm=false --force # version 1.12.1 $ kamel run /tmp/Test.java Integration "test" created $ stern camel-k-operator .... camel-k-operator-65d8657fff-4s6hb camel-k-operator {"level":"info","ts":1685624071.3318849,"logger":"camel-k.controller.build","msg":"Maximum number of running builds (0) exceeded - the build gets enqueued","request-namespace":"default","request-name":"test","max-running-builds-limit":0,"api-version":"camel.apache.org/v1","kind":"Build","ns":"default","name":"kit-chs9a1ven07s73abbl80"} ``` Probably the fact you're using a global installation mode is the reason why this is not thrown on your side. -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org
