Add custom podTemplate docs

Signed-off-by: Tapajit Chandra Paul <[email protected]>

docs/guides/druid/configuration/guide.md → docs/guides/druid/configuration/config-file/index.md

@@ -2,7 +2,7 @@
 title: Configuring Druid Cluster
 menu:
   docs_{{ .version }}:
-    identifier: guides-druid-configuration-druid-cluster
+    identifier: guides-druid-configuration-config-file
     name: Configuration File
     parent: guides-druid-configuration
     weight: 10
@@ -134,7 +134,7 @@ stringData:
 ```
 
 ```bash
-$ kubectl apply -f https://github.com/kubedb/docs/raw/{{< param "info.version" >}}/docs/guides/druid/configuration/yamls/config-secret.yaml
+$ kubectl apply -f https://github.com/kubedb/docs/raw/{{< param "info.version" >}}/docs/guides/druid/configuration/config-file/yamls/config-secret.yaml
 secret/config-secret created
 ```
 
@@ -170,7 +170,7 @@ spec:
 Now, create the Druid object by the following command:
 
 ```bash
-$ kubectl apply -f https://github.com/kubedb/docs/raw/{{< param "info.version" >}}/docs/guides/druid/configuration/yamls/druid-with-monitoring.yaml
+$ kubectl apply -f https://github.com/kubedb/docs/raw/{{< param "info.version" >}}/docs/guides/druid/configuration/config-file/yamls/druid-with-monitoring.yaml
 druid.kubedb.com/druid-with-config created
 ```
 
@@ -256,7 +256,7 @@ Now hit the `http://localhost:8888` from any browser, and you will be prompted t
 After providing the credentials correctly, you should be able to access the web console like shown below.
 
 <p align="center">
-  <img alt="lifecycle"  src="/docs/guides/druid/reconfigure/images/druid-updated-ui.png">
+  <img alt="druid-ui"  src="/docs/guides/druid/configuration/config-file/images/druid-updated-ui.png">
 </p>
 
 

docs/guides/druid/configuration/podtemplating/yamls/deep-storage-config.yaml

@@ -0,0 +1,16 @@
+apiVersion: v1
+kind: Secret
+metadata:
+  name: deep-storage-config
+  namespace: demo
+stringData:
+  druid.storage.type: "s3"
+  druid.storage.bucket: "druid"
+  druid.storage.baseKey: "druid/segments"
+  druid.s3.accessKey: "minio"
+  druid.s3.secretKey: "minio123"
+  druid.s3.protocol: "http"
+  druid.s3.enablePathStyleAccess: "true"
+  druid.s3.endpoint.signingRegion: "us-east-1"
+  druid.s3.endpoint.url: "http://myminio-hl.demo.svc.cluster.local:9000/"
+

docs/guides/druid/configuration/podtemplating/yamls/druid-cluster.yaml

@@ -0,0 +1,43 @@
+apiVersion: kubedb.com/v1alpha2
+kind: Druid
+metadata:
+  name: druid-cluster
+  namespace: demo
+spec:
+  version: 28.0.1
+  configSecret:
+    name: config-secret
+  deepStorage:
+    type: s3
+    configSecret:
+      name: deep-storage-config
+  topology:
+    coordinators:
+      replicas: 1
+      podTemplate:
+        spec:
+          containers:
+            - name: druid
+              resources:
+                limits:
+                  memory: "2Gi"
+                  cpu: "600m"
+                requests:
+                  memory: "2Gi"
+                  cpu: "600m"
+    brokers:
+      replicas: 1
+      podTemplate:
+        spec:
+          containers:
+            - name: druid
+              resources:
+                limits:
+                  memory: "2Gi"
+                  cpu: "600m"
+                requests:
+                  memory: "2Gi"
+                  cpu: "600m"
+    routers:
+      replicas: 1
+  deletionPolicy: WipeOut

docs/guides/druid/configuration/podtemplating/yamls/druid-node-selector.yaml

@@ -0,0 +1,20 @@
+apiVersion: kubedb.com/v1alpha2
+kind: Druid
+metadata:
+  name: druid-node-selector
+  namespace: demo
+spec:
+  version: 28.0.1
+  deepStorage:
+    type: s3
+    configSecret:
+      name: deep-storage-config
+  topology:
+    routers:
+      replicas: 1
+    coordinators:
+      podTemplate:
+        spec:
+          nodeSelector:
+            disktype: ssd
+  deletionPolicy: Delete

docs/guides/druid/configuration/podtemplating/yamls/druid-with-tolerations.yaml

@@ -0,0 +1,58 @@
+apiVersion: kubedb.com/v1alpha2
+kind: Druid
+metadata:
+  name: druid-cluster
+  namespace: demo
+spec:
+  version: 28.0.1
+  deepStorage:
+    type: s3
+    configSecret:
+      name: deep-storage-config
+  topology:
+    routers:
+      podTemplate:
+        spec:
+          tolerations:
+            - key: "key1"
+              operator: "Equal"
+              value: "node1"
+              effect: "NoSchedule"
+      replicas: 1
+    coordinators:
+      podTemplate:
+        spec:
+          tolerations:
+            - key: "key1"
+              operator: "Equal"
+              value: "node1"
+              effect: "NoSchedule"
+      replicas: 1
+    brokers:
+      podTemplate:
+        spec:
+          tolerations:
+            - key: "key1"
+              operator: "Equal"
+              value: "node1"
+              effect: "NoSchedule"
+      replicas: 1
+    historicals:
+      podTemplate:
+        spec:
+          tolerations:
+            - key: "key1"
+              operator: "Equal"
+              value: "node1"
+              effect: "NoSchedule"
+      replicas: 1
+    middleManagers:
+      podTemplate:
+        spec:
+          tolerations:
+            - key: "key1"
+              operator: "Equal"
+              value: "node1"
+              effect: "NoSchedule"
+      replicas: 1
+  deletionPolicy: Delete

docs/guides/druid/configuration/podtemplating/yamls/druid-without-tolerations.yaml

@@ -0,0 +1,15 @@
+apiVersion: kubedb.com/v1alpha2
+kind: Druid
+metadata:
+  name: druid-without-tolerations
+  namespace: demo
+spec:
+  version: 28.0.1
+  deepStorage:
+    type: s3
+    configSecret:
+      name: deep-storage-config
+  topology:
+    routers:
+      replicas: 1
+  deletionPolicy: Delete

docs/guides/druid/reconfigure/guide.md

@@ -678,7 +678,7 @@ You can access the UI similarly by doing port-forward as mentioned in [Check Con
 You should be able to see the following changes in the UI:
 
 <p align="center">
-  <img alt="lifecycle"  src="/docs/guides/druid/reconfigure/images/druid-updated-ui.png">
+  <img alt="lifecycle"  src="/docs/guides/druid/configuration/config-file/images/druid-updated-ui.png">
 </p>
 
 You can see that there are 5 task slots reflecting with our provided custom configuration of `druid.worker.capacity=5`.

docs/guides/druid/scaling/vertical-scaling/yamls/druid-cluster.yaml

@@ -13,4 +13,3 @@ spec:
     routers:
       replicas: 1
   deletionPolicy: Delete
-