@@ -114,7 +114,7 @@ metadata:
114
114
name: sample-druid
115
115
namespace: demo
116
116
spec:
117
- version: 30.0.0
117
+ version: 30.0.1
118
118
deepStorage:
119
119
type: s3
120
120
configSecret:
@@ -143,7 +143,7 @@ Let's check if the database is ready to use,
143
143
` ` ` bash
144
144
$ kubectl get druids.kubedb.com -n demo
145
145
NAME TYPE VERSION STATUS AGE
146
- sample-druid kubedb.com/v1alpha2 30.0.0 Ready 4m14s
146
+ sample-druid kubedb.com/v1alpha2 30.0.1 Ready 4m14s
147
147
` ` `
148
148
149
149
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
183
183
` ` ` bash
184
184
$ kubectl get appbindings -n demo
185
185
NAME TYPE VERSION AGE
186
- sample-druid kubedb.com/druid 30.0.0 4m7s
186
+ sample-druid kubedb.com/druid 30.0.1 4m7s
187
187
sample-druid-mysql-metadata kubedb.com/mysql 8.0.35 6m31s
188
188
sample-druid-zk kubedb.com/zookeeper 3.7.2 6m34s
189
189
` ` `
@@ -202,7 +202,7 @@ kind: AppBinding
202
202
metadata:
203
203
annotations:
204
204
kubectl.kubernetes.io/last-applied-configuration: |
205
- {"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 "}}
205
+ {"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 "}}
206
206
creationTimestamp: "2024-09-19T13:02:20Z"
207
207
generation: 1
208
208
labels:
@@ -236,7 +236,7 @@ spec:
236
236
secret:
237
237
name: sample-druid-admin-cred
238
238
type: kubedb.com/druid
239
- version: 30.0.0
239
+ version: 30.0.1
240
240
` ` `
241
241
242
242
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
544
544
kind: Snapshot
545
545
metadata:
546
546
annotations:
547
- kubedb.com/db-version: 30.0.0
547
+ kubedb.com/db-version: 30.0.1
548
548
creationTimestamp: "2024-09-20T11:09:00Z"
549
549
finalizers:
550
550
- kubestash.com/cleanup
@@ -707,7 +707,7 @@ In this section, we will verify whether the desired `Druid` database manifest ha
707
707
` ` ` bash
708
708
$ kubectl get druids.kubedb.com -n dev
709
709
NAME VERSION STATUS AGE
710
- restored-druid 30.0.0 Ready 39m
710
+ restored-druid 30.0.1 Ready 39m
711
711
` ` `
712
712
713
713
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
733
733
` ` ` bash
734
734
$ kubectl get druid -n dev restored-druid
735
735
NAME VERSION STATUS AGE
736
- restored-druid 30.0.0 Ready 34m
736
+ restored-druid 30.0.1 Ready 34m
737
737
` ` `
738
738
739
739
Now, let's verify if our datasource `wikipedia` exists or not. For that, first find out the database `Sevices` by the following command,
0 commit comments