Update docs with KubeDB version v2024.12.18

docs/examples/kafka/autoscaler/kafka-combined.yaml

@@ -5,7 +5,7 @@ metadata:
   namespace: demo
 spec:
   replicas: 2
-  version: 3.6.1
+  version: 3.9.0
   podTemplate:
     spec:
       containers:

docs/examples/kafka/autoscaler/kafka-topology.yaml

@@ -4,7 +4,7 @@ metadata:
   name: kafka-prod
   namespace: demo
 spec:
-  version: 3.6.1
+  version: 3.9.0
   topology:
     broker:
       replicas: 2

docs/examples/kafka/clustering/kf-multinode.yaml

@@ -5,7 +5,7 @@ metadata:
   namespace: demo
 spec:
   replicas: 3
-  version: 3.6.1
+  version: 3.9.0
   storage:
     accessModes:
       - ReadWriteOnce

docs/examples/kafka/clustering/kf-standalone.yaml

@@ -5,7 +5,7 @@ metadata:
   namespace: demo
 spec:
   replicas: 1
-  version: 3.6.1
+  version: 3.9.0
   storage:
     accessModes:
       - ReadWriteOnce

docs/examples/kafka/clustering/kf-topology.yaml

@@ -4,7 +4,7 @@ metadata:
   name: kafka-prod
   namespace: demo
 spec:
-  version: 3.6.1
+  version: 3.9.0
   enableSSL: true
   tls:
     issuerRef:

docs/examples/kafka/configuration/kafka-combined.yaml

@@ -5,7 +5,7 @@ metadata:
   namespace: demo
 spec:
   replicas: 2
-  version: 3.6.1
+  version: 3.9.0
   configSecret:
     name: configsecret-combined
   storage:

docs/examples/kafka/configuration/kafka-topology.yaml

@@ -4,7 +4,7 @@ metadata:
   name: kafka-prod
   namespace: demo
 spec:
-  version: 3.6.1
+  version: 3.9.0
   configSecret:
     name: configsecret-topology
   topology:

docs/examples/kafka/connectcluster/connectcluster-quickstart.yaml

@@ -4,13 +4,13 @@ metadata:
   name: connectcluster-quickstart
   namespace: demo
 spec:
-  version: 3.6.1
+  version: 3.9.0
   replicas: 3
   connectorPlugins:
     - mongodb-1.11.0
-    - mysql-2.4.2.final
-    - postgres-2.4.2.final
-    - jdbc-2.6.1.final
+    - mysql-3.0.5.final
+    - postgres-3.0.5.final
+    - jdbc-3.0.5.final
   kafkaRef:
     name: kafka-quickstart
     namespace: demo

docs/examples/kafka/connectcluster/kcc-distributed.yaml

@@ -4,7 +4,7 @@ metadata:
   name: connectcluster-distributed
   namespace: demo
 spec:
-  version: 3.6.1
+  version: 3.9.0
   enableSSL: true
   tls:
     issuerRef:
@@ -15,8 +15,8 @@ spec:
     name: connectcluster-custom-config
   replicas: 3
   connectorPlugins:
-    - postgres-2.4.2.final
-    - jdbc-2.6.1.final
+    - postgres-3.0.5.final
+    - jdbc-3.0.5.final
   kafkaRef:
     name: kafka-prod
     namespace: demo

docs/examples/kafka/migration/mirror-connect.yaml

@@ -6,7 +6,7 @@ metadata:
 spec:
   authSecret:
     name: mirror-connect-auth
-  version: 3.6.1
+  version: 3.9.0
   replicas: 3
   kafkaRef:
     name: target-kafka

docs/examples/kafka/migration/source-kafka.yaml

@@ -7,7 +7,7 @@ spec:
   authSecret:
     name: source-kafka-auth
   replicas: 2
-  version: 3.6.1
+  version: 3.9.0
   storage:
     accessModes:
       - ReadWriteOnce

docs/examples/kafka/migration/target-cluster.yaml

@@ -6,7 +6,7 @@ metadata:
 spec:
   authSecret:
     name: target-kafka-auth
-  version: 3.6.1
+  version: 3.9.0
   topology:
     broker:
       replicas: 2

docs/examples/kafka/monitoring/kafka-builtin-prom.yaml

@@ -5,7 +5,7 @@ metadata:
   namespace: demo
 spec:
   replicas: 2
-  version: 3.6.1
+  version: 3.9.0
   storage:
     accessModes:
       - ReadWriteOnce

docs/examples/kafka/monitoring/kf-with-monitoring.yaml

@@ -11,7 +11,7 @@ spec:
       name: kafka-ca-issuer
       kind: Issuer
   replicas: 3
-  version: 3.6.1
+  version: 3.9.0
   storage:
     accessModes:
       - ReadWriteOnce

docs/examples/kafka/reconfigure-tls/kafka.yaml

@@ -4,7 +4,7 @@ metadata:
   name: kafka-prod
   namespace: demo
 spec:
-  version: 3.6.1
+  version: 3.9.0
   topology:
     broker:
       replicas: 2

docs/examples/kafka/reconfigure/kafka-combined.yaml

@@ -5,7 +5,7 @@ metadata:
   namespace: demo
 spec:
   replicas: 2
-  version: 3.6.1
+  version: 3.9.0
   configSecret:
     name: kf-combined-custom-config
   storage:

docs/examples/kafka/reconfigure/kafka-topology.yaml

@@ -4,7 +4,7 @@ metadata:
   name: kafka-prod
   namespace: demo
 spec:
-  version: 3.6.1
+  version: 3.9.0
   configSecret:
     name: kf-topology-custom-config
   topology:

docs/examples/kafka/restart/kafka.yaml

@@ -4,7 +4,7 @@ metadata:
   name: kafka-prod
   namespace: demo
 spec:
-  version: 3.6.1
+  version: 3.9.0
   topology:
     broker:
       replicas: 2

docs/examples/kafka/scaling/kafka-combined.yaml

@@ -5,7 +5,7 @@ metadata:
   namespace: demo
 spec:
   replicas: 2
-  version: 3.6.1
+  version: 3.9.0
   storage:
     accessModes:
       - ReadWriteOnce

docs/examples/kafka/scaling/kafka-topology.yaml

@@ -4,7 +4,7 @@ metadata:
   name: kafka-prod
   namespace: demo
 spec:
-  version: 3.6.1
+  version: 3.9.0
   topology:
     broker:
       replicas: 2

docs/examples/kafka/tls/connectcluster-tls.yaml

@@ -4,7 +4,7 @@ metadata:
   name: connectcluster-tls
   namespace: demo
 spec:
-  version: 3.6.1
+  version: 3.9.0
   enableSSL: true
   tls:
     issuerRef:
@@ -13,8 +13,8 @@ spec:
       name: connectcluster-ca-issuer
   replicas: 3
   connectorPlugins:
-    - postgres-2.4.2.final
-    - jdbc-2.6.1.final
+    - postgres-3.0.5.final
+    - jdbc-3.0.5.final
   kafkaRef:
     name: kafka-prod
     namespace: demo

docs/examples/kafka/tls/kafka-dev-tls.yaml

@@ -4,7 +4,7 @@ metadata:
   name: kafka-dev-tls
   namespace: demo
 spec:
-  version: 3.6.1
+  version: 3.9.0
   enableSSL: true
   tls:
     issuerRef:

docs/examples/kafka/tls/kafka-prod-tls.yaml

@@ -4,7 +4,7 @@ metadata:
   name: kafka-prod-tls
   namespace: demo
 spec:
-  version: 3.6.1
+  version: 3.9.0
   enableSSL: true
   tls:
     issuerRef:

docs/examples/kafka/update-version/kafka.yaml

@@ -4,7 +4,7 @@ metadata:
   name: kafka-prod
   namespace: demo
 spec:
-  version: 3.5.2
+  version: 3.8.1
   topology:
     broker:
       replicas: 2

docs/examples/kafka/update-version/update-version-ops.yaml

@@ -8,6 +8,6 @@ spec:
     databaseRef:
         name: kafka-prod
     updateVersion:
-        targetVersion: 3.6.1
+        targetVersion: 3.9.0
     timeout: 5m
     apply: IfReady

docs/examples/kafka/volume-expansion/kafka-combined.yaml

@@ -5,7 +5,7 @@ metadata:
   namespace: demo
 spec:
   replicas: 2
-  version: 3.6.1
+  version: 3.9.0
   storage:
     accessModes:
       - ReadWriteOnce

docs/examples/kafka/volume-expansion/kafka-topology.yaml

@@ -4,7 +4,7 @@ metadata:
   name: kafka-prod
   namespace: demo
 spec:
-  version: 3.6.1
+  version: 3.9.0
   topology:
     broker:
       replicas: 2

docs/guides/druid/backup/application-level/examples/sample-druid.yaml

@@ -4,7 +4,7 @@ metadata:
   name: sample-druid
   namespace: demo
 spec:
-  version: 30.0.0
+  version: 30.0.1
   deepStorage:
     type: s3
     configSecret:

docs/guides/druid/backup/application-level/index.md

@@ -114,7 +114,7 @@ metadata:
   name: sample-druid
   namespace: demo
 spec:
-  version: 30.0.0
+  version: 30.0.1
   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.0    Ready    4m14s
+sample-druid   kubedb.com/v1alpha2   30.0.1    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.0    4m7s
+sample-druid                  kubedb.com/druid       30.0.1    4m7s
 sample-druid-mysql-metadata   kubedb.com/mysql       8.0.35    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.0"}}
+      {"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"}}
   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.0
+  version: 30.0.1
 ```
 
 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.0
+    kubedb.com/db-version: 30.0.1
   creationTimestamp: "2024-09-20T11:09:00Z"
   finalizers:
     - kubestash.com/cleanup
@@ -707,7 +707,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.0    Ready    39m
+restored-druid   30.0.1    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.
@@ -733,7 +733,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.0    Ready   34m
+restored-druid   30.0.1    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,

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.0
+  version: 30.0.1
   deepStorage:
     type: s3
     configSecret:

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.0
+  version: 30.0.1
   deepStorage:
     type: s3
     configSecret: