Help getting started with tiny-cluster

[mmynk]

Hi, I am trying to set up druid-operator in minikube (for now) which is running on an EC2.

Here's what I have done:

cd druid-operator
git checkout -b v1.0.0 v1.0.0

k create ns druid-ns
k config set-context --current --namespace=druid-ns

k create -f deploy/service_account.yaml
k create -f deploy/role.yaml
k create -f deploy/role_binding.yaml
k create -f deploy/crds/druid.apache.org_druids.yaml
k create -f deploy/operator.yaml

# k apply -f examples/tiny-cluster-zk.yaml
k apply -f examples/tiny-cluster.yaml

I initially started with https://github.com/datainfrahq/druid-operator/blob/master/docs/getting_started.md but that was not bringing up all the services for me but the above did.

Now I wish to access the web console.

Here's the output of k get all:

$ k get all
NAME                                    READY   STATUS             RESTARTS        AGE
pod/druid-operator-7ccbfc66b-2mm7q      1/1     Running            0               6m36s
pod/druid-tiny-cluster-brokers-0        0/1     Running            1 (2m49s ago)   6m30s
pod/druid-tiny-cluster-coordinators-0   0/1     Running            3 (69s ago)     6m30s
pod/druid-tiny-cluster-historicals-0    0/1     CrashLoopBackOff   5 (2m26s ago)   6m30s
pod/druid-tiny-cluster-routers-0        1/1     Running            0               6m30s

NAME                                      TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)    AGE
service/druid-tiny-cluster-brokers        ClusterIP   None         <none>        8088/TCP   6m30s
service/druid-tiny-cluster-coordinators   ClusterIP   None         <none>        8088/TCP   6m30s
service/druid-tiny-cluster-historicals    ClusterIP   None         <none>        8088/TCP   6m30s
service/druid-tiny-cluster-routers        ClusterIP   None         <none>        8088/TCP   6m30s

NAME                             READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/druid-operator   1/1     1            1           6m36s

NAME                                       DESIRED   CURRENT   READY   AGE
replicaset.apps/druid-operator-7ccbfc66b   1         1         1       6m36s

NAME                                               READY   AGE
statefulset.apps/druid-tiny-cluster-brokers        0/1     6m30s
statefulset.apps/druid-tiny-cluster-coordinators   0/1     6m30s
statefulset.apps/druid-tiny-cluster-historicals    0/1     6m30s
statefulset.apps/druid-tiny-cluster-routers        1/1     6m30s

I tried running:

k port-forward service/druid-tiny-cluster-routers --address 0.0.0.0 8888:8088

And then tried to access the console using http://ec2-public-ip:8888 but that did not work.

I am pretty sure I'm doing something wrong but I am a k8s beginner so any help would be really great.

[mmynk]

Okay, looks like the issue was with the SG attached to the EC2.
However, I'd be interested in understanding why the router service doesn't come when using the getting_started.md instruction.

[AdheipSingh]

getting started is an example of writing druid CR configs.
You can check this for router config here

[mmynk]

Oh okay, I tried using the e2e/config but I am still struggling. If it's not a lot of effort, could you give me the steps on a high level how I can deploy a druid operator (with router) on, say GKE. As in what configs would I need to apply , or do I need to write my own CRD.
Thanks a lot!