diff --git a/docs/examples/druid/quickstart/druid-quickstart.yaml b/docs/examples/druid/quickstart/druid-quickstart.yaml index 1119ffbb67..16fcef0e0b 100644 --- a/docs/examples/druid/quickstart/druid-quickstart.yaml +++ b/docs/examples/druid/quickstart/druid-quickstart.yaml @@ -4,7 +4,7 @@ metadata: name: druid-quickstart namespace: demo spec: - version: 28.0.1 + version: 36.0.0 deepStorage: type: s3 configuration: diff --git a/docs/guides/druid/autoscaler/compute/guide.md b/docs/guides/druid/autoscaler/compute/guide.md index b0810f67b2..0b91283ecd 100644 --- a/docs/guides/druid/autoscaler/compute/guide.md +++ b/docs/guides/druid/autoscaler/compute/guide.md @@ -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 @@ -104,7 +104,7 @@ metadata: name: druid-cluster namespace: demo spec: - version: 28.0.1 + version: 36.0.0 deepStorage: type: s3 configSecret: @@ -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 diff --git a/docs/guides/druid/autoscaler/compute/yamls/druid-cluster.yaml b/docs/guides/druid/autoscaler/compute/yamls/druid-cluster.yaml index ffac2b300b..750f0f72a6 100644 --- a/docs/guides/druid/autoscaler/compute/yamls/druid-cluster.yaml +++ b/docs/guides/druid/autoscaler/compute/yamls/druid-cluster.yaml @@ -4,7 +4,7 @@ metadata: name: druid-cluster namespace: demo spec: - version: 28.0.1 + version: 36.0.0 deepStorage: type: s3 configSecret: diff --git a/docs/guides/druid/autoscaler/storage/guide.md b/docs/guides/druid/autoscaler/storage/guide.md index 02b3571625..7ce945b498 100644 --- a/docs/guides/druid/autoscaler/storage/guide.md +++ b/docs/guides/druid/autoscaler/storage/guide.md @@ -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 @@ -118,7 +118,7 @@ metadata: name: druid-cluster namespace: demo spec: - version: 28.0.1 + version: 36.0.0 deepStorage: type: s3 configSecret: @@ -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, diff --git a/docs/guides/druid/autoscaler/storage/yamls/druid-cluster.yaml b/docs/guides/druid/autoscaler/storage/yamls/druid-cluster.yaml index 5415590a2b..d39570b888 100644 --- a/docs/guides/druid/autoscaler/storage/yamls/druid-cluster.yaml +++ b/docs/guides/druid/autoscaler/storage/yamls/druid-cluster.yaml @@ -4,7 +4,7 @@ metadata: name: druid-cluster namespace: demo spec: - version: 28.0.1 + version: 36.0.0 deepStorage: type: s3 configSecret: diff --git a/docs/guides/druid/backup/application-level/examples/sample-druid.yaml b/docs/guides/druid/backup/application-level/examples/sample-druid.yaml index cca8bd8797..adc68664f8 100644 --- a/docs/guides/druid/backup/application-level/examples/sample-druid.yaml +++ b/docs/guides/druid/backup/application-level/examples/sample-druid.yaml @@ -4,7 +4,7 @@ metadata: name: sample-druid namespace: demo spec: - version: 30.0.1 + version: 36.0.0 deepStorage: type: s3 configSecret: diff --git a/docs/guides/druid/backup/application-level/index.md b/docs/guides/druid/backup/application-level/index.md index eacfca75ee..92d8afc022 100644 --- a/docs/guides/druid/backup/application-level/index.md +++ b/docs/guides/druid/backup/application-level/index.md @@ -114,7 +114,7 @@ metadata: name: sample-druid namespace: demo spec: - version: 30.0.1 + version: 36.0.0 deepStorage: type: s3 configSecret: @@ -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, @@ -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 ``` @@ -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: @@ -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. @@ -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 @@ -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. @@ -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, diff --git a/docs/guides/druid/backup/auto-backup/examples/sample-druid-2.yaml b/docs/guides/druid/backup/auto-backup/examples/sample-druid-2.yaml index a9808332e8..3f28727c7d 100644 --- a/docs/guides/druid/backup/auto-backup/examples/sample-druid-2.yaml +++ b/docs/guides/druid/backup/auto-backup/examples/sample-druid-2.yaml @@ -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: diff --git a/docs/guides/druid/backup/auto-backup/examples/sample-druid.yaml b/docs/guides/druid/backup/auto-backup/examples/sample-druid.yaml index 90090e9907..87a99671cf 100644 --- a/docs/guides/druid/backup/auto-backup/examples/sample-druid.yaml +++ b/docs/guides/druid/backup/auto-backup/examples/sample-druid.yaml @@ -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: diff --git a/docs/guides/druid/backup/auto-backup/index.md b/docs/guides/druid/backup/auto-backup/index.md index 3e4cd4438f..a5b71694da 100644 --- a/docs/guides/druid/backup/auto-backup/index.md +++ b/docs/guides/druid/backup/auto-backup/index.md @@ -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: @@ -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: @@ -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: @@ -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: diff --git a/docs/guides/druid/backup/cross-ns-dependencies/examples/sample-druid.yaml b/docs/guides/druid/backup/cross-ns-dependencies/examples/sample-druid.yaml index c21629db96..c7419dfb95 100644 --- a/docs/guides/druid/backup/cross-ns-dependencies/examples/sample-druid.yaml +++ b/docs/guides/druid/backup/cross-ns-dependencies/examples/sample-druid.yaml @@ -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 diff --git a/docs/guides/druid/backup/cross-ns-dependencies/index.md b/docs/guides/druid/backup/cross-ns-dependencies/index.md index 07570de1fb..c7261cf32d 100644 --- a/docs/guides/druid/backup/cross-ns-dependencies/index.md +++ b/docs/guides/druid/backup/cross-ns-dependencies/index.md @@ -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 @@ -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, @@ -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 @@ -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: @@ -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. @@ -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 @@ -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. @@ -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, diff --git a/docs/guides/druid/backup/customization/examples/common/sample-druid.yaml b/docs/guides/druid/backup/customization/examples/common/sample-druid.yaml index cca8bd8797..adc68664f8 100644 --- a/docs/guides/druid/backup/customization/examples/common/sample-druid.yaml +++ b/docs/guides/druid/backup/customization/examples/common/sample-druid.yaml @@ -4,7 +4,7 @@ metadata: name: sample-druid namespace: demo spec: - version: 30.0.1 + version: 36.0.0 deepStorage: type: s3 configSecret: diff --git a/docs/guides/druid/backup/logical/examples/restored-druid.yaml b/docs/guides/druid/backup/logical/examples/restored-druid.yaml index ed4937b8a6..5fcfda6188 100644 --- a/docs/guides/druid/backup/logical/examples/restored-druid.yaml +++ b/docs/guides/druid/backup/logical/examples/restored-druid.yaml @@ -6,7 +6,7 @@ metadata: spec: init: waitForInitialRestore: true - version: 30.0.1 + version: 36.0.0 deepStorage: type: s3 configSecret: diff --git a/docs/guides/druid/backup/logical/examples/sample-druid.yaml b/docs/guides/druid/backup/logical/examples/sample-druid.yaml index cca8bd8797..adc68664f8 100644 --- a/docs/guides/druid/backup/logical/examples/sample-druid.yaml +++ b/docs/guides/druid/backup/logical/examples/sample-druid.yaml @@ -4,7 +4,7 @@ metadata: name: sample-druid namespace: demo spec: - version: 30.0.1 + version: 36.0.0 deepStorage: type: s3 configSecret: diff --git a/docs/guides/druid/backup/logical/index.md b/docs/guides/druid/backup/logical/index.md index 430cf47e23..345b61d91b 100644 --- a/docs/guides/druid/backup/logical/index.md +++ b/docs/guides/druid/backup/logical/index.md @@ -115,7 +115,7 @@ metadata: name: druid-quickstart namespace: demo spec: - version: 30.0.1 + version: 36.0.0 deepStorage: type: s3 configSecret: @@ -140,7 +140,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 113s +sample-druid kubedb.com/v1alpha2 36.0.0 Ready 113s ``` The database is `Ready`. Verify that KubeDB has created the necessary `Secrets` and `Services` to access the database along with `MySQL` and `ZooKeeper` instance for this database using the following commands, @@ -167,7 +167,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 2m26s +sample-druid kubedb.com/druid 36.0.0 2m26s sample-druid-mysql-metadata kubedb.com/mysql 9.1.0 5m40s sample-druid-zk kubedb.com/zookeeper 3.7.2 5m43s ``` @@ -184,7 +184,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-17T12:17:27Z" generation: 1 labels: @@ -218,7 +218,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. @@ -530,7 +530,7 @@ metadata: kubestash.com/app-ref-namespace: demo kubestash.com/repo-name: gcs-druid-repo annotations: - kubedb.com/db-version: 30.0.1 + kubedb.com/db-version: 36.0.0 name: gcs-druid-repo-sample-druid-backup-frequent-backup-1726656835 namespace: demo ownerReferences: @@ -600,7 +600,7 @@ metadata: spec: init: waitForInitialRestore: true - version: 30.0.1 + version: 36.0.0 deepStorage: type: s3 configSecret: @@ -623,7 +623,7 @@ If you check the database status, you will see it is stuck in `Provisioning` sta ```bash $ kubectl get druid -n demo restored-druid NAME TYPE VERSION STATUS AGE -restored-druid kubedb.com/v1alpha2 30.0.1 Provisioning 22s +restored-druid kubedb.com/v1alpha2 36.0.0 Provisioning 22s ``` #### Create RestoreSession: @@ -693,7 +693,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 8.2.0 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, diff --git a/docs/guides/druid/clustering/guide/index.md b/docs/guides/druid/clustering/guide/index.md index 33b7c6e21f..2e41caf31a 100644 --- a/docs/guides/druid/clustering/guide/index.md +++ b/docs/guides/druid/clustering/guide/index.md @@ -95,7 +95,7 @@ metadata: name: druid-cluster namespace: demo spec: - version: 28.0.1 + version: 36.0.0 deepStorage: type: s3 configSecret: @@ -432,7 +432,7 @@ Spec: Security Context: Fs Group: 1000 Replicas: 1 - Version: 28.0.1 + Version: 36.0.0 Zookeeper Ref: Name: druid-cluster-zk Namespace: demo @@ -804,7 +804,7 @@ Spec: Security Context: Fs Group: 1000 Replicas: 1 - Version: 28.0.1 + Version: 36.0.0 Zookeeper Ref: Name: druid-cluster-zk Namespace: demo diff --git a/docs/guides/druid/clustering/guide/yamls/druid-cluster.yaml b/docs/guides/druid/clustering/guide/yamls/druid-cluster.yaml index 7a89d0dc91..2484eebb82 100644 --- a/docs/guides/druid/clustering/guide/yamls/druid-cluster.yaml +++ b/docs/guides/druid/clustering/guide/yamls/druid-cluster.yaml @@ -4,7 +4,7 @@ metadata: name: druid-cluster namespace: demo spec: - version: 28.0.1 + version: 36.0.0 deepStorage: type: s3 configSecret: diff --git a/docs/guides/druid/concepts/appbinding.md b/docs/guides/druid/concepts/appbinding.md index 02c4750799..1d95242108 100644 --- a/docs/guides/druid/concepts/appbinding.md +++ b/docs/guides/druid/concepts/appbinding.md @@ -34,7 +34,7 @@ kind: AppBinding metadata: annotations: kubectl.kubernetes.io/last-applied-configuration: | - {"apiVersion":"kubedb.com/v1alpha2","kind":"Druid","metadata":{"annotations":{},"name":"druid-quickstart","namespace":"demo"},"spec":{"deepStorage":{"configSecret":{"name":"deep-storage-config"},"type":"s3"},"topology":{"routers":{"replicas":1}},"version":"28.0.1"}} + {"apiVersion":"kubedb.com/v1alpha2","kind":"Druid","metadata":{"annotations":{},"name":"druid-quickstart","namespace":"demo"},"spec":{"deepStorage":{"configSecret":{"name":"deep-storage-config"},"type":"s3"},"topology":{"routers":{"replicas":1}},"version":"36.0.0"}} creationTimestamp: "2024-10-16T13:28:40Z" generation: 1 labels: @@ -71,7 +71,7 @@ spec: tlsSecret: name: druid-client-cert type: kubedb.com/druid - version: 28.0.1 + version: 36.0.0 ``` Here, we are going to describe the sections of an `AppBinding` crd. diff --git a/docs/guides/druid/concepts/druid.md b/docs/guides/druid/concepts/druid.md index 4e16e89e93..e41c1ec538 100644 --- a/docs/guides/druid/concepts/druid.md +++ b/docs/guides/druid/concepts/druid.md @@ -164,7 +164,7 @@ spec: labels: release: prometheus interval: 10s - version: 30.0.1 + version: 36.0.0 ``` ### spec.version @@ -174,6 +174,7 @@ spec: - `28.0.1` - `30.0.1` - `31.0.1` +- `36.0.0` ### spec.replicas diff --git a/docs/guides/druid/concepts/druidopsrequest.md b/docs/guides/druid/concepts/druidopsrequest.md index c464528f6b..0b1ccefaee 100644 --- a/docs/guides/druid/concepts/druidopsrequest.md +++ b/docs/guides/druid/concepts/druidopsrequest.md @@ -38,7 +38,7 @@ spec: databaseRef: name: druid-prod updateVersion: - targetVersion: 30.0.1 + targetVersion: 36.0.0 status: conditions: - lastTransitionTime: "2024-07-25T18:22:38Z" diff --git a/docs/guides/druid/configuration/config-file/index.md b/docs/guides/druid/configuration/config-file/index.md index c7365dc5e8..c6d326d242 100644 --- a/docs/guides/druid/configuration/config-file/index.md +++ b/docs/guides/druid/configuration/config-file/index.md @@ -153,7 +153,7 @@ metadata: name: druid-with-config namespace: demo spec: - version: 28.0.1 + version: 36.0.0 configuration: secretName: config-secret deepStorage: @@ -178,11 +178,11 @@ Now, wait for the Druid to become ready: ```bash $ kubectl get dr -n demo -w NAME TYPE VERSION STATUS AGE -druid-with-config kubedb.com/v1alpha2 28.0.1 Provisioning 5s -druid-with-config kubedb.com/v1alpha2 28.0.1 Provisioning 7s +druid-with-config kubedb.com/v1alpha2 36.0.0 Provisioning 5s +druid-with-config kubedb.com/v1alpha2 36.0.0 Provisioning 7s . . -druid-with-config kubedb.com/v1alpha2 28.0.1 Ready 2m +druid-with-config kubedb.com/v1alpha2 36.0.0 Ready 2m ``` ## Verify Configuration diff --git a/docs/guides/druid/configuration/config-file/yamls/druid-with-config.yaml b/docs/guides/druid/configuration/config-file/yamls/druid-with-config.yaml index d4573cf773..802cf86242 100644 --- a/docs/guides/druid/configuration/config-file/yamls/druid-with-config.yaml +++ b/docs/guides/druid/configuration/config-file/yamls/druid-with-config.yaml @@ -4,7 +4,7 @@ metadata: name: druid-with-config namespace: demo spec: - version: 28.0.1 + version: 36.0.0 configuration: secretName: config-secret deepStorage: diff --git a/docs/guides/druid/configuration/podtemplating/index.md b/docs/guides/druid/configuration/podtemplating/index.md index a00bd0b972..549ba45496 100644 --- a/docs/guides/druid/configuration/podtemplating/index.md +++ b/docs/guides/druid/configuration/podtemplating/index.md @@ -120,7 +120,7 @@ metadata: name: druid-cluster namespace: demo spec: - version: 28.0.1 + version: 36.0.0 configuration: secretName: config-secret deepStorage: @@ -168,7 +168,7 @@ Now, wait a few minutes. KubeDB operator will create necessary PVC, petset, serv ```bash $ kubectl get druid -n demo NAME TYPE VERSION STATUS AGE -druid-cluster kubedb.com/v1alpha2 28.0.1 Ready 6m5s +druid-cluster kubedb.com/v1alpha2 36.0.0 Ready 6m5s ``` Check that the petset's pod is running @@ -269,7 +269,7 @@ metadata: name: druid-node-selector namespace: demo spec: - version: 28.0.1 + version: 36.0.0 deepStorage: type: s3 configSecret: @@ -294,7 +294,7 @@ Now, wait a few minutes. KubeDB operator will create necessary petset, services, ```bash $ kubectl get druid -n demo NAME TYPE VERSION STATUS AGE -druid-node-selector kubedb.com/v1alpha2 28.0.1 Ready 54m +druid-node-selector kubedb.com/v1alpha2 36.0.0 Ready 54m ``` You can verify that by running `kubectl get pods -n demo druid-node-selector-0 -o wide` and looking at the “NODE” to which the Pod was assigned. ```bash @@ -364,7 +364,7 @@ metadata: name: druid-without-tolerations namespace: demo spec: - version: 28.0.1 + version: 36.0.0 deepStorage: type: s3 configSecret: @@ -416,7 +416,7 @@ Controlled By: PetSet/druid-without-tolerations-coordinators Init Containers: init-druid: Container ID: containerd://62c9a2053d619dded2085e354cd2c0dfa238761033cc0483c824c1ed8ee4c002 - Image: ghcr.io/kubedb/druid-init:28.0.1@sha256:ed87835bc0f89dea923fa8e3cf1ef209e3e41cb93944a915289322035dcd8a91 + Image: ghcr.io/kubedb/druid-init:36.0.0@sha256:ed87835bc0f89dea923fa8e3cf1ef209e3e41cb93944a915289322035dcd8a91 Image ID: ghcr.io/kubedb/druid-init@sha256:ed87835bc0f89dea923fa8e3cf1ef209e3e41cb93944a915289322035dcd8a91 Port: Host Port: @@ -444,7 +444,7 @@ Init Containers: Containers: druid: Container ID: containerd://3a52f120ca09f90fcdc062c94bf404964add7a5b6ded4a372400267a9d0fd598 - Image: ghcr.io/appscode-images/druid:28.0.1@sha256:d86e424233ec5a120c1e072cf506fa169868fd9572bbb9800a85400f0c879dec + Image: ghcr.io/appscode-images/druid:36.0.0@sha256:d86e424233ec5a120c1e072cf506fa169868fd9572bbb9800a85400f0c879dec Image ID: ghcr.io/appscode-images/druid@sha256:d86e424233ec5a120c1e072cf506fa169868fd9572bbb9800a85400f0c879dec Port: 8081/TCP Host Port: 0/TCP @@ -515,7 +515,7 @@ metadata: name: druid-cluster namespace: demo spec: - version: 28.0.1 + version: 36.0.0 deepStorage: type: s3 configSecret: diff --git a/docs/guides/druid/configuration/podtemplating/yamls/druid-cluster.yaml b/docs/guides/druid/configuration/podtemplating/yamls/druid-cluster.yaml index 3a84fb47d1..3f84e50cdc 100644 --- a/docs/guides/druid/configuration/podtemplating/yamls/druid-cluster.yaml +++ b/docs/guides/druid/configuration/podtemplating/yamls/druid-cluster.yaml @@ -4,7 +4,7 @@ metadata: name: druid-cluster namespace: demo spec: - version: 28.0.1 + version: 36.0.0 configuration: secretName: config-secret deepStorage: diff --git a/docs/guides/druid/configuration/podtemplating/yamls/druid-node-selector.yaml b/docs/guides/druid/configuration/podtemplating/yamls/druid-node-selector.yaml index 7ad2eae717..8beb870a2d 100644 --- a/docs/guides/druid/configuration/podtemplating/yamls/druid-node-selector.yaml +++ b/docs/guides/druid/configuration/podtemplating/yamls/druid-node-selector.yaml @@ -4,7 +4,7 @@ metadata: name: druid-node-selector namespace: demo spec: - version: 28.0.1 + version: 36.0.0 deepStorage: type: s3 configSecret: diff --git a/docs/guides/druid/configuration/podtemplating/yamls/druid-with-tolerations.yaml b/docs/guides/druid/configuration/podtemplating/yamls/druid-with-tolerations.yaml index 4ef158f85a..820e3c73f5 100644 --- a/docs/guides/druid/configuration/podtemplating/yamls/druid-with-tolerations.yaml +++ b/docs/guides/druid/configuration/podtemplating/yamls/druid-with-tolerations.yaml @@ -4,7 +4,7 @@ metadata: name: druid-cluster namespace: demo spec: - version: 28.0.1 + version: 36.0.0 deepStorage: type: s3 configSecret: diff --git a/docs/guides/druid/configuration/podtemplating/yamls/druid-without-tolerations.yaml b/docs/guides/druid/configuration/podtemplating/yamls/druid-without-tolerations.yaml index 1098f3d70d..f76e265f01 100644 --- a/docs/guides/druid/configuration/podtemplating/yamls/druid-without-tolerations.yaml +++ b/docs/guides/druid/configuration/podtemplating/yamls/druid-without-tolerations.yaml @@ -4,7 +4,7 @@ metadata: name: druid-without-tolerations namespace: demo spec: - version: 28.0.1 + version: 36.0.0 deepStorage: type: s3 configSecret: diff --git a/docs/guides/druid/failover/guide.md b/docs/guides/druid/failover/guide.md index b2c674e5f8..b6458afea7 100644 --- a/docs/guides/druid/failover/guide.md +++ b/docs/guides/druid/failover/guide.md @@ -79,12 +79,13 @@ NAME VERSION DB_IMAGE DEPRECATED AGE 28.0.1 28.0.1 ghcr.io/appscode-images/druid:28.0.1 24h 30.0.1 30.0.1 ghcr.io/appscode-images/druid:30.0.1 24h 31.0.0 31.0.0 ghcr.io/appscode-images/druid:31.0.0 24h +36.0.0 36.0.0 ghcr.io/appscode-images/druid:36.0.0 24h ``` Notice the `DEPRECATED` column. Here, `true` means that this DruidVersion is deprecated for the current KubeDB version. KubeDB will not work for deprecated DruidVersion. You can also use the short from `drversion` to check available DruidVersions. -In this tutorial, we will use `28.0.1` DruidVersion CR to create a Druid cluster. +In this tutorial, we will use `36.0.0` DruidVersion CR to create a Druid cluster. ## Get External Dependencies Ready @@ -151,7 +152,7 @@ metadata: name: druid-cluster namespace: demo spec: - version: 31.0.0 + version: 36.0.0 deletionPolicy: Delete deepStorage: type: s3 @@ -188,7 +189,7 @@ The Druid's `STATUS` will go from `Provisioning` to `Ready` state within few min ```bash $ kubectl get druid -n demo -w NAME TYPE VERSION STATUS AGE -druid-cluster kubedb.com/v1alpha2 31.0.0 Ready 4m12s +druid-cluster kubedb.com/v1alpha2 36.0.0 Ready 4m12s ``` ## Inspect Druid Pod Roles and Health @@ -203,7 +204,7 @@ See the database is ready. ```shell $ kubectl get druid,petset,pods -n demo NAME TYPE VERSION STATUS AGE -druid.kubedb.com/druid-cluster kubedb.com/v1alpha2 31.0.0 Ready 15m +druid.kubedb.com/druid-cluster kubedb.com/v1alpha2 36.0.0 Ready 15m NAME AGE petset.apps.k8s.appscode.com/druid-cluster-brokers 14m diff --git a/docs/guides/druid/monitoring/overview.md b/docs/guides/druid/monitoring/overview.md index 752599f2e8..0b20440478 100644 --- a/docs/guides/druid/monitoring/overview.md +++ b/docs/guides/druid/monitoring/overview.md @@ -53,7 +53,7 @@ metadata: name: druid-with-monitoring namespace: demo spec: - version: 28.0.1 + version: 36.0.0 deepStorage: type: s3 configSecret: diff --git a/docs/guides/druid/monitoring/using-builtin-prometheus.md b/docs/guides/druid/monitoring/using-builtin-prometheus.md index 69ec2aa62e..494e8de48f 100644 --- a/docs/guides/druid/monitoring/using-builtin-prometheus.md +++ b/docs/guides/druid/monitoring/using-builtin-prometheus.md @@ -49,7 +49,7 @@ metadata: name: druid-with-monitoring namespace: demo spec: - version: 28.0.1 + version: 36.0.0 deepStorage: type: s3 configSecret: @@ -85,7 +85,7 @@ Now, wait for the cluster to go into `Ready` state. ```bash NAME TYPE VERSION STATUS AGE -druid-with-monitoring kubedb.com/v1alpha2 28.0.1 Ready 31s +druid-with-monitoring kubedb.com/v1alpha2 36.0.0 Ready 31s ``` KubeDB will create a separate stats service with name `{Druid crd name}-stats` for monitoring purpose. diff --git a/docs/guides/druid/monitoring/using-prometheus-operator.md b/docs/guides/druid/monitoring/using-prometheus-operator.md index 1b7ef85979..da4f0c10d2 100644 --- a/docs/guides/druid/monitoring/using-prometheus-operator.md +++ b/docs/guides/druid/monitoring/using-prometheus-operator.md @@ -160,7 +160,7 @@ metadata: name: druid-with-monitoring namespace: demo spec: - version: 28.0.1 + version: 36.0.0 deepStorage: type: s3 configSecret: @@ -196,7 +196,7 @@ Now, wait for the database to go into `Running` state. ```bash $ kubectl get dr -n demo druid NAME TYPE VERSION STATUS AGE -druid-with-monitoring kubedb.com/v1alpha2 28.0.1 Ready 2m24s +druid-with-monitoring kubedb.com/v1alpha2 36.0.0 Ready 2m24s ``` KubeDB will create a separate stats service with name `{Druid crd name}-stats` for monitoring purpose. diff --git a/docs/guides/druid/monitoring/yamls/druid-monitoring-builtin.yaml b/docs/guides/druid/monitoring/yamls/druid-monitoring-builtin.yaml index 4962c3c536..bdafc5084d 100644 --- a/docs/guides/druid/monitoring/yamls/druid-monitoring-builtin.yaml +++ b/docs/guides/druid/monitoring/yamls/druid-monitoring-builtin.yaml @@ -4,7 +4,7 @@ metadata: name: druid-with-monitoring namespace: demo spec: - version: 28.0.1 + version: 36.0.0 deepStorage: type: s3 configSecret: diff --git a/docs/guides/druid/monitoring/yamls/druid-with-monitoring.yaml b/docs/guides/druid/monitoring/yamls/druid-with-monitoring.yaml index 0b8b074410..18e7cfd3b2 100644 --- a/docs/guides/druid/monitoring/yamls/druid-with-monitoring.yaml +++ b/docs/guides/druid/monitoring/yamls/druid-with-monitoring.yaml @@ -4,7 +4,7 @@ metadata: name: druid-with-monitoring namespace: demo spec: - version: 28.0.1 + version: 36.0.0 deepStorage: type: s3 configSecret: diff --git a/docs/guides/druid/quickstart/guide/index.md b/docs/guides/druid/quickstart/guide/index.md index 6d577ec7cd..923a3be262 100644 --- a/docs/guides/druid/quickstart/guide/index.md +++ b/docs/guides/druid/quickstart/guide/index.md @@ -60,12 +60,12 @@ When you install the KubeDB operator, it registers a CRD named [DruidVersion](/d ```bash $ kubectl get druidversion NAME VERSION DB_IMAGE DEPRECATED AGE -28.0.1 28.0.1 ghcr.io/appscode-images/druid:28.0.1 4h47m +36.0.0 36.0.0 ghcr.io/appscode-images/druid:36.0.0 4h47m ``` Notice the `DEPRECATED` column. Here, `true` means that this DruidVersion is deprecated for the current KubeDB version. KubeDB will not work for deprecated DruidVersion. You can also use the short from `drversion` to check available DruidVersions. -In this tutorial, we will use `28.0.1` DruidVersion CR to create a Druid cluster. +In this tutorial, we will use `36.0.0` DruidVersion CR to create a Druid cluster. ## Get External Dependencies Ready @@ -165,7 +165,7 @@ metadata: name: druid-quickstart namespace: demo spec: - version: 28.0.1 + version: 36.0.0 deepStorage: type: s3 configSecret: @@ -184,7 +184,7 @@ spec: ``` Here, -- `spec.version` - is the name of the DruidVersion CR. Here, a Druid of version `28.0.1` will be created. +- `spec.version` - is the name of the DruidVersion CR. Here, a Druid of version `36.0.0` will be created. - `spec.deepStorage` - contains the information of deep storage configuration with `spec.deepStorage.type` being the deep storage type and `spec.deepStorage.configSecret` is a reference to the configuration secret. - `spec.topology` - is the definition of the topology that will be deployed. The required nodes such as `coordinators`, `historicals`, `middleManagers`, and `brokers` will be deployed by default with one replica. You can also add optional nodes including `routers` and `overlords` in the topology. - `spec.deletionPolicy` specifies what KubeDB should do when a user try to delete Druid CR. Deletion policy `Delete` will delete the database pods and PVC when the Druid CR is deleted. @@ -203,11 +203,11 @@ The Druid's `STATUS` will go from `Provisioning` to `Ready` state within few min ```bash $ kubectl get druid -n demo -w NAME TYPE VERSION STATUS AGE -druid-quickstart kubedb.com/v1alpha2 28.0.1 Provisioning 17s -druid-quickstart kubedb.com/v1alpha2 28.0.1 Provisioning 28s +druid-quickstart kubedb.com/v1alpha2 36.0.0 Provisioning 17s +druid-quickstart kubedb.com/v1alpha2 36.0.0 Provisioning 28s . . -druid-quickstart kubedb.com/v1alpha2 28.0.1 Ready 82s +druid-quickstart kubedb.com/v1alpha2 36.0.0 Ready 82s ``` Describe the Druid object to observe the progress if something goes wrong or the status is not changing for a long period of time: @@ -540,7 +540,7 @@ Spec: Security Context: Fs Group: 1000 Replicas: 1 - Version: 28.0.1 + Version: 36.0.0 Zookeeper Ref: Name: druid-quickstart-zk Namespace: demo @@ -607,7 +607,7 @@ service/druid-quickstart-pods ClusterIP None service/druid-quickstart-routers LoadBalancer 10.96.134.202 10.86.51.181 8888:32751/TCP 2m13s NAME TYPE VERSION AGE -appbinding.appcatalog.appscode.com/druid-quickstart kubedb.com/druid 28.0.1 2m1s +appbinding.appcatalog.appscode.com/druid-quickstart kubedb.com/druid 36.0.0 2m1s NAME TYPE DATA AGE secret/druid-quickstart-admin-cred kubernetes.io/basic-auth 2 2m13s diff --git a/docs/guides/druid/reconfigure-tls/guide.md b/docs/guides/druid/reconfigure-tls/guide.md index 6baa86542e..3cee0b4d62 100644 --- a/docs/guides/druid/reconfigure-tls/guide.md +++ b/docs/guides/druid/reconfigure-tls/guide.md @@ -48,7 +48,7 @@ metadata: name: druid-cluster namespace: demo spec: - version: 28.0.1 + version: 36.0.0 deepStorage: type: s3 configSecret: @@ -71,11 +71,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 15s -druid-cluster kubedb.com/v1alpha2 28.0.1 Provisioning 37s +druid-cluster kubedb.com/v1alpha2 36.0.0 Provisioning 15s +druid-cluster kubedb.com/v1alpha2 36.0.0 Provisioning 37s . . -druid-cluster kubedb.com/v1alpha2 28.0.1 Ready 2m27s +druid-cluster kubedb.com/v1alpha2 36.0.0 Ready 2m27s ``` Now, we can exec one druid broker pod and verify configuration that the TLS is disabled. diff --git a/docs/guides/druid/reconfigure-tls/yamls/druid-cluster.yaml b/docs/guides/druid/reconfigure-tls/yamls/druid-cluster.yaml index 7a89d0dc91..2484eebb82 100644 --- a/docs/guides/druid/reconfigure-tls/yamls/druid-cluster.yaml +++ b/docs/guides/druid/reconfigure-tls/yamls/druid-cluster.yaml @@ -4,7 +4,7 @@ metadata: name: druid-cluster namespace: demo spec: - version: 28.0.1 + version: 36.0.0 deepStorage: type: s3 configSecret: diff --git a/docs/guides/druid/reconfigure/guide.md b/docs/guides/druid/reconfigure/guide.md index 5ff094b3c3..28cb3bec17 100644 --- a/docs/guides/druid/reconfigure/guide.md +++ b/docs/guides/druid/reconfigure/guide.md @@ -41,7 +41,7 @@ Now, we are going to deploy a `Druid` cluster using a supported version by `Kub ### Prepare Druid Cluster -Now, we are going to deploy a `Druid` topology cluster with version `28.0.1`. +Now, we are going to deploy a `Druid` topology cluster with version `36.0.0`. #### Create External Dependency (Deep Storage) @@ -101,7 +101,7 @@ metadata: name: druid-cluster namespace: demo spec: - version: 28.0.1 + version: 36.0.0 deepStorage: type: s3 configSecret: diff --git a/docs/guides/druid/reconfigure/yamls/druid-cluster.yaml b/docs/guides/druid/reconfigure/yamls/druid-cluster.yaml index 7a89d0dc91..2484eebb82 100644 --- a/docs/guides/druid/reconfigure/yamls/druid-cluster.yaml +++ b/docs/guides/druid/reconfigure/yamls/druid-cluster.yaml @@ -4,7 +4,7 @@ metadata: name: druid-cluster namespace: demo spec: - version: 28.0.1 + version: 36.0.0 deepStorage: type: s3 configSecret: diff --git a/docs/guides/druid/restart/guide.md b/docs/guides/druid/restart/guide.md index b172825913..c4175081f7 100644 --- a/docs/guides/druid/restart/guide.md +++ b/docs/guides/druid/restart/guide.md @@ -93,7 +93,7 @@ metadata: name: druid-cluster namespace: demo spec: - version: 28.0.1 + version: 36.0.0 deepStorage: type: s3 configSecret: diff --git a/docs/guides/druid/restart/yamls/druid-cluster.yaml b/docs/guides/druid/restart/yamls/druid-cluster.yaml index 6351c2ddda..ef33edfc1c 100644 --- a/docs/guides/druid/restart/yamls/druid-cluster.yaml +++ b/docs/guides/druid/restart/yamls/druid-cluster.yaml @@ -4,7 +4,7 @@ metadata: name: druid-cluster namespace: demo spec: - version: 28.0.1 + version: 36.0.0 deepStorage: type: s3 configSecret: diff --git a/docs/guides/druid/rotate-auth/guide.md b/docs/guides/druid/rotate-auth/guide.md index 9955a5bbd0..6612c7f937 100644 --- a/docs/guides/druid/rotate-auth/guide.md +++ b/docs/guides/druid/rotate-auth/guide.md @@ -97,7 +97,7 @@ metadata: name: druid-cluster namespace: demo spec: - version: 28.0.1 + version: 36.0.0 deepStorage: type: s3 configSecret: @@ -119,7 +119,7 @@ Now, wait until `druid-quickstart` has status Ready. i.e, ```shell $ kubectl get druid -n demo NAME TYPE VERSION STATUS AGE -druid-quickstart kubedb.com/v1alpha2 28.0.1 Ready 5m3s +druid-quickstart kubedb.com/v1alpha2 36.0.0 Ready 5m3s ``` ## Verify authentication diff --git a/docs/guides/druid/scaling/horizontal-scaling/guide.md b/docs/guides/druid/scaling/horizontal-scaling/guide.md index 6e6648b4f8..bc688e2525 100644 --- a/docs/guides/druid/scaling/horizontal-scaling/guide.md +++ b/docs/guides/druid/scaling/horizontal-scaling/guide.md @@ -43,7 +43,7 @@ Here, we are going to deploy a `Druid` cluster using a supported version by `Kub ### Prepare Druid Topology cluster -Now, we are going to deploy a `Druid` topology cluster with version `28.0.1`. +Now, we are going to deploy a `Druid` topology cluster with version `36.0.0`. ### Create External Dependency (Deep Storage) @@ -106,7 +106,7 @@ metadata: name: druid-cluster namespace: demo spec: - version: 28.0.1 + version: 36.0.0 deepStorage: type: s3 configSecret: @@ -129,11 +129,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/v1aplha2 28.0.1 Provisioning 0s -druid-cluster kubedb.com/v1aplha2 28.0.1 Provisioning 24s +druid-cluster kubedb.com/v1aplha2 36.0.0 Provisioning 0s +druid-cluster kubedb.com/v1aplha2 36.0.0 Provisioning 24s . . -druid-cluster kubedb.com/v1aplha2 28.0.1 Ready 92s +druid-cluster kubedb.com/v1aplha2 36.0.0 Ready 92s ``` Let's check the number of replicas has from druid object, number of pods the petset have, diff --git a/docs/guides/druid/scaling/horizontal-scaling/yamls/druid-cluster.yaml b/docs/guides/druid/scaling/horizontal-scaling/yamls/druid-cluster.yaml index 6351c2ddda..ef33edfc1c 100644 --- a/docs/guides/druid/scaling/horizontal-scaling/yamls/druid-cluster.yaml +++ b/docs/guides/druid/scaling/horizontal-scaling/yamls/druid-cluster.yaml @@ -4,7 +4,7 @@ metadata: name: druid-cluster namespace: demo spec: - version: 28.0.1 + version: 36.0.0 deepStorage: type: s3 configSecret: diff --git a/docs/guides/druid/scaling/vertical-scaling/guide.md b/docs/guides/druid/scaling/vertical-scaling/guide.md index cedf35b076..649cb64ff6 100644 --- a/docs/guides/druid/scaling/vertical-scaling/guide.md +++ b/docs/guides/druid/scaling/vertical-scaling/guide.md @@ -43,7 +43,7 @@ Here, we are going to deploy a `Druid` topology cluster using a supported versio ### Prepare Druid Topology Cluster -Now, we are going to deploy a `Druid` topology cluster database with version `28.0.1`. +Now, we are going to deploy a `Druid` topology cluster database with version `36.0.0`. ### Create External Dependency (Deep Storage) @@ -105,7 +105,7 @@ metadata: name: druid-cluster namespace: demo spec: - version: 28.0.1 + version: 36.0.0 deepStorage: type: s3 configSecret: @@ -128,11 +128,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/v1aplha2 28.0.1 Provisioning 0s -druid-cluster kubedb.com/v1aplha2 28.0.1 Provisioning 24s +druid-cluster kubedb.com/v1aplha2 36.0.0 Provisioning 0s +druid-cluster kubedb.com/v1aplha2 36.0.0 Provisioning 24s . . -druid-cluster kubedb.com/v1aplha2 28.0.1 Ready 92s +druid-cluster kubedb.com/v1aplha2 36.0.0 Ready 92s ``` Let's check the Pod containers resources for both `coordinators` and `historicals` of the Druid topology cluster. Run the following command to get the resources of the `coordinators` and `historicals` containers of the Druid topology cluster diff --git a/docs/guides/druid/scaling/vertical-scaling/yamls/druid-cluster.yaml b/docs/guides/druid/scaling/vertical-scaling/yamls/druid-cluster.yaml index 7a89d0dc91..2484eebb82 100644 --- a/docs/guides/druid/scaling/vertical-scaling/yamls/druid-cluster.yaml +++ b/docs/guides/druid/scaling/vertical-scaling/yamls/druid-cluster.yaml @@ -4,7 +4,7 @@ metadata: name: druid-cluster namespace: demo spec: - version: 28.0.1 + version: 36.0.0 deepStorage: type: s3 configSecret: diff --git a/docs/guides/druid/tls/guide.md b/docs/guides/druid/tls/guide.md index ead99ecbd5..faa2dbd7ce 100644 --- a/docs/guides/druid/tls/guide.md +++ b/docs/guides/druid/tls/guide.md @@ -148,7 +148,7 @@ metadata: name: druid-cluster-tls namespace: demo spec: - version: 28.0.1 + version: 36.0.0 enableSSL: true tls: issuerRef: @@ -179,11 +179,11 @@ $ kubectl get druid -n demo -w Every 2.0s: kubectl get druid -n demo aadee: Fri Sep 6 12:34:51 2024 NAME TYPE VERSION STATUS AGE -druid-cluster-tls kubedb.com/v1alpha2 28.0.1 Ready 20s -druid-cluster-tls kubedb.com/v1alpha2 28.0.1 Provisioning 1m +druid-cluster-tls kubedb.com/v1alpha2 36.0.0 Ready 20s +druid-cluster-tls kubedb.com/v1alpha2 36.0.0 Provisioning 1m ... ... -druid-cluster-tls kubedb.com/v1alpha2 28.0.1 Ready 38m +druid-cluster-tls kubedb.com/v1alpha2 36.0.0 Ready 38m ``` ### Verify TLS/SSL in Druid Cluster diff --git a/docs/guides/druid/tls/yamls/druid-cluster-tls.yaml b/docs/guides/druid/tls/yamls/druid-cluster-tls.yaml index 902b5b36d4..433e868a4f 100644 --- a/docs/guides/druid/tls/yamls/druid-cluster-tls.yaml +++ b/docs/guides/druid/tls/yamls/druid-cluster-tls.yaml @@ -4,7 +4,7 @@ metadata: name: druid-cluster-tls namespace: demo spec: - version: 28.0.1 + version: 36.0.0 enableSSL: true tls: issuerRef: diff --git a/docs/guides/druid/update-version/guide.md b/docs/guides/druid/update-version/guide.md index 2ff20d7fee..a68e2194cb 100644 --- a/docs/guides/druid/update-version/guide.md +++ b/docs/guides/druid/update-version/guide.md @@ -37,7 +37,7 @@ namespace/demo created ## Prepare Druid -Now, we are going to deploy a `Druid` cluster with version `28.0.1`. +Now, we are going to deploy a `Druid` cluster with version `35.0.1`. ### Create External Dependency (Deep Storage) @@ -99,7 +99,7 @@ metadata: name: druid-quickstart namespace: demo spec: - version: 28.0.1 + version: 35.0.1 deepStorage: type: s3 configSecret: @@ -122,11 +122,11 @@ Now, wait until `druid-cluster` created has status `Ready`. i.e, ```bash $ kubectl get dr -n demo -w NAME TYPE VERSION STATUS AGE -druid-cluster kubedb.com/v1aplha2 28.0.1 Provisioning 0s -druid-cluster kubedb.com/v1aplha2 28.0.1 Provisioning 55s +druid-cluster kubedb.com/v1aplha2 35.0.1 Provisioning 0s +druid-cluster kubedb.com/v1aplha2 35.0.1 Provisioning 55s . . -druid-cluster kubedb.com/v1aplha2 28.0.1 Ready 119s +druid-cluster kubedb.com/v1aplha2 35.0.1 Ready 119s ``` We are now ready to apply the `DruidOpsRequest` CR to update. @@ -168,11 +168,11 @@ After providing the credentials correctly, you should be able to access the web

