ansh0014 commented on issue #6858: URL: https://github.com/apache/camel-k/issues/6858#issuecomment-6313719053
Hi @squakez , To make sure we are fully aligned on the 3.x redesign before diving into the code, here is the proposal I am thinking: 1. **Remove `scheduleAction` & in-memory state:** Remove `sync.Mutex` and the in-memory `runningBuilds` map so the controller is fully stateless. 2. **Poll running builds directly:** Count active builds/pods directly from the client against the configured limit (`MAX_RUNNING_BUILDS` / `MAX_PIPELINES`). 3. **Quiet requeue:** Avoid spamming the `"enqueued"` message at `Info` level on every 5s loop, and only set the waiting condition once. To make sure everything is properly thought out and clear, I'd like to first document this architecture (or open a docs PR), and once we agree on the design, I'll proceed with the code implementation. Does this plan sound good to you? -- 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]
