-
Notifications
You must be signed in to change notification settings - Fork 2
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
[Merged by Bors] - Bugfix for: Druid connection not established #187
Conversation
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.
Just one thing (not sure if that applies, but i think it could make things easier)
762926b
to
6e9c4f6
Compare
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.
Approved as soon as the open comments of @maltesander are done.
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.
Some small things:
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.
LGTM.
bors merge |
## Description Fixes #174 A test for the bug is found in this PR https://github.com/stackabletech/integration-tests/pull/235 - the DruidConnection controller now watches the ConfigMaps, to be notified if a druid instance that should be connected is deployed; to connect it then. - the DruidConnnection namespaces are also made optional in this PR
Pull request successfully merged into main. Build succeeded: |
Description
Fixes #174
A test for the bug is found in this PR https://github.com/stackabletech/integration-tests/pull/235
Review Checklist
Once the review is done, comment
bors r+
(orbors merge
) to merge. Further information