- 
                Notifications
    
You must be signed in to change notification settings  - Fork 70
 
Description
Problem
As far as I can tell, when creating a broker with RabbitmqBrokerConfig, there is no way to specify the replica count of the ingress-broker deployment.
This means that if my autoscaling decides to move the pod to a different node, I cannot send cloudevents during that time.
This can easily be solved by adding a parameter to the broker type or to the configuration.
As far as I can tell from looking a bit at the code, there is no reason multiple pods cannot act together (as all they do is send messages to the rabbit).
As far as I can tell, none of the brokers today have any option for scaling the ingress.
Exit Criteria
The ability to set number of replicas in the deployment generated by the Broker
Additional context (optional)
I might be missing some configuration option, for now I am manually updating the deployment count of the ingress and hoping that it won't get restored when I'm not looking