-Here, we can see that the version of the druid cluster is `28.0.1`. +Here, we can see that the version of the druid cluster is `35.0.1`. ### Update Druid Version -Here, we are going to update `Druid` from `28.0.1` to `30.0.1`. +Here, we are going to update `Druid` from `35.0.1` to `36.0.0`. #### Create DruidOpsRequest: @@ -189,7 +189,7 @@ spec: databaseRef: name: druid-cluster updateVersion: - targetVersion: 30.0.1 + targetVersion: 36.0.0 timeout: 5m apply: IfReady ``` @@ -198,7 +198,7 @@ Here, - `spec.databaseRef.name` specifies that we are performing operation on `druid-cluster` Druid. - `spec.type` specifies that we are going to perform `UpdateVersion` on our database. -- `spec.updateVersion.targetVersion` specifies the expected version of the database `30.0.1`. +- `spec.updateVersion.targetVersion` specifies the expected version of the database `36.0.0`. Let's create the `DruidOpsRequest` CR we have shown above, @@ -273,7 +273,7 @@ Spec: Timeout: 5m Type: UpdateVersion Update Version: - Target Version: 30.0.1 + Target Version: 36.0.0 Status: Conditions: Last Transition Time: 2024-10-21T13:04:51Z @@ -407,13 +407,13 @@ Now, we are going to verify whether the `Druid` and the related `PetSets` and th ```bash $ kubectl get dr -n demo druid-cluster -o=jsonpath='{.spec.version}{"\n"}' -30.0.1 +36.0.0 $ kubectl get petset -n demo druid-cluster-brokers -o=jsonpath='{.spec.template.spec.containers[0].image}{"\n"}' -ghcr.io/appscode-images/druid:30.0.1@sha256:4cd60a1dc6a124e27e91ec52ca39e2b9ca6809df915ae2dd712a2dd7462626d7 +ghcr.io/appscode-images/druid:36.0.0@sha256:4cd60a1dc6a124e27e91ec52ca39e2b9ca6809df915ae2dd712a2dd7462626d7 $ kubectl get pods -n demo druid-cluster-brokers-0 -o=jsonpath='{.spec.containers[0].image}{"\n"}' -ghcr.io/appscode-images/druid:30.0.1 +ghcr.io/appscode-images/druid:36.0.0 ``` You can see from above, our `Druid` has been updated with the new version. So, the updateVersion process is successfully completed. @@ -422,7 +422,7 @@ You can see from above, our `Druid` has been updated with the new version. So, t You can also see the version of druid cluster from the druid ui by following the steps described previously in this tutorial. [Check Druid Version from UI](/docs/guides/druid/update-version/guide.md/#Check-Druid-Version-from-UI) -If you follow the steps properly, you should be able to see that the version is upgraded to `30.0.1` from the druid console as shown below. +If you follow the steps properly, you should be able to see that the version is upgraded to `36.0.0` from the druid console as shown below.

  lifecycle diff --git a/docs/guides/druid/update-version/yamls/druid-cluster.yaml b/docs/guides/druid/update-version/yamls/druid-cluster.yaml index 7a89d0dc91..ebe7e8a404 100644 --- a/docs/guides/druid/update-version/yamls/druid-cluster.yaml +++ b/docs/guides/druid/update-version/yamls/druid-cluster.yaml @@ -4,7 +4,7 @@ metadata: name: druid-cluster namespace: demo spec: - version: 28.0.1 + version: 35.0.1 deepStorage: type: s3 configSecret: diff --git a/docs/guides/druid/update-version/yamls/update-version-ops.yaml b/docs/guides/druid/update-version/yamls/update-version-ops.yaml index b005719ef7..6da9b834da 100644 --- a/docs/guides/druid/update-version/yamls/update-version-ops.yaml +++ b/docs/guides/druid/update-version/yamls/update-version-ops.yaml @@ -8,6 +8,6 @@ spec: databaseRef: name: druid-cluster updateVersion: - targetVersion: 30.0.1 + targetVersion: 36.0.0 timeout: 5m apply: IfReady \ No newline at end of file diff --git a/docs/guides/druid/volume-expansion/guide.md b/docs/guides/druid/volume-expansion/guide.md index 96eed7eecc..deadb13186 100644 --- a/docs/guides/druid/volume-expansion/guide.md +++ b/docs/guides/druid/volume-expansion/guide.md @@ -105,7 +105,7 @@ $ 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 @@ -118,7 +118,7 @@ metadata: name: druid-cluster namespace: demo spec: - version: 28.0.1 + version: 36.0.0 deepStorage: type: s3 configSecret: @@ -159,11 +159,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 9s +druid-cluster kubedb.com/v1alpha2 36.0.0 Provisioning 0s +druid-cluster kubedb.com/v1alpha2 36.0.0 Provisioning 9s . . -druid-cluster kubedb.com/v1alpha2 28.0.1 Ready 3m26s +druid-cluster kubedb.com/v1alpha2 36.0.0 Ready 3m26s ``` Let's check volume size from petset, and from the persistent volume, diff --git a/docs/guides/druid/volume-expansion/yamls/druid-cluster.yaml b/docs/guides/druid/volume-expansion/yamls/druid-cluster.yaml index 235818e2c3..73b0871581 100644 --- a/docs/guides/druid/volume-expansion/yamls/druid-cluster.yaml +++ b/docs/guides/druid/volume-expansion/yamls/druid-cluster.yaml @@ -4,7 +4,7 @@ metadata: name: druid-cluster namespace: demo spec: - version: 28.0.1 + version: 36.0.0 deepStorage: type: s3 configSecret: