You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There may be an optional field where we may specify the number of replicas and the containers will be dynamically spun up and assigned port and container names, with all the environment variables required for coordination injected. The wait hook may also configurable waiting for either master, or all replicas to stabilize.
The text was updated successfully, but these errors were encountered:
Hi, is there any particular use case that you are trying to handle?
From my perspective, if some Go code relies on kafka, it doesn't really care if it runs in a cluster or not.
Of course if there is some value in running a cluster of kafka or rabbitmq instances, I support this idea. Would you like to work on it?
Services such as kafka, rabbitmq can be run using multiple replicas.
For example cp-kafka with kraft
There may be an optional field where we may specify the number of replicas and the containers will be dynamically spun up and assigned port and container names, with all the environment variables required for coordination injected. The wait hook may also configurable waiting for either master, or all replicas to stabilize.
The text was updated successfully, but these errors were encountered: