-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Create a travis build that runs Druid on a K8S Cluster and runs the integration tests #10542
Comments
@himanshug can help here, i have been testing on kind on travis, plus we can use the same way druid-io/druid-operator#57 , i guess once we get this finalized. |
it should be added as a new job in https://github.com/apache/druid/blob/master/.travis.yml , so travis would run it automatically on each PR
something along the lines of...
AFTER above is done, as a follow up we will change above Druid cluster configuration to not use Zookeeper and remove the Zookeeper StatefulSet part. |
Hi @himanshug Our Dev, Stg and Prd Druid clusters are all deployed on K8s using Helm Chart. Maybe I can do some help for this great work. What we have done is that K8s + tiller(optional) + helmChart(including ZK statefulset) but do not use |
I wouldn't say I have something ready :) , but I have done following many many times in remote k8s clusters...
so, I could get those done somewhat easily if needed. I am guessing, So, most important step missing is setting up a k8s cluster in travis build env that has enough resources to run a Druid cluster which can handle the things we do in integration tests. |
Understood! Although I am not very familiar with |
In the end state, I would prefer the operator. |
Hi @himanshug , I just make a PR #10669.
Now job PTAL :) |
thanks, yeah I will review that. |
Currently we have many different travis builds that setup a single node druid cluster and run integration tests.
This issue is to have one more that sets up the Druid cluster inside a K8S cluster (maybe using https://github.com/druid-io/druid-operator ) and runs some of the integration tests.
Once above setup exists, as a follow up, it would be modified to run Druid without Zookeeper for continuous integration testing of ability to run Druid without Zookeeper(see #9053 ) inside K8S Cluster.
The text was updated successfully, but these errors were encountered: