Skip to content

Update druid docs examples to latest supported version (36.0.0) #915

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.

Sign up for GitHub

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

Open
tamalsaha wants to merge 4 commits into
base: master
Choose a base branch
from
Open

Update druid docs examples to latest supported version (36.0.0) #915

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
97e7e34
Update druid docs examples to latest supported version (36.0.0)
tamalsaha Jun 30, 2026
c2ee10b
ready
fr-sarker Jun 30, 2026
8409185
Merge branch 'master' into update-druid-docs-version
fr-sarker Jun 30, 2026
dc819eb
fix version mismatch
fr-sarker Jul 2, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/examples/druid/quickstart/druid-quickstart.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ metadata:
name: druid-quickstart
namespace: demo
spec:
version: 28.0.1
version: 36.0.0
deepStorage:
type: s3
configuration:
Expand Down
14 changes: 7 additions & 7 deletions docs/guides/druid/autoscaler/compute/guide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -91,11 +91,11 @@ $ kubectl create -f https://github.com/kubedb/docs/raw/{{< param "info.version"
secret/deep-storage-config created
```

Now, we are going to deploy a `Druid` combined cluster with version `28.0.1`.
Now, we are going to deploy a `Druid` combined cluster with version `36.0.0`.

### Deploy Druid Cluster

In this section, we are going to deploy a Druid Topology cluster with version `28.0.1`. Then, in the next section we will set up autoscaling for this database using `DruidAutoscaler` CRD. Below is the YAML of the `Druid` CR that we are going to create,
In this section, we are going to deploy a Druid Topology cluster with version `36.0.0`. Then, in the next section we will set up autoscaling for this database using `DruidAutoscaler` CRD. Below is the YAML of the `Druid` CR that we are going to create,

```yaml
apiVersion: kubedb.com/v1alpha2
Expand All @@ -104,7 +104,7 @@ metadata:
name: druid-cluster
namespace: demo
spec:
version: 28.0.1
version: 36.0.0
deepStorage:
type: s3
configSecret:
Expand All @@ -125,13 +125,13 @@ druid.kubedb.com/druid-cluster created
Now, wait until `druid-cluster` has status `Ready`. i.e,

```bash
$ kubectl get kf -n demo -w
$ kubectl get dr -n demo -w
NAME TYPE VERSION STATUS AGE
druid-cluster kubedb.com/v1alpha2 28.0.1 Provisioning 0s
druid-cluster kubedb.com/v1alpha2 28.0.1 Provisioning 24s
druid-cluster kubedb.com/v1alpha2 36.0.0 Provisioning 0s
druid-cluster kubedb.com/v1alpha2 36.0.0 Provisioning 24s
.
.
druid-cluster kubedb.com/v1alpha2 28.0.1 Ready 118s
druid-cluster kubedb.com/v1alpha2 36.0.0 Ready 118s
```

## Druid Topology Autoscaler
Expand Down
2 changes: 1 addition & 1 deletion docs/guides/druid/autoscaler/compute/yamls/druid-cluster.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ metadata:
name: druid-cluster
namespace: demo
spec:
version: 28.0.1
version: 36.0.0
deepStorage:
type: s3
configSecret:
Expand Down
10 changes: 5 additions & 5 deletions docs/guides/druid/autoscaler/storage/guide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -109,7 +109,7 @@ secret/deep-storage-config created

### Deploy Druid Cluster

In this section, we are going to deploy a Druid topology cluster with monitoring enabled and with version `28.0.1`. Then, in the next section we will set up autoscaling for this cluster using `DruidAutoscaler` CRD. Below is the YAML of the `Druid` CR that we are going to create,
In this section, we are going to deploy a Druid topology cluster with monitoring enabled and with version `36.0.0`. Then, in the next section we will set up autoscaling for this cluster using `DruidAutoscaler` CRD. Below is the YAML of the `Druid` CR that we are going to create,

