-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for multiple kafka brokers #881
Conversation
Signed-off-by: Chris Mitchell <cmitchel@redhat.com>
/retest |
Signed-off-by: Chris Mitchell <cmitchel@redhat.com>
/retest |
Signed-off-by: Chris Mitchell <cmitchel@redhat.com>
/retest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. The old test-kafka-managed
is making sure the plain old hostname
key still works... and test-kafka-managed-multibroker
is validating the new plural hostnames
key works.
Sup! When can we expected to see a new release with this? |
This was released to stage last Friday (but we haven't tagged a new official release on github yet) |
Ok let us know when we can actually start upgrading dependencies and trying it out on stage. Thanks. |
Which dependencies do you need to upgrade? I would expect that you actually should not need to change dependencies because the cdappconfig schema did not change. Clowder is sending 3 broker configurations to apps in stage already. |
Oh I thought a clowder bump is needed, disregard then. Thanks. |
This allows a
hostnames
key to be defined in the managed kafka secret as a comma,separated,list of broker hostnames. If it is defined, the cdappconfig's BrokerConfig array will contain all the possible broker hostnames that a client can connect to.If the
hostnames
key is not found, then we fall back to looking for thehostname
key as we have always done and only have a single BrokerConfig in the array.