Details
-
Task
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
Unknown
Description
In Camel K we need to distinguish active from passive endpoints in order to determine when a integration can be scaled down to 0.
E.g.
- a "timer" (start) endpoint is active, because it needs to have a JVM always running and do something at each interval
- a "jms" (start) endpoint is active because it needs to establish a connection to the broker and keep it alive
- a "direct" or "seda" endpoint is passive, because they do something when they receive an exchange from another route
- a "undertow" (start) endpoint is passive, because it does nothing until somebody calls it from an external service (http based endpoints can all be considered passive in Knative+CamelK)
We should add this information to the catalog. Now I've embedded it in Camel K.