```yaml
apiVersion: kubedb.com/v1alpha2
Expand All @@ -118,7 +118,7 @@ metadata:
name: druid-cluster
namespace: demo
spec:
version: 28.0.1
version: 36.0.0
deepStorage:
type: s3
configSecret:
Expand Down Expand Up @@ -166,11 +166,11 @@ Now, wait until `druid-cluster` has status `Ready`. i.e,
```bash
$ kubectl get dr -n demo -w
NAME TYPE VERSION STATUS AGE
druid-cluster kubedb.com/v1alpha2 28.0.1 Provisioning 0s
druid-cluster kubedb.com/v1alpha2 28.0.1 Provisioning 24s
druid-cluster kubedb.com/v1alpha2 36.0.0 Provisioning 0s
druid-cluster kubedb.com/v1alpha2 36.0.0 Provisioning 24s
.
.
druid-cluster kubedb.com/v1alpha2 28.0.1 Ready 2m20s
druid-cluster kubedb.com/v1alpha2 36.0.0 Ready 2m20s
```

Let's check volume size from petset, and from the persistent volume,
Expand Down
2 changes: 1 addition & 1 deletion docs/guides/druid/autoscaler/storage/yamls/druid-cluster.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ metadata:
name: druid-cluster
namespace: demo
spec:
version: 28.0.1
version: 36.0.0
deepStorage:
type: s3
configSecret:
Expand Down
2 changes: 1 addition & 1 deletion docs/guides/druid/backup/application-level/examples/sample-druid.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ metadata:
name: sample-druid
namespace: demo
spec:
version: 30.0.1
version: 36.0.0
deepStorage:
type: s3
configSecret:
Expand Down
16 changes: 8 additions & 8 deletions docs/guides/druid/backup/application-level/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -114,7 +114,7 @@ metadata:
name: sample-druid
namespace: demo
spec:
version: 30.0.1
version: 36.0.0
deepStorage:
type: s3
configSecret:
Expand Down Expand Up @@ -143,7 +143,7 @@ Let's check if the database is ready to use,
```bash
$ kubectl get druids.kubedb.com -n demo
NAME TYPE VERSION STATUS AGE
sample-druid kubedb.com/v1alpha2 30.0.1 Ready 4m14s
sample-druid kubedb.com/v1alpha2 36.0.0 Ready 4m14s
```

The database is `Ready`. Verify that KubeDB has created a `Secret` and a `Service` for this database using the following commands,
Expand Down Expand Up @@ -183,7 +183,7 @@ Verify that the `AppBinding` has been created successfully using the following c
```bash
$ kubectl get appbindings -n demo
NAME TYPE VERSION AGE
sample-druid kubedb.com/druid 30.0.1 4m7s
sample-druid kubedb.com/druid 36.0.0 4m7s
sample-druid-mysql-metadata kubedb.com/mysql 9.1.0 6m31s
sample-druid-zk kubedb.com/zookeeper 3.7.2 6m34s
```
Expand All @@ -202,7 +202,7 @@ kind: AppBinding
metadata:
annotations:
kubectl.kubernetes.io/last-applied-configuration: |
{"apiVersion":"kubedb.com/v1alpha2","kind":"Druid","metadata":{"annotations":{},"name":"sample-druid","namespace":"demo"},"spec":{"deepStorage":{"configSecret":{"name":"deep-storage-config"},"type":"s3"},"deletionPolicy":"WipeOut","topology":{"routers":{"replicas":1}},"version":"30.0.1"}}
{"apiVersion":"kubedb.com/v1alpha2","kind":"Druid","metadata":{"annotations":{},"name":"sample-druid","namespace":"demo"},"spec":{"deepStorage":{"configSecret":{"name":"deep-storage-config"},"type":"s3"},"deletionPolicy":"WipeOut","topology":{"routers":{"replicas":1}},"version":"36.0.0"}}
creationTimestamp: "2024-09-19T13:02:20Z"
generation: 1
labels:
Expand Down Expand Up @@ -236,7 +236,7 @@ spec:
secret:
name: sample-druid-admin-cred
type: kubedb.com/druid
version: 30.0.1
version: 36.0.0
```

KubeStash uses the `AppBinding` CR to connect with the target database. It requires the following two fields to be set in AppBinding's `.spec` section.
Expand Down Expand Up @@ -544,7 +544,7 @@ apiVersion: storage.kubestash.com/v1alpha1
kind: Snapshot
metadata:
annotations:
kubedb.com/db-version: 30.0.1
kubedb.com/db-version: 36.0.0
creationTimestamp: "2024-09-20T11:09:00Z"
finalizers:
- kubestash.com/cleanup
Expand Down Expand Up @@ -709,7 +709,7 @@ In this section, we will verify whether the desired `Druid` database manifest ha
```bash
$ kubectl get druids.kubedb.com -n dev
NAME VERSION STATUS AGE
restored-druid 30.0.1 Ready 39m
restored-druid 36.0.0 Ready 39m
```

The output confirms that the `Druid` database has been successfully created with the same configuration as it had at the time of backup.
Expand All @@ -735,7 +735,7 @@ At first, check if the database has gone into `Ready` state by the following com
```bash
$ kubectl get druid -n dev restored-druid
NAME VERSION STATUS AGE
restored-druid 30.0.1 Ready 34m
restored-druid 36.0.0 Ready 34m
```

Now, let's verify if our datasource `wikipedia` exists or not. For that, first find out the database `Sevices` by the following command,
Expand Down
2 changes: 1 addition & 1 deletion docs/guides/druid/backup/auto-backup/examples/sample-druid-2.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ metadata:
variables.kubestash.com/targetName: sample-druid-2
variables.kubestash.com/targetedDatabases: druid
spec:
version: 30.0.1
version: 36.0.0
deepStorage:
type: s3
configSecret:
Expand Down
2 changes: 1 addition & 1 deletion docs/guides/druid/backup/auto-backup/examples/sample-druid.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ metadata:
blueprint.kubestash.com/name: druid-default-backup-blueprint
blueprint.kubestash.com/namespace: demo
spec:
version: 30.0.1
version: 36.0.0
deepStorage:
type: s3
configSecret:
Expand Down
8 changes: 4 additions & 4 deletions docs/guides/druid/backup/auto-backup/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -266,7 +266,7 @@ metadata:
blueprint.kubestash.com/name: druid-default-backup-blueprint
blueprint.kubestash.com/namespace: demo
spec:
version: 30.0.1
version: 36.0.0
deepStorage:
type: s3
configSecret:
Expand Down Expand Up @@ -438,7 +438,7 @@ metadata:
kubestash.com/app-ref-namespace: demo
kubestash.com/repo-name: default-blueprint
annotations:
kubedb.com/db-version: 30.0.1
kubedb.com/db-version: 36.0.0
name: default-blueprint-appbinding-samruid-frequent-backup-1726741846
namespace: demo
ownerReferences:
Expand Down Expand Up @@ -587,7 +587,7 @@ metadata:
variables.kubestash.com/targetName: sample-druid-2
variables.kubestash.com/targetedDatabases: druid
spec:
version: 30.0.1
version: 36.0.0
deepStorage:
type: s3
configSecret:
Expand Down Expand Up @@ -755,7 +755,7 @@ metadata:
kubestash.com/app-ref-namespace: demo
kubestash.com/repo-name: customize-blueprint
annotations:
kubedb.com/db-version: 30.0.1
kubedb.com/db-version: 36.0.0
name: customize-blueprint-appbinding-sid-2-frequent-backup-1726743656
namespace: demo
ownerReferences:
Expand Down
2 changes: 1 addition & 1 deletion docs/guides/druid/backup/cross-ns-dependencies/examples/sample-druid.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ metadata:
name: sample-druid
namespace: demo
spec:
version: 30.0.1
version: 36.0.0
zookeeperRef:
name: zk-dev
namespace: dev
Expand Down
16 changes: 8 additions & 8 deletions docs/guides/druid/backup/cross-ns-dependencies/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -121,7 +121,7 @@ metadata:
name: sample-druid
namespace: demo
spec:
version: 30.0.1
version: 36.0.0
zookeeperRef:
name: zk-dev
namespace: dev
Expand Down Expand Up @@ -158,7 +158,7 @@ Let's check if the database is ready to use,
```bash
$ kubectl get druids.kubedb.com -n demo
NAME TYPE VERSION STATUS AGE
sample-druid kubedb.com/v1alpha2 30.0.1 Ready 4m14s
sample-druid kubedb.com/v1alpha2 36.0.0 Ready 4m14s
```

The database is `Ready`. Verify that KubeDB has created a `Secret` and a `Service` for this database using the following commands,
Expand Down Expand Up @@ -199,7 +199,7 @@ Verify that the `AppBinding` has been created successfully using the following c
```bash
$ kubectl get appbindings -n demo
NAME TYPE VERSION AGE
sample-druid kubedb.com/druid 30.0.1 4m7s
sample-druid kubedb.com/druid 36.0.0 4m7s

$ kubectl get appbindings -n dev1
NAME TYPE VERSION AGE
Expand All @@ -224,7 +224,7 @@ kind: AppBinding
metadata:
annotations:
kubectl.kubernetes.io/last-applied-configuration: |
{"apiVersion":"kubedb.com/v1alpha2","kind":"Druid","metadata":{"annotations":{},"name":"sample-druid","namespace":"demo"},"spec":{"deepStorage":{"configSecret":{"name":"deep-storage-config"},"type":"s3"},"deletionPolicy":"WipeOut","topology":{"routers":{"replicas":1}},"version":"30.0.1"}}
{"apiVersion":"kubedb.com/v1alpha2","kind":"Druid","metadata":{"annotations":{},"name":"sample-druid","namespace":"demo"},"spec":{"deepStorage":{"configSecret":{"name":"deep-storage-config"},"type":"s3"},"deletionPolicy":"WipeOut","topology":{"routers":{"replicas":1}},"version":"36.0.0"}}
creationTimestamp: "2024-09-19T13:02:20Z"
generation: 1
labels:
Expand Down Expand Up @@ -258,7 +258,7 @@ spec:
secret:
name: sample-druid-admin-cred
type: kubedb.com/druid
version: 30.0.1
version: 36.0.0
```

KubeStash uses the `AppBinding` CR to connect with the target database. It requires the following two fields to set in AppBinding's `.spec` section.
Expand Down Expand Up @@ -638,7 +638,7 @@ apiVersion: storage.kubestash.com/v1alpha1
kind: Snapshot
metadata:
annotations:
kubedb.com/db-version: 30.0.1
kubedb.com/db-version: 36.0.0
creationTimestamp: "2024-09-20T11:09:00Z"
finalizers:
- kubestash.com/cleanup
Expand Down Expand Up @@ -808,7 +808,7 @@ In this section, we will verify whether the desired `Druid` database manifest ha
```bash
$ kubectl get druids.kubedb.com -n demo
NAME VERSION STATUS AGE
restored-druid 30.0.1 Ready 6m26s
restored-druid 36.0.0 Ready 6m26s
```

The output confirms that the `Druid` database has been successfully created with the same configuration as it had at the time of backup.
Expand All @@ -835,7 +835,7 @@ At first, check if the database has gone into `Ready` state by the following com
```bash
$ kubectl get druid -n demo restored-druid
NAME VERSION STATUS AGE
restored-druid 30.0.1 Ready 34m
restored-druid 36.0.0 Ready 34m
```

Now, let's verify if our datasource `wikipedia` exists or not. For that, first find out the database `Sevices` by the following command,
Expand Down
2 changes: 1 addition & 1 deletion docs/guides/druid/backup/customization/examples/common/sample-druid.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ metadata:
name: sample-druid
namespace: demo
spec:
version: 30.0.1
version: 36.0.0
deepStorage:
type: s3
configSecret:
Expand Down
2 changes: 1 addition & 1 deletion docs/guides/druid/backup/logical/examples/restored-druid.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ metadata:
spec:
init:
waitForInitialRestore: true
version: 30.0.1
version: 36.0.0
deepStorage:
type: s3
configSecret:
Expand Down
2 changes: 1 addition & 1 deletion docs/guides/druid/backup/logical/examples/sample-druid.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ metadata:
name: sample-druid
namespace: demo
spec:
version: 30.0.1
version: 36.0.0
deepStorage:
type: s3
configSecret:
Expand Down
Loading
Loading