diff --git a/docs/examples/elasticsearch/cli/elasticsearch-demo.yaml b/docs/examples/elasticsearch/cli/elasticsearch-demo.yaml index 47f3840ef5..4f0e209cbd 100644 --- a/docs/examples/elasticsearch/cli/elasticsearch-demo.yaml +++ b/docs/examples/elasticsearch/cli/elasticsearch-demo.yaml @@ -4,7 +4,7 @@ metadata: name: elasticsearch-demo namespace: demo spec: - version: searchguard-7.9.3 + version: xpack-8.11.1 storage: storageClassName: "standard" accessModes: diff --git a/docs/examples/elasticsearch/clustering/multi-node-es.yaml b/docs/examples/elasticsearch/clustering/multi-node-es.yaml index e550d55eac..f6593e3df6 100644 --- a/docs/examples/elasticsearch/clustering/multi-node-es.yaml +++ b/docs/examples/elasticsearch/clustering/multi-node-es.yaml @@ -4,7 +4,7 @@ metadata: name: multi-node-es namespace: demo spec: - version: searchguard-7.9.3 + version: xpack-8.11.1 replicas: 3 storageType: Durable storage: diff --git a/docs/examples/elasticsearch/clustering/topology-es.yaml b/docs/examples/elasticsearch/clustering/topology-es.yaml index be3c99cb68..1522b9f866 100644 --- a/docs/examples/elasticsearch/clustering/topology-es.yaml +++ b/docs/examples/elasticsearch/clustering/topology-es.yaml @@ -4,7 +4,7 @@ metadata: name: topology-es namespace: demo spec: - version: searchguard-7.9.3 + version: xpack-8.11.1 storageType: Durable topology: master: diff --git a/docs/examples/elasticsearch/custom-config/es-custom-with-topology.yaml b/docs/examples/elasticsearch/custom-config/es-custom-with-topology.yaml index 078f4fcf36..d20a480604 100644 --- a/docs/examples/elasticsearch/custom-config/es-custom-with-topology.yaml +++ b/docs/examples/elasticsearch/custom-config/es-custom-with-topology.yaml @@ -4,7 +4,7 @@ metadata: name: custom-elasticsearch namespace: demo spec: - version: searchguard-7.9.3 + version: xpack-8.11.1 configSecret: name: es-custom-config topology: diff --git a/docs/examples/elasticsearch/custom-config/es-custom.yaml b/docs/examples/elasticsearch/custom-config/es-custom.yaml index 2c875a44c8..53e58159b9 100644 --- a/docs/examples/elasticsearch/custom-config/es-custom.yaml +++ b/docs/examples/elasticsearch/custom-config/es-custom.yaml @@ -4,7 +4,7 @@ metadata: name: custom-elasticsearch namespace: demo spec: - version: searchguard-7.9.3 + version: xpack-8.11.1 replicas: 2 configSecret: name: es-custom-config diff --git a/docs/examples/elasticsearch/custom-rbac/es-custom-db-two.yaml b/docs/examples/elasticsearch/custom-rbac/es-custom-db-two.yaml index 1c84afdd1c..f62381d39b 100644 --- a/docs/examples/elasticsearch/custom-rbac/es-custom-db-two.yaml +++ b/docs/examples/elasticsearch/custom-rbac/es-custom-db-two.yaml @@ -4,7 +4,7 @@ metadata: name: minute-elasticsearch namespace: demo spec: - version: searchguard-7.9.3 + version: xpack-8.11.1 storageType: Durable podTemplate: spec: diff --git a/docs/examples/elasticsearch/custom-rbac/es-custom-db.yaml b/docs/examples/elasticsearch/custom-rbac/es-custom-db.yaml index 426b8a9058..36b246721d 100644 --- a/docs/examples/elasticsearch/custom-rbac/es-custom-db.yaml +++ b/docs/examples/elasticsearch/custom-rbac/es-custom-db.yaml @@ -4,7 +4,7 @@ metadata: name: quick-elasticsearch namespace: demo spec: - version: searchguard-7.9.3 + version: xpack-8.11.1 storageType: Durable podTemplate: spec: diff --git a/docs/examples/elasticsearch/es-overview.yaml b/docs/examples/elasticsearch/es-overview.yaml index 1c5a5dd6cb..f9543d4e02 100644 --- a/docs/examples/elasticsearch/es-overview.yaml +++ b/docs/examples/elasticsearch/es-overview.yaml @@ -4,7 +4,7 @@ metadata: name: e1 namespace: demo spec: - version: searchguard-7.9.3 + version: xpack-8.11.1 replicas: 2 enableSSL: true authSecret: diff --git a/docs/examples/elasticsearch/initialization/recovered-es.yaml b/docs/examples/elasticsearch/initialization/recovered-es.yaml index bf1a4b9cee..5b9defde48 100644 --- a/docs/examples/elasticsearch/initialization/recovered-es.yaml +++ b/docs/examples/elasticsearch/initialization/recovered-es.yaml @@ -4,7 +4,7 @@ metadata: name: recovered-es namespace: demo spec: - version: searchguard-7.9.3 + version: xpack-8.11.1 authSecret: name: instant-elasticsearch-auth storageType: Durable diff --git a/docs/examples/elasticsearch/kibana/es-kibana-demo.yaml b/docs/examples/elasticsearch/kibana/es-kibana-demo.yaml index 9cae575cf2..0eefcc1dd3 100644 --- a/docs/examples/elasticsearch/kibana/es-kibana-demo.yaml +++ b/docs/examples/elasticsearch/kibana/es-kibana-demo.yaml @@ -4,7 +4,7 @@ metadata: name: es-kibana-demo namespace: demo spec: - version: searchguard-7.9.3 + version: xpack-8.11.1 replicas: 1 authSecret: name: es-auth diff --git a/docs/examples/elasticsearch/monitoring/builtin-prom-es.yaml b/docs/examples/elasticsearch/monitoring/builtin-prom-es.yaml index 1acc4189d9..848c15a26b 100644 --- a/docs/examples/elasticsearch/monitoring/builtin-prom-es.yaml +++ b/docs/examples/elasticsearch/monitoring/builtin-prom-es.yaml @@ -4,7 +4,7 @@ metadata: name: builtin-prom-es namespace: demo spec: - version: searchguard-7.9.3 + version: xpack-8.11.1 terminationPolicy: WipeOut storage: storageClassName: "standard" diff --git a/docs/examples/elasticsearch/monitoring/coreos-prom-es.yaml b/docs/examples/elasticsearch/monitoring/coreos-prom-es.yaml index 5111751ca4..6e0a0fe869 100644 --- a/docs/examples/elasticsearch/monitoring/coreos-prom-es.yaml +++ b/docs/examples/elasticsearch/monitoring/coreos-prom-es.yaml @@ -4,7 +4,7 @@ metadata: name: coreos-prom-es namespace: demo spec: - version: searchguard-7.9.3 + version: xpack-8.11.1 terminationPolicy: WipeOut storage: storageClassName: "standard" diff --git a/docs/examples/elasticsearch/private-registry/private-registry.yaml b/docs/examples/elasticsearch/private-registry/private-registry.yaml index a14cecb622..37b3c7fccc 100644 --- a/docs/examples/elasticsearch/private-registry/private-registry.yaml +++ b/docs/examples/elasticsearch/private-registry/private-registry.yaml @@ -4,7 +4,7 @@ metadata: name: searchguard-793 namespace: demo spec: - version: searchguard-7.9.3 + version: xpack-8.11.1 storage: storageClassName: "standard" accessModes: diff --git a/docs/examples/elasticsearch/private-registry/pvt-elasticsearchversion.yaml b/docs/examples/elasticsearch/private-registry/pvt-elasticsearchversion.yaml index 7fe914b4f7..41f36983bc 100644 --- a/docs/examples/elasticsearch/private-registry/pvt-elasticsearchversion.yaml +++ b/docs/examples/elasticsearch/private-registry/pvt-elasticsearchversion.yaml @@ -1,7 +1,7 @@ apiVersion: catalog.kubedb.com/v1alpha1 kind: ElasticsearchVersion metadata: - name: searchguard-7.9.3 + name: xpack-8.11.1 spec: authPlugin: SearchGuard db: diff --git a/docs/examples/elasticsearch/quickstart/instant-elasticsearch.yaml b/docs/examples/elasticsearch/quickstart/instant-elasticsearch.yaml index 991687755a..74d5a9f5cf 100644 --- a/docs/examples/elasticsearch/quickstart/instant-elasticsearch.yaml +++ b/docs/examples/elasticsearch/quickstart/instant-elasticsearch.yaml @@ -4,6 +4,6 @@ metadata: name: instant-elasticsearch namespace: demo spec: - version: searchguard-7.9.3 + version: xpack-8.11.1 replicas: 1 storageType: Ephemeral diff --git a/docs/examples/elasticsearch/quickstart/quick-elasticsearch.yaml b/docs/examples/elasticsearch/quickstart/quick-elasticsearch.yaml index 4dd315a975..a4770dfb8b 100644 --- a/docs/examples/elasticsearch/quickstart/quick-elasticsearch.yaml +++ b/docs/examples/elasticsearch/quickstart/quick-elasticsearch.yaml @@ -4,7 +4,7 @@ metadata: name: es-quickstart namespace: demo spec: - version: xpack-8.2.0 + version: xpack-8.2.3 storageType: Durable storage: storageClassName: "standard" diff --git a/docs/examples/elasticsearch/x-pack/config-elasticsearch.yaml b/docs/examples/elasticsearch/x-pack/config-elasticsearch.yaml index f5e67391f6..487f3924c5 100644 --- a/docs/examples/elasticsearch/x-pack/config-elasticsearch.yaml +++ b/docs/examples/elasticsearch/x-pack/config-elasticsearch.yaml @@ -4,7 +4,7 @@ metadata: name: config-elasticsearch namespace: demo spec: - version: searchguard-7.9.3 + version: xpack-8.11.1 storage: storageClassName: "standard" accessModes: diff --git a/docs/examples/elasticsearch/x-pack/custom-certificate-es-ssl.yaml b/docs/examples/elasticsearch/x-pack/custom-certificate-es-ssl.yaml index 6f56cd8bd1..4f296e0f00 100644 --- a/docs/examples/elasticsearch/x-pack/custom-certificate-es-ssl.yaml +++ b/docs/examples/elasticsearch/x-pack/custom-certificate-es-ssl.yaml @@ -4,7 +4,7 @@ metadata: name: custom-certificate-es-ssl namespace: demo spec: - version: searchguard-7.9.3 + version: xpack-8.11.1 enableSSL: true storage: storageClassName: "standard" diff --git a/docs/examples/elasticsearch/x-pack/es-mon-demo.yaml b/docs/examples/elasticsearch/x-pack/es-mon-demo.yaml index e59f9baa8c..12195473d2 100644 --- a/docs/examples/elasticsearch/x-pack/es-mon-demo.yaml +++ b/docs/examples/elasticsearch/x-pack/es-mon-demo.yaml @@ -4,7 +4,7 @@ metadata: name: es-mon-demo namespace: demo spec: - version: searchguard-7.9.3 + version: xpack-8.11.1 replicas: 1 authSecret: name: es-auth diff --git a/docs/examples/elasticsearch/x-pack/es-xpack-disabled.yaml b/docs/examples/elasticsearch/x-pack/es-xpack-disabled.yaml index d5b85983c6..8b3b2a196e 100644 --- a/docs/examples/elasticsearch/x-pack/es-xpack-disabled.yaml +++ b/docs/examples/elasticsearch/x-pack/es-xpack-disabled.yaml @@ -4,7 +4,7 @@ metadata: name: es-xpack-disabled namespace: demo spec: - version: searchguard-7.9.3 + version: xpack-8.11.1 disableSecurity: true storage: storageClassName: "standard" diff --git a/docs/examples/elasticsearch/x-pack/esversion-none.yaml b/docs/examples/elasticsearch/x-pack/esversion-none.yaml index fb641021f6..49332f2959 100644 --- a/docs/examples/elasticsearch/x-pack/esversion-none.yaml +++ b/docs/examples/elasticsearch/x-pack/esversion-none.yaml @@ -1,7 +1,7 @@ apiVersion: catalog.kubedb.com/v1alpha1 kind: ElasticsearchVersion metadata: - name: searchguard-7.9.3 + name: xpack-8.11.1 spec: authPlugin: SearchGuard db: diff --git a/docs/examples/elasticsearch/x-pack/ssl-elasticsearch.yaml b/docs/examples/elasticsearch/x-pack/ssl-elasticsearch.yaml index 7de3a3c76a..8393c7d96c 100644 --- a/docs/examples/elasticsearch/x-pack/ssl-elasticsearch.yaml +++ b/docs/examples/elasticsearch/x-pack/ssl-elasticsearch.yaml @@ -4,7 +4,7 @@ metadata: name: ssl-elasticsearch namespace: demo spec: - version: searchguard-7.9.3 + version: xpack-8.11.1 replicas: 2 enableSSL: true storage: diff --git a/docs/examples/mongodb/Initialization/demo-1.yaml b/docs/examples/mongodb/Initialization/demo-1.yaml index 4824ac217c..3a0f99606d 100644 --- a/docs/examples/mongodb/Initialization/demo-1.yaml +++ b/docs/examples/mongodb/Initialization/demo-1.yaml @@ -4,7 +4,7 @@ metadata: name: mgo-init-script namespace: demo spec: - version: "4.2.3" + version: "4.4.26" storage: storageClassName: "standard" accessModes: diff --git a/docs/examples/mongodb/arbiter/replicaset.yaml b/docs/examples/mongodb/arbiter/replicaset.yaml index d189d4b49b..b9e71c6266 100644 --- a/docs/examples/mongodb/arbiter/replicaset.yaml +++ b/docs/examples/mongodb/arbiter/replicaset.yaml @@ -4,7 +4,7 @@ metadata: name: mongo-arb namespace: demo spec: - version: "4.4.6" + version: "4.4.26" replicaSet: name: "rs0" replicas: 2 diff --git a/docs/examples/mongodb/arbiter/sharding.yaml b/docs/examples/mongodb/arbiter/sharding.yaml index ad4bea1daa..5fc81ed684 100644 --- a/docs/examples/mongodb/arbiter/sharding.yaml +++ b/docs/examples/mongodb/arbiter/sharding.yaml @@ -4,7 +4,7 @@ metadata: name: mongo-sh-arb namespace: demo spec: - version: "4.4.6" + version: "4.4.26" shardTopology: configServer: replicas: 3 diff --git a/docs/examples/mongodb/autoscaling/compute/mg-rs.yaml b/docs/examples/mongodb/autoscaling/compute/mg-rs.yaml index 50ad896494..ccd96941a0 100644 --- a/docs/examples/mongodb/autoscaling/compute/mg-rs.yaml +++ b/docs/examples/mongodb/autoscaling/compute/mg-rs.yaml @@ -4,7 +4,7 @@ metadata: name: mg-rs namespace: demo spec: - version: "4.2.3" + version: "4.4.26" replicaSet: name: "replicaset" replicas: 3 diff --git a/docs/examples/mongodb/autoscaling/compute/mg-sh.yaml b/docs/examples/mongodb/autoscaling/compute/mg-sh.yaml index cb2dbce8ec..a31103482e 100644 --- a/docs/examples/mongodb/autoscaling/compute/mg-sh.yaml +++ b/docs/examples/mongodb/autoscaling/compute/mg-sh.yaml @@ -4,7 +4,7 @@ metadata: name: mg-sh namespace: demo spec: - version: "4.2.3" + version: "4.4.26" storageType: Durable shardTopology: configServer: diff --git a/docs/examples/mongodb/autoscaling/compute/mg-standalone.yaml b/docs/examples/mongodb/autoscaling/compute/mg-standalone.yaml index d0fb310e74..5ff2b0c233 100644 --- a/docs/examples/mongodb/autoscaling/compute/mg-standalone.yaml +++ b/docs/examples/mongodb/autoscaling/compute/mg-standalone.yaml @@ -4,7 +4,7 @@ metadata: name: mg-standalone namespace: demo spec: - version: "4.2.3" + version: "4.4.26" storageType: Durable storage: resources: diff --git a/docs/examples/mongodb/autoscaling/storage/mg-rs.yaml b/docs/examples/mongodb/autoscaling/storage/mg-rs.yaml index 5965f148be..db194ef615 100644 --- a/docs/examples/mongodb/autoscaling/storage/mg-rs.yaml +++ b/docs/examples/mongodb/autoscaling/storage/mg-rs.yaml @@ -4,7 +4,7 @@ metadata: name: mg-rs namespace: demo spec: - version: "4.2.3" + version: "4.4.26" replicaSet: name: "replicaset" replicas: 3 diff --git a/docs/examples/mongodb/autoscaling/storage/mg-sh.yaml b/docs/examples/mongodb/autoscaling/storage/mg-sh.yaml index a078d9531b..f4d6e876cb 100644 --- a/docs/examples/mongodb/autoscaling/storage/mg-sh.yaml +++ b/docs/examples/mongodb/autoscaling/storage/mg-sh.yaml @@ -4,7 +4,7 @@ metadata: name: mg-sh namespace: demo spec: - version: "4.2.3" + version: "4.4.26" storageType: Durable shardTopology: configServer: diff --git a/docs/examples/mongodb/autoscaling/storage/mg-standalone.yaml b/docs/examples/mongodb/autoscaling/storage/mg-standalone.yaml index c2b31988ec..3250b67466 100644 --- a/docs/examples/mongodb/autoscaling/storage/mg-standalone.yaml +++ b/docs/examples/mongodb/autoscaling/storage/mg-standalone.yaml @@ -4,7 +4,7 @@ metadata: name: mg-standalone namespace: demo spec: - version: "4.2.3" + version: "4.4.26" storageType: Durable storage: storageClassName: topolvm-provisioner diff --git a/docs/examples/mongodb/cli/mongodb-demo.yaml b/docs/examples/mongodb/cli/mongodb-demo.yaml index 31a5ea4efd..b21005cbbb 100644 --- a/docs/examples/mongodb/cli/mongodb-demo.yaml +++ b/docs/examples/mongodb/cli/mongodb-demo.yaml @@ -4,7 +4,7 @@ metadata: name: mongodb-demo namespace: demo spec: - version: "4.2.3" + version: "4.4.26" storage: storageClassName: "standard" accessModes: diff --git a/docs/examples/mongodb/clustering/mongo-sharding.yaml b/docs/examples/mongodb/clustering/mongo-sharding.yaml index b7676ae928..a1158fba09 100644 --- a/docs/examples/mongodb/clustering/mongo-sharding.yaml +++ b/docs/examples/mongodb/clustering/mongo-sharding.yaml @@ -4,7 +4,7 @@ metadata: name: mongo-sh namespace: demo spec: - version: 4.2.3 + version: 4.4.26 shardTopology: configServer: replicas: 3 diff --git a/docs/examples/mongodb/clustering/replicaset.yaml b/docs/examples/mongodb/clustering/replicaset.yaml index d862f36779..0b3607ba0a 100644 --- a/docs/examples/mongodb/clustering/replicaset.yaml +++ b/docs/examples/mongodb/clustering/replicaset.yaml @@ -4,7 +4,7 @@ metadata: name: mgo-replicaset namespace: demo spec: - version: "4.2.3" + version: "4.4.26" replicas: 3 replicaSet: name: rs0 diff --git a/docs/examples/mongodb/clustering/standalone.yaml b/docs/examples/mongodb/clustering/standalone.yaml index 5b6d98eecd..2ad99d0c82 100644 --- a/docs/examples/mongodb/clustering/standalone.yaml +++ b/docs/examples/mongodb/clustering/standalone.yaml @@ -4,7 +4,7 @@ metadata: name: mg-alone namespace: demo spec: - version: "4.2.3" + version: "4.4.26" podTemplate: spec: resources: diff --git a/docs/examples/mongodb/configuration/demo-1.yaml b/docs/examples/mongodb/configuration/demo-1.yaml index cf2f83a954..066b831b4c 100644 --- a/docs/examples/mongodb/configuration/demo-1.yaml +++ b/docs/examples/mongodb/configuration/demo-1.yaml @@ -4,7 +4,7 @@ metadata: name: mgo-custom-config namespace: demo spec: - version: "4.2.3" + version: "4.4.26" storageType: Durable storage: storageClassName: "standard" diff --git a/docs/examples/mongodb/configuration/mgo-misc-config.yaml b/docs/examples/mongodb/configuration/mgo-misc-config.yaml index cbc6894be2..a164b01a63 100644 --- a/docs/examples/mongodb/configuration/mgo-misc-config.yaml +++ b/docs/examples/mongodb/configuration/mgo-misc-config.yaml @@ -4,7 +4,7 @@ metadata: name: mgo-misc-config namespace: demo spec: - version: "4.2.3" + version: "4.4.26" storageType: "Durable" storage: storageClassName: "standard" diff --git a/docs/examples/mongodb/custom-rbac/mg-custom-db-two.yaml b/docs/examples/mongodb/custom-rbac/mg-custom-db-two.yaml index afbc71360a..bd85719647 100644 --- a/docs/examples/mongodb/custom-rbac/mg-custom-db-two.yaml +++ b/docs/examples/mongodb/custom-rbac/mg-custom-db-two.yaml @@ -4,7 +4,7 @@ metadata: name: minute-mongodb namespace: demo spec: - version: "4.2.3" + version: "4.4.26" storageType: Durable podTemplate: spec: diff --git a/docs/examples/mongodb/custom-rbac/mg-custom-db.yaml b/docs/examples/mongodb/custom-rbac/mg-custom-db.yaml index 3f3c5b5a3f..d224d1166a 100644 --- a/docs/examples/mongodb/custom-rbac/mg-custom-db.yaml +++ b/docs/examples/mongodb/custom-rbac/mg-custom-db.yaml @@ -4,7 +4,7 @@ metadata: name: quick-mongodb namespace: demo spec: - version: "4.2.3" + version: "4.4.26" storageType: Durable podTemplate: spec: diff --git a/docs/examples/mongodb/monitoring/builtin-prom-mgo.yaml b/docs/examples/mongodb/monitoring/builtin-prom-mgo.yaml index 03b346f009..a3a595a49b 100644 --- a/docs/examples/mongodb/monitoring/builtin-prom-mgo.yaml +++ b/docs/examples/mongodb/monitoring/builtin-prom-mgo.yaml @@ -4,7 +4,7 @@ metadata: name: builtin-prom-mgo namespace: demo spec: - version: "4.2.3" + version: "4.4.26" terminationPolicy: WipeOut storage: storageClassName: "standard" diff --git a/docs/examples/mongodb/monitoring/coreos-prom-mgo.yaml b/docs/examples/mongodb/monitoring/coreos-prom-mgo.yaml index 76076f7abb..55a607da18 100644 --- a/docs/examples/mongodb/monitoring/coreos-prom-mgo.yaml +++ b/docs/examples/mongodb/monitoring/coreos-prom-mgo.yaml @@ -4,7 +4,7 @@ metadata: name: coreos-prom-mgo namespace: demo spec: - version: "4.2.3" + version: "4.4.26" terminationPolicy: WipeOut storage: storageClassName: "standard" diff --git a/docs/examples/mongodb/private-registry/demo-1.yaml b/docs/examples/mongodb/private-registry/demo-1.yaml index 56c8e4f13b..1bdd213e59 100644 --- a/docs/examples/mongodb/private-registry/demo-1.yaml +++ b/docs/examples/mongodb/private-registry/demo-1.yaml @@ -4,7 +4,7 @@ metadata: name: mgo-pvt-reg namespace: demo spec: - version: 4.2.3 + version: 4.4.26 storage: storageClassName: "standard" accessModes: diff --git a/docs/examples/mongodb/quickstart/replicaset.yaml b/docs/examples/mongodb/quickstart/replicaset.yaml index ba84cbfd28..bfef48b556 100644 --- a/docs/examples/mongodb/quickstart/replicaset.yaml +++ b/docs/examples/mongodb/quickstart/replicaset.yaml @@ -4,7 +4,7 @@ metadata: name: mgo-quickstart namespace: demo spec: - version: "4.4.6" + version: "4.4.26" replicaSet: name: "rs1" replicas: 3 diff --git a/docs/examples/mongodb/reconfigure-tls/mg-replicaset.yaml b/docs/examples/mongodb/reconfigure-tls/mg-replicaset.yaml index 9bbef94636..399b9daaa0 100644 --- a/docs/examples/mongodb/reconfigure-tls/mg-replicaset.yaml +++ b/docs/examples/mongodb/reconfigure-tls/mg-replicaset.yaml @@ -4,7 +4,7 @@ metadata: name: mg-rs namespace: demo spec: - version: "4.2.3" + version: "4.4.26" replicas: 3 replicaSet: name: rs0 diff --git a/docs/examples/mongodb/reconfigure/mg-replicaset-config.yaml b/docs/examples/mongodb/reconfigure/mg-replicaset-config.yaml index 1981db9aa7..2a32cbb179 100644 --- a/docs/examples/mongodb/reconfigure/mg-replicaset-config.yaml +++ b/docs/examples/mongodb/reconfigure/mg-replicaset-config.yaml @@ -4,7 +4,7 @@ metadata: name: mg-replicaset namespace: demo spec: - version: "4.2.3" + version: "4.4.26" replicas: 3 replicaSet: name: rs0 diff --git a/docs/examples/mongodb/reconfigure/mg-shard-config.yaml b/docs/examples/mongodb/reconfigure/mg-shard-config.yaml index 218bd5bda5..c5007872c8 100644 --- a/docs/examples/mongodb/reconfigure/mg-shard-config.yaml +++ b/docs/examples/mongodb/reconfigure/mg-shard-config.yaml @@ -4,7 +4,7 @@ metadata: name: mg-sharding namespace: demo spec: - version: 4.2.3 + version: 4.4.26 shardTopology: configServer: replicas: 3 diff --git a/docs/examples/mongodb/reconfigure/mg-standalone-config.yaml b/docs/examples/mongodb/reconfigure/mg-standalone-config.yaml index 0ca919b771..ac2cce3615 100644 --- a/docs/examples/mongodb/reconfigure/mg-standalone-config.yaml +++ b/docs/examples/mongodb/reconfigure/mg-standalone-config.yaml @@ -4,7 +4,7 @@ metadata: name: mg-standalone namespace: demo spec: - version: "4.2.3" + version: "4.4.26" storageType: Durable storage: storageClassName: "standard" diff --git a/docs/examples/mongodb/reprovision/mongo.yaml b/docs/examples/mongodb/reprovision/mongo.yaml index af70cd97d5..384f3a4317 100644 --- a/docs/examples/mongodb/reprovision/mongo.yaml +++ b/docs/examples/mongodb/reprovision/mongo.yaml @@ -4,7 +4,7 @@ metadata: name: mongo namespace: demo spec: - version: "4.4.6" + version: "4.4.26" replicaSet: name: "replicaset" podTemplate: diff --git a/docs/examples/mongodb/restart/mongo.yaml b/docs/examples/mongodb/restart/mongo.yaml index af70cd97d5..384f3a4317 100644 --- a/docs/examples/mongodb/restart/mongo.yaml +++ b/docs/examples/mongodb/restart/mongo.yaml @@ -4,7 +4,7 @@ metadata: name: mongo namespace: demo spec: - version: "4.4.6" + version: "4.4.26" replicaSet: name: "replicaset" podTemplate: diff --git a/docs/examples/mongodb/scaling/mg-replicaset.yaml b/docs/examples/mongodb/scaling/mg-replicaset.yaml index 06505ffc58..777010ad0e 100644 --- a/docs/examples/mongodb/scaling/mg-replicaset.yaml +++ b/docs/examples/mongodb/scaling/mg-replicaset.yaml @@ -4,7 +4,7 @@ metadata: name: mg-replicaset namespace: demo spec: - version: "4.2.3" + version: "4.4.26" replicaSet: name: "replicaset" replicas: 3 diff --git a/docs/examples/mongodb/scaling/mg-shard.yaml b/docs/examples/mongodb/scaling/mg-shard.yaml index cf893f2825..d500656b05 100644 --- a/docs/examples/mongodb/scaling/mg-shard.yaml +++ b/docs/examples/mongodb/scaling/mg-shard.yaml @@ -4,7 +4,7 @@ metadata: name: mg-sharding namespace: demo spec: - version: 4.2.3 + version: 4.4.26 shardTopology: configServer: replicas: 3 diff --git a/docs/examples/mongodb/scaling/mg-standalone.yaml b/docs/examples/mongodb/scaling/mg-standalone.yaml index f756dd6f18..b625c062bc 100644 --- a/docs/examples/mongodb/scaling/mg-standalone.yaml +++ b/docs/examples/mongodb/scaling/mg-standalone.yaml @@ -4,7 +4,7 @@ metadata: name: mg-standalone namespace: demo spec: - version: "4.2.3" + version: "4.4.26" storageType: Durable storage: storageClassName: "standard" diff --git a/docs/examples/mongodb/tls/mg-replicaset-ssl.yaml b/docs/examples/mongodb/tls/mg-replicaset-ssl.yaml index 02a42a8ac8..9205a98070 100644 --- a/docs/examples/mongodb/tls/mg-replicaset-ssl.yaml +++ b/docs/examples/mongodb/tls/mg-replicaset-ssl.yaml @@ -4,7 +4,7 @@ metadata: name: mgo-rs-tls namespace: demo spec: - version: "4.1.13-v1" + version: "4.4.26" sslMode: requireSSL tls: issuerRef: diff --git a/docs/examples/mongodb/tls/mg-shard-ssl.yaml b/docs/examples/mongodb/tls/mg-shard-ssl.yaml index 5be5d7841e..eae445d61a 100644 --- a/docs/examples/mongodb/tls/mg-shard-ssl.yaml +++ b/docs/examples/mongodb/tls/mg-shard-ssl.yaml @@ -4,7 +4,7 @@ metadata: name: mongo-sh-tls namespace: demo spec: - version: "4.1.13-v1" + version: "4.4.26" sslMode: requireSSL tls: issuerRef: diff --git a/docs/examples/mongodb/tls/mg-standalone-ssl.yaml b/docs/examples/mongodb/tls/mg-standalone-ssl.yaml index 17d7e9fa18..24be9f30a5 100644 --- a/docs/examples/mongodb/tls/mg-standalone-ssl.yaml +++ b/docs/examples/mongodb/tls/mg-standalone-ssl.yaml @@ -4,7 +4,7 @@ metadata: name: mgo-tls namespace: demo spec: - version: "4.1.13-v1" + version: "4.4.26" sslMode: requireSSL tls: issuerRef: diff --git a/docs/examples/mongodb/update-version/mg-replicaset.yaml b/docs/examples/mongodb/update-version/mg-replicaset.yaml index 270f5b777c..c8890a60dd 100644 --- a/docs/examples/mongodb/update-version/mg-replicaset.yaml +++ b/docs/examples/mongodb/update-version/mg-replicaset.yaml @@ -4,7 +4,7 @@ metadata: name: mg-replicaset namespace: demo spec: - version: "3.6.8-v1" + version: "4.4.26" replicaSet: name: "replicaset" replicas: 3 diff --git a/docs/examples/mongodb/update-version/mg-shard.yaml b/docs/examples/mongodb/update-version/mg-shard.yaml index 67e01aac8d..76304853c1 100644 --- a/docs/examples/mongodb/update-version/mg-shard.yaml +++ b/docs/examples/mongodb/update-version/mg-shard.yaml @@ -4,7 +4,7 @@ metadata: name: mg-sharding namespace: demo spec: - version: 3.6.8-v1 + version: 4.4.26 shardTopology: configServer: replicas: 2 diff --git a/docs/examples/mongodb/update-version/mg-standalone.yaml b/docs/examples/mongodb/update-version/mg-standalone.yaml index 76f2374495..d2de03e594 100644 --- a/docs/examples/mongodb/update-version/mg-standalone.yaml +++ b/docs/examples/mongodb/update-version/mg-standalone.yaml @@ -4,7 +4,7 @@ metadata: name: mg-standalone namespace: demo spec: - version: "3.6.8-v1" + version: "4.4.26" storageType: Durable storage: storageClassName: "standard" diff --git a/docs/examples/mongodb/volume-expansion/mg-replicaset.yaml b/docs/examples/mongodb/volume-expansion/mg-replicaset.yaml index 8315516688..367336370f 100644 --- a/docs/examples/mongodb/volume-expansion/mg-replicaset.yaml +++ b/docs/examples/mongodb/volume-expansion/mg-replicaset.yaml @@ -4,7 +4,7 @@ metadata: name: mg-replicaset namespace: demo spec: - version: "4.2.3" + version: "4.4.26" replicaSet: name: "replicaset" replicas: 3 diff --git a/docs/examples/mongodb/volume-expansion/mg-shard.yaml b/docs/examples/mongodb/volume-expansion/mg-shard.yaml index be8003d849..76304853c1 100644 --- a/docs/examples/mongodb/volume-expansion/mg-shard.yaml +++ b/docs/examples/mongodb/volume-expansion/mg-shard.yaml @@ -4,7 +4,7 @@ metadata: name: mg-sharding namespace: demo spec: - version: 4.2.3 + version: 4.4.26 shardTopology: configServer: replicas: 2 diff --git a/docs/examples/mongodb/volume-expansion/mg-standalone.yaml b/docs/examples/mongodb/volume-expansion/mg-standalone.yaml index 013e6197cd..d2de03e594 100644 --- a/docs/examples/mongodb/volume-expansion/mg-standalone.yaml +++ b/docs/examples/mongodb/volume-expansion/mg-standalone.yaml @@ -4,7 +4,7 @@ metadata: name: mg-standalone namespace: demo spec: - version: "4.2.3" + version: "4.4.26" storageType: Durable storage: storageClassName: "standard" diff --git a/docs/guides/elasticsearch/autoscaler/compute/combined/index.md b/docs/guides/elasticsearch/autoscaler/compute/combined/index.md index 0650d5b485..2d9077a4df 100644 --- a/docs/guides/elasticsearch/autoscaler/compute/combined/index.md +++ b/docs/guides/elasticsearch/autoscaler/compute/combined/index.md @@ -47,7 +47,7 @@ Here, we are going to deploy an `Elasticsearch` in combined cluster mode using a ### Deploy Elasticsearch standalone -In this section, we are going to deploy an Elasticsearch combined cluster with ElasticsearchVersion `searchguard-7.9.3`. Then, in the next section, we will set up autoscaling for this database using `ElasticsearchAutoscaler` CRD. Below is the YAML of the `Elasticsearch` CR that we are going to create, +In this section, we are going to deploy an Elasticsearch combined cluster with ElasticsearchVersion `xpack-8.11.1`. Then, in the next section, we will set up autoscaling for this database using `ElasticsearchAutoscaler` CRD. Below is the YAML of the `Elasticsearch` CR that we are going to create, ```yaml apiVersion: kubedb.com/v1alpha2 @@ -57,7 +57,7 @@ metadata: namespace: demo spec: enableSSL: true - version: xpack-8.2.0 + version: xpack-8.2.3 storageType: Durable replicas: 3 storage: @@ -90,11 +90,11 @@ Now, wait until `es-combined` has status `Ready`. i.e, ```bash $ kubectl get elasticsearch -n demo -w NAME VERSION STATUS AGE -es-combined xpack-8.2.0 Provisioning 4s -es-combined xpack-8.2.0 Provisioning 7s +es-combined xpack-8.2.3 Provisioning 4s +es-combined xpack-8.2.3 Provisioning 7s .... .... -es-combined xpack-8.2.0 Ready 60s +es-combined xpack-8.2.3 Ready 60s ``` diff --git a/docs/guides/elasticsearch/autoscaler/compute/combined/yamls/es-combined.yaml b/docs/guides/elasticsearch/autoscaler/compute/combined/yamls/es-combined.yaml index 99175adec9..aa9873b8fe 100644 --- a/docs/guides/elasticsearch/autoscaler/compute/combined/yamls/es-combined.yaml +++ b/docs/guides/elasticsearch/autoscaler/compute/combined/yamls/es-combined.yaml @@ -5,7 +5,7 @@ metadata: namespace: demo spec: enableSSL: true - version: xpack-8.2.0 + version: xpack-8.2.3 storageType: Durable replicas: 3 storage: diff --git a/docs/guides/elasticsearch/autoscaler/compute/topology/index.md b/docs/guides/elasticsearch/autoscaler/compute/topology/index.md index 5c80e4d2ed..0563d3e34c 100644 --- a/docs/guides/elasticsearch/autoscaler/compute/topology/index.md +++ b/docs/guides/elasticsearch/autoscaler/compute/topology/index.md @@ -47,7 +47,7 @@ Here, we are going to deploy an `Elasticsearch` topology cluster using a support #### Deploy Elasticsearch Topology Cluster -In this section, we are going to deploy an Elasticsearch topology with ElasticsearchVersion `opendistro-1.12.0`. Then, in the next section we will set up autoscaling for this database using `ElasticsearchAutoscaler` CRD. Below is the YAML of the `Elasticsearch` CR that we are going to create, +In this section, we are going to deploy an Elasticsearch topology with ElasticsearchVersion `opensearch-2.8.0`. Then, in the next section we will set up autoscaling for this database using `ElasticsearchAutoscaler` CRD. Below is the YAML of the `Elasticsearch` CR that we are going to create, ```yaml apiVersion: kubedb.com/v1alpha2 @@ -57,7 +57,7 @@ metadata: namespace: demo spec: enableSSL: true - version: opendistro-1.12.0 + version: opensearch-2.8.0 storageType: Durable topology: master: @@ -105,8 +105,8 @@ Now, wait until `es-topology` has status `Ready`. i.e, ```bash $ kubectl get elasticsearch -n demo -w NAME VERSION STATUS AGE -es-topology opendistro-1.12.0 Provisioning 113s -es-topology opendistro-1.12.0 Ready 115s +es-topology opensearch-2.8.0 Provisioning 113s +es-topology opensearch-2.8.0 Ready 115s ``` Let's check an ingest node containers resources, diff --git a/docs/guides/elasticsearch/autoscaler/compute/topology/yamls/es-topology.yaml b/docs/guides/elasticsearch/autoscaler/compute/topology/yamls/es-topology.yaml index c5e807e757..86c6e7c6c3 100644 --- a/docs/guides/elasticsearch/autoscaler/compute/topology/yamls/es-topology.yaml +++ b/docs/guides/elasticsearch/autoscaler/compute/topology/yamls/es-topology.yaml @@ -5,7 +5,7 @@ metadata: namespace: demo spec: enableSSL: true - version: opendistro-1.12.0 + version: opensearch-2.8.0 storageType: Durable topology: master: diff --git a/docs/guides/elasticsearch/autoscaler/storage/combined/index.md b/docs/guides/elasticsearch/autoscaler/storage/combined/index.md index e88d783c1f..7903a73a86 100644 --- a/docs/guides/elasticsearch/autoscaler/storage/combined/index.md +++ b/docs/guides/elasticsearch/autoscaler/storage/combined/index.md @@ -60,7 +60,7 @@ Now, we are going to deploy a `Elasticsearch` combined cluster using a supported #### Deploy Elasticsearch Combined Cluster -In this section, we are going to deploy an Elasticsearch combined cluster with version `searchguard-7.9.3`. Then, in the next section we will set up autoscaling for this database using `ElasticsearchAutoscaler` CRD. Below is the YAML of the `Elasticsearch` CR that we are going to create, +In this section, we are going to deploy an Elasticsearch combined cluster with version `xpack-8.11.1`. Then, in the next section we will set up autoscaling for this database using `ElasticsearchAutoscaler` CRD. Below is the YAML of the `Elasticsearch` CR that we are going to create, ```yaml apiVersion: kubedb.com/v1alpha2 @@ -70,7 +70,7 @@ metadata: namespace: demo spec: enableSSL: true - version: searchguard-7.9.3 + version: xpack-8.11.1 storageType: Durable replicas: 1 storage: @@ -95,8 +95,8 @@ Now, wait until `es-combined` has status `Ready`. i.e, ```bash $ kubectl get es -n demo -w NAME VERSION STATUS AGE -es-combined searchguard-7.9.3 Provisioning 5s -es-combined searchguard-7.9.3 Ready 50s +es-combined xpack-8.11.1 Provisioning 5s +es-combined xpack-8.11.1 Ready 50s ``` Let's check volume size from statefulset, and from the persistent volume, diff --git a/docs/guides/elasticsearch/autoscaler/storage/combined/yamls/es-combined.yaml b/docs/guides/elasticsearch/autoscaler/storage/combined/yamls/es-combined.yaml index 8e6e1aa460..e6d69b29ec 100644 --- a/docs/guides/elasticsearch/autoscaler/storage/combined/yamls/es-combined.yaml +++ b/docs/guides/elasticsearch/autoscaler/storage/combined/yamls/es-combined.yaml @@ -5,7 +5,7 @@ metadata: namespace: demo spec: enableSSL: true - version: searchguard-7.9.3 + version: xpack-8.11.1 storageType: Durable replicas: 1 storage: diff --git a/docs/guides/elasticsearch/autoscaler/storage/topology/index.md b/docs/guides/elasticsearch/autoscaler/storage/topology/index.md index f48e1b7d4c..9709c20980 100644 --- a/docs/guides/elasticsearch/autoscaler/storage/topology/index.md +++ b/docs/guides/elasticsearch/autoscaler/storage/topology/index.md @@ -60,7 +60,7 @@ Now, we are going to deploy a `Elasticsearch` topology cluster using a supported #### Deploy Elasticsearch Topology -In this section, we are going to deploy a Elasticsearch topology cluster with version `searchguard-7.9.3`. Then, in the next section we will set up autoscaling for this database using `ElasticsearchAutoscaler` CRD. Below is the YAML of the `Elasticsearch` CR that we are going to create, +In this section, we are going to deploy a Elasticsearch topology cluster with version `xpack-8.11.1`. Then, in the next section we will set up autoscaling for this database using `ElasticsearchAutoscaler` CRD. Below is the YAML of the `Elasticsearch` CR that we are going to create, ```yaml apiVersion: kubedb.com/v1alpha2 @@ -70,7 +70,7 @@ metadata: namespace: demo spec: enableSSL: true - version: searchguard-7.9.3 + version: xpack-8.11.1 storageType: Durable topology: master: @@ -118,8 +118,8 @@ Now, wait until `es-topology` has status `Ready`. i.e, ```bash $ kubectl get elasticsearch -n demo -w NAME VERSION STATUS AGE -es-topology searchguard-7.9.3 Provisioning 12s -es-topology searchguard-7.9.3 Ready 1m50s +es-topology xpack-8.11.1 Provisioning 12s +es-topology xpack-8.11.1 Ready 1m50s ``` Let's check volume size from the data statefulset, and from the persistent volume, diff --git a/docs/guides/elasticsearch/autoscaler/storage/topology/yamls/es-topology.yaml b/docs/guides/elasticsearch/autoscaler/storage/topology/yamls/es-topology.yaml index 256b4708d2..b935e79666 100644 --- a/docs/guides/elasticsearch/autoscaler/storage/topology/yamls/es-topology.yaml +++ b/docs/guides/elasticsearch/autoscaler/storage/topology/yamls/es-topology.yaml @@ -5,7 +5,7 @@ metadata: namespace: demo spec: enableSSL: true - version: searchguard-7.9.3 + version: xpack-8.11.1 storageType: Durable topology: master: diff --git a/docs/guides/elasticsearch/backup/auto-backup/examples/es-demo-2.yaml b/docs/guides/elasticsearch/backup/auto-backup/examples/es-demo-2.yaml index f7a7a0668d..1e8ae8fb1d 100644 --- a/docs/guides/elasticsearch/backup/auto-backup/examples/es-demo-2.yaml +++ b/docs/guides/elasticsearch/backup/auto-backup/examples/es-demo-2.yaml @@ -7,7 +7,7 @@ metadata: stash.appscode.com/backup-blueprint: elasticsearch-backup-template stash.appscode.com/schedule: "*/3 * * * *" spec: - version: xpack-7.9.1-v1 + version: xpack-8.11.1 replicas: 1 storageType: Durable storage: diff --git a/docs/guides/elasticsearch/backup/auto-backup/examples/es-demo-3.yaml b/docs/guides/elasticsearch/backup/auto-backup/examples/es-demo-3.yaml index 4779725642..164d7e9368 100644 --- a/docs/guides/elasticsearch/backup/auto-backup/examples/es-demo-3.yaml +++ b/docs/guides/elasticsearch/backup/auto-backup/examples/es-demo-3.yaml @@ -7,7 +7,7 @@ metadata: stash.appscode.com/backup-blueprint: elasticsearch-backup-template params.stash.appscode.com/args: --ignoreType=settings,template spec: - version: xpack-7.9.1-v1 + version: xpack-8.11.1 replicas: 1 storageType: Durable storage: diff --git a/docs/guides/elasticsearch/backup/auto-backup/examples/es-demo.yaml b/docs/guides/elasticsearch/backup/auto-backup/examples/es-demo.yaml index 61bc84d5b6..034a6a9861 100644 --- a/docs/guides/elasticsearch/backup/auto-backup/examples/es-demo.yaml +++ b/docs/guides/elasticsearch/backup/auto-backup/examples/es-demo.yaml @@ -6,7 +6,7 @@ metadata: annotations: stash.appscode.com/backup-blueprint: elasticsearch-backup-template spec: - version: xpack-7.9.1-v1 + version: xpack-8.11.1 replicas: 1 storageType: Durable storage: diff --git a/docs/guides/elasticsearch/backup/auto-backup/index.md b/docs/guides/elasticsearch/backup/auto-backup/index.md index 44a1b4a1b9..d020104dfd 100644 --- a/docs/guides/elasticsearch/backup/auto-backup/index.md +++ b/docs/guides/elasticsearch/backup/auto-backup/index.md @@ -156,7 +156,7 @@ metadata: annotations: stash.appscode.com/backup-blueprint: elasticsearch-backup-template spec: - version: xpack-7.9.1-v1 + version: xpack-8.11.1 replicas: 1 storageType: Durable storage: @@ -334,7 +334,7 @@ metadata: stash.appscode.com/backup-blueprint: elasticsearch-backup-template stash.appscode.com/schedule: "*/3 * * * *" spec: - version: xpack-7.9.1-v1 + version: xpack-8.11.1 replicas: 1 storageType: Durable storage: @@ -513,7 +513,7 @@ metadata: stash.appscode.com/backup-blueprint: elasticsearch-backup-template params.stash.appscode.com/args: --ignoreType=settings,template spec: - version: xpack-7.9.1-v1 + version: xpack-8.11.1 replicas: 1 storageType: Durable storage: diff --git a/docs/guides/elasticsearch/backup/customization/examples/elasticsearch.yaml b/docs/guides/elasticsearch/backup/customization/examples/elasticsearch.yaml index b37bfe04ce..d0074e8664 100644 --- a/docs/guides/elasticsearch/backup/customization/examples/elasticsearch.yaml +++ b/docs/guides/elasticsearch/backup/customization/examples/elasticsearch.yaml @@ -4,7 +4,7 @@ metadata: name: sample-elasticsearch namespace: demo spec: - version: searchguard-7.9.3 + version: xpack-8.11.1 replicas: 1 storageType: Durable storage: diff --git a/docs/guides/elasticsearch/backup/kubedb/examples/elasticsearch/init_sample.yaml b/docs/guides/elasticsearch/backup/kubedb/examples/elasticsearch/init_sample.yaml index 6bb2037a94..a35d96663b 100644 --- a/docs/guides/elasticsearch/backup/kubedb/examples/elasticsearch/init_sample.yaml +++ b/docs/guides/elasticsearch/backup/kubedb/examples/elasticsearch/init_sample.yaml @@ -4,7 +4,7 @@ metadata: name: init-sample namespace: restored spec: - version: opendistro-1.11.0 + version: opensearch-2.8.0 storageType: Durable init: waitForInitialRestore: true diff --git a/docs/guides/elasticsearch/backup/kubedb/examples/elasticsearch/sample_es.yaml b/docs/guides/elasticsearch/backup/kubedb/examples/elasticsearch/sample_es.yaml index 253bafcec9..792ea029a5 100644 --- a/docs/guides/elasticsearch/backup/kubedb/examples/elasticsearch/sample_es.yaml +++ b/docs/guides/elasticsearch/backup/kubedb/examples/elasticsearch/sample_es.yaml @@ -4,7 +4,7 @@ metadata: name: sample-es namespace: demo spec: - version: xpack-7.9.1-v1 + version: xpack-8.11.1 storageType: Durable topology: master: diff --git a/docs/guides/elasticsearch/backup/kubedb/index.md b/docs/guides/elasticsearch/backup/kubedb/index.md index d710a3dffc..4c204a47de 100644 --- a/docs/guides/elasticsearch/backup/kubedb/index.md +++ b/docs/guides/elasticsearch/backup/kubedb/index.md @@ -54,7 +54,7 @@ metadata: name: sample-es namespace: demo spec: - version: xpack-7.9.1-v1 + version: xpack-8.11.1 storageType: Durable topology: master: @@ -101,8 +101,8 @@ KubeDB will create the necessary resources to deploy the Elasticsearch database ```console ❯ kubectl get elasticsearch -n demo -w NAME VERSION STATUS AGE -sample-es xpack-7.9.1-v1 Provisioning 89s -sample-es xpack-7.9.1-v1 Ready 5m26s +sample-es xpack-8.11.1 Provisioning 89s +sample-es xpack-8.11.1 Ready 5m26s ``` The database is in `Ready` state. It means the database is ready to accept connections. @@ -834,7 +834,7 @@ metadata: name: init-sample namespace: restored spec: - version: opendistro-1.11.0 + version: opensearch-2.8.0 storageType: Durable init: waitForInitialRestore: true diff --git a/docs/guides/elasticsearch/cli/cli.md b/docs/guides/elasticsearch/cli/cli.md index c4c2aad748..4d34a05fb1 100644 --- a/docs/guides/elasticsearch/cli/cli.md +++ b/docs/guides/elasticsearch/cli/cli.md @@ -84,7 +84,7 @@ spec: storageClassName: standard storageType: Durable terminationPolicy: Halt - version: searchguard-7.9.3 + version: xpack-8.11.1 status: observedGeneration: 3$4212299729528774793 phase: Running diff --git a/docs/guides/elasticsearch/clustering/combined-cluster/index.md b/docs/guides/elasticsearch/clustering/combined-cluster/index.md index c568c848d5..8081071a3d 100644 --- a/docs/guides/elasticsearch/clustering/combined-cluster/index.md +++ b/docs/guides/elasticsearch/clustering/combined-cluster/index.md @@ -37,7 +37,7 @@ demo Active 9s ## Create Standalone Elasticsearch Cluster -Here, we are going to create a standalone (ie. `replicas: 1`) Elasticsearch cluster. We will use the Elasticsearch image provided by the Opendistro (`opendistro-1.12.0`) for this demo. To learn more about Elasticsearch CR, visit [here](/docs/guides/elasticsearch/concepts/elasticsearch/index.md). +Here, we are going to create a standalone (ie. `replicas: 1`) Elasticsearch cluster. We will use the Elasticsearch image provided by the Opendistro (`opensearch-2.8.0`) for this demo. To learn more about Elasticsearch CR, visit [here](/docs/guides/elasticsearch/concepts/elasticsearch/index.md). ```yaml apiVersion: kubedb.com/v1alpha2 @@ -46,7 +46,7 @@ metadata: name: es-standalone namespace: demo spec: - version: opendistro-1.12.0 + version: opensearch-2.8.0 enableSSL: true replicas: 1 storageType: Durable @@ -72,11 +72,11 @@ Watch the bootstrap progress: ```bash $ kubectl get elasticsearch -n demo -w NAME VERSION STATUS AGE -es-standalone opendistro-1.12.0 Provisioning 1m32s -es-standalone opendistro-1.12.0 Provisioning 2m17s -es-standalone opendistro-1.12.0 Provisioning 2m17s -es-standalone opendistro-1.12.0 Provisioning 2m20s -es-standalone opendistro-1.12.0 Ready 2m20s +es-standalone opensearch-2.8.0 Provisioning 1m32s +es-standalone opensearch-2.8.0 Provisioning 2m17s +es-standalone opensearch-2.8.0 Provisioning 2m17s +es-standalone opensearch-2.8.0 Provisioning 2m20s +es-standalone opensearch-2.8.0 Ready 2m20s ``` Hence the cluster is ready to use. @@ -155,7 +155,7 @@ $ curl -XGET -k -u 'admin:V,YY1.qXxoAch9)B' "https://localhost:9200/_cluster/hea ## Create Multi-Node Combined Elasticsearch Cluster -Here, we are going to create a multi-node (say `replicas: 3`) Elasticsearch cluster. We will use the Elasticsearch image provided by the Opendistro (`opendistro-1.12.0`) for this demo. To learn more about Elasticsearch CR, visit [here](/docs/guides/elasticsearch/concepts/elasticsearch/index.md). +Here, we are going to create a multi-node (say `replicas: 3`) Elasticsearch cluster. We will use the Elasticsearch image provided by the Opendistro (`opensearch-2.8.0`) for this demo. To learn more about Elasticsearch CR, visit [here](/docs/guides/elasticsearch/concepts/elasticsearch/index.md). ```yaml apiVersion: kubedb.com/v1alpha2 @@ -164,7 +164,7 @@ metadata: name: es-multinode namespace: demo spec: - version: opendistro-1.12.0 + version: opensearch-2.8.0 enableSSL: true replicas: 3 storageType: Durable @@ -190,11 +190,11 @@ Watch the bootstrap progress: ```bash $ kubectl get elasticsearch -n demo -w NAME VERSION STATUS AGE -es-multinode opendistro-1.12.0 Provisioning 18s -es-multinode opendistro-1.12.0 Provisioning 78s -es-multinode opendistro-1.12.0 Provisioning 78s -es-multinode opendistro-1.12.0 Provisioning 81s -es-multinode opendistro-1.12.0 Ready 81s +es-multinode opensearch-2.8.0 Provisioning 18s +es-multinode opensearch-2.8.0 Provisioning 78s +es-multinode opensearch-2.8.0 Provisioning 78s +es-multinode opensearch-2.8.0 Provisioning 81s +es-multinode opensearch-2.8.0 Ready 81s ``` Hence the cluster is ready to use. diff --git a/docs/guides/elasticsearch/clustering/combined-cluster/yamls/es-multinode.yaml b/docs/guides/elasticsearch/clustering/combined-cluster/yamls/es-multinode.yaml index 9192403b8e..ef6da275d4 100644 --- a/docs/guides/elasticsearch/clustering/combined-cluster/yamls/es-multinode.yaml +++ b/docs/guides/elasticsearch/clustering/combined-cluster/yamls/es-multinode.yaml @@ -4,7 +4,7 @@ metadata: name: es-multinode namespace: demo spec: - version: opendistro-1.12.0 + version: opensearch-2.8.0 enableSSL: true replicas: 3 storageType: Durable diff --git a/docs/guides/elasticsearch/clustering/combined-cluster/yamls/es-standalone.yaml b/docs/guides/elasticsearch/clustering/combined-cluster/yamls/es-standalone.yaml index ccea46ca8c..d7bf099dd3 100644 --- a/docs/guides/elasticsearch/clustering/combined-cluster/yamls/es-standalone.yaml +++ b/docs/guides/elasticsearch/clustering/combined-cluster/yamls/es-standalone.yaml @@ -4,7 +4,7 @@ metadata: name: es-standalone namespace: demo spec: - version: opendistro-1.12.0 + version: opensearch-2.8.0 enableSSL: true replicas: 1 storageType: Durable diff --git a/docs/guides/elasticsearch/clustering/topology-cluster/hot-warm-cold-cluster/index.md b/docs/guides/elasticsearch/clustering/topology-cluster/hot-warm-cold-cluster/index.md index f0d98edba5..16ccbb3d89 100644 --- a/docs/guides/elasticsearch/clustering/topology-cluster/hot-warm-cold-cluster/index.md +++ b/docs/guides/elasticsearch/clustering/topology-cluster/hot-warm-cold-cluster/index.md @@ -51,7 +51,7 @@ Here, we use `linode-block-storage` as StorageClass in this demo. ## Create Elasticsearch Hot-Warm-Cold Cluster -We are going to create a Elasticsearch Hot-Warm-Cold cluster in topology mode. Our cluster will be consist of 2 master nodes, 2 ingest nodes, 1 data content node, 3 data hot nodes, 2 data warm node, and 2 data cold nodes. Here, we are using Elasticsearch version (`xpack-7.16.2`) of ElasticStack distribution for this demo. To learn more about the Elasticsearch CR, visit [here](/docs/guides/elasticsearch/concepts/elasticsearch/index.md). +We are going to create a Elasticsearch Hot-Warm-Cold cluster in topology mode. Our cluster will be consist of 2 master nodes, 2 ingest nodes, 1 data content node, 3 data hot nodes, 2 data warm node, and 2 data cold nodes. Here, we are using Elasticsearch version (`xpack-8.11.1`) of ElasticStack distribution for this demo. To learn more about the Elasticsearch CR, visit [here](/docs/guides/elasticsearch/concepts/elasticsearch/index.md). ```yaml apiVersion: kubedb.com/v1alpha2 @@ -61,7 +61,7 @@ metadata: namespace: demo spec: enableSSL: true - version: xpack-7.16.2 + version: xpack-8.11.1 topology: master: replicas: 2 @@ -110,7 +110,7 @@ spec: Here, -- `spec.version` - is the name of the ElasticsearchVersion CR. Here, we are using Elasticsearch version `xpack-7.16.2` of ElasticStack distribution. +- `spec.version` - is the name of the ElasticsearchVersion CR. Here, we are using Elasticsearch version `xpack-8.11.1` of ElasticStack distribution. - `spec.enableSSL` - specifies whether the HTTP layer is secured with certificates or not. - `spec.storageType` - specifies the type of storage that will be used for Elasticsearch database. It can be `Durable` or `Ephemeral`. The default value of this field is `Durable`. If `Ephemeral` is used then KubeDB will create the Elasticsearch database using `EmptyDir` volume. In this case, you don't have to specify `spec.storage` field. This is useful for testing purposes. - `spec.topology` - specifies the node-specific properties for the Elasticsearch cluster. @@ -146,7 +146,7 @@ KubeDB will create the necessary resources to deploy the Elasticsearch cluster a ```bash $ watch kubectl get elasticsearch -n demo NAME VERSION STATUS AGE -es-cluster xpack-7.16.2 Ready 2m48s +es-cluster xpack-8.11.1 Ready 2m48s ``` Here, Elasticsearch is in `Ready` state. It means the database is ready to accept connections. @@ -336,7 +336,7 @@ Spec: Storage: 1Gi Storage Class Name: linode-block-storage Suffix: master - Version: xpack-7.16.2 + Version: xpack-8.11.1 Status: Conditions: Last Transition Time: 2022-03-14T06:33:20Z diff --git a/docs/guides/elasticsearch/clustering/topology-cluster/hot-warm-cold-cluster/yamls/es-cluster.yaml b/docs/guides/elasticsearch/clustering/topology-cluster/hot-warm-cold-cluster/yamls/es-cluster.yaml index 37d5845541..0df7555c80 100644 --- a/docs/guides/elasticsearch/clustering/topology-cluster/hot-warm-cold-cluster/yamls/es-cluster.yaml +++ b/docs/guides/elasticsearch/clustering/topology-cluster/hot-warm-cold-cluster/yamls/es-cluster.yaml @@ -5,7 +5,7 @@ metadata: namespace: demo spec: enableSSL: true - version: xpack-7.16.2 + version: xpack-8.11.1 topology: master: replicas: 2 diff --git a/docs/guides/elasticsearch/clustering/topology-cluster/simple-dedicated-cluster/index.md b/docs/guides/elasticsearch/clustering/topology-cluster/simple-dedicated-cluster/index.md index b9c5303296..dfedd590d5 100644 --- a/docs/guides/elasticsearch/clustering/topology-cluster/simple-dedicated-cluster/index.md +++ b/docs/guides/elasticsearch/clustering/topology-cluster/simple-dedicated-cluster/index.md @@ -47,7 +47,7 @@ Here, we have `standard` StorageClass in our cluster from [Local Path Provisione ## Create Elasticsearch Simple Dedicated Cluster -We are going to create a Elasticsearch Simple Dedicated Cluster in topology mode. Our cluster will be consist of 2 master nodes, 3 data nodes, 2 ingest nodes. Here, we are using Elasticsearch version ( `searchguard-7.14.2` ) of SearchGuard distribution for this demo. To learn more about the Elasticsearch CR, visit [here](/docs/guides/elasticsearch/concepts/elasticsearch/index.md). +We are going to create a Elasticsearch Simple Dedicated Cluster in topology mode. Our cluster will be consist of 2 master nodes, 3 data nodes, 2 ingest nodes. Here, we are using Elasticsearch version ( `xpack-8.11.1` ) of SearchGuard distribution for this demo. To learn more about the Elasticsearch CR, visit [here](/docs/guides/elasticsearch/concepts/elasticsearch/index.md). ```yaml apiVersion: kubedb.com/v1alpha2 @@ -57,7 +57,7 @@ metadata: namespace: demo spec: enableSSL: true - version: searchguard-7.14.2 + version: xpack-8.11.1 storageType: Durable topology: master: @@ -91,7 +91,7 @@ spec: Here, -- `spec.version` - is the name of the ElasticsearchVersion CR. Here, we are using Elasticsearch version `searchguard-7.14.2` of SearchGuard distribution. +- `spec.version` - is the name of the ElasticsearchVersion CR. Here, we are using Elasticsearch version `xpack-8.11.1` of SearchGuard distribution. - `spec.enableSSL` - specifies whether the HTTP layer is secured with certificates or not. - `spec.storageType` - specifies the type of storage that will be used for Elasticsearch database. It can be `Durable` or `Ephemeral`. The default value of this field is `Durable`. If `Ephemeral` is used then KubeDB will create the Elasticsearch database using `EmptyDir` volume. In this case, you don't have to specify `spec.storage` field. This is useful for testing purposes. - `spec.topology` - specifies the node-specific properties for the Elasticsearch cluster. @@ -116,7 +116,7 @@ KubeDB will create the necessary resources to deploy the Elasticsearch cluster a ```bash $ watch kubectl get elasticsearch -n demo NAME VERSION STATUS AGE -es-cluster searchguard-7.14.2 Ready 3m32s +es-cluster xpack-8.11.1 Ready 3m32s ``` Here, Elasticsearch is in `Ready` state. It means the database is ready to accept connections. @@ -270,7 +270,7 @@ Spec: Storage: 1Gi Storage Class Name: standard Suffix: master - Version: searchguard-7.14.2 + Version: xpack-8.11.1 Status: Conditions: Last Transition Time: 2022-04-07T09:48:51Z diff --git a/docs/guides/elasticsearch/clustering/topology-cluster/simple-dedicated-cluster/yamls/es-cluster.yaml b/docs/guides/elasticsearch/clustering/topology-cluster/simple-dedicated-cluster/yamls/es-cluster.yaml index 1df6e0eacc..602f053d5c 100644 --- a/docs/guides/elasticsearch/clustering/topology-cluster/simple-dedicated-cluster/yamls/es-cluster.yaml +++ b/docs/guides/elasticsearch/clustering/topology-cluster/simple-dedicated-cluster/yamls/es-cluster.yaml @@ -5,7 +5,7 @@ metadata: namespace: demo spec: enableSSL: true - version: searchguard-7.14.2 + version: xpack-8.11.1 storageType: Durable topology: master: diff --git a/docs/guides/elasticsearch/concepts/appbinding/index.md b/docs/guides/elasticsearch/concepts/appbinding/index.md index c6dfaea4c4..f5573cbc87 100644 --- a/docs/guides/elasticsearch/concepts/appbinding/index.md +++ b/docs/guides/elasticsearch/concepts/appbinding/index.md @@ -34,7 +34,7 @@ kind: AppBinding metadata: annotations: kubectl.kubernetes.io/last-applied-configuration: | - {"apiVersion":"kubedb.com/v1alpha2","kind":"Elasticsearch","metadata":{"annotations":{},"name":"es-quickstart","namespace":"demo"},"spec":{"enableSSL":true,"replicas":3,"storage":{"accessModes":["ReadWriteOnce"],"resources":{"requests":{"storage":"1Gi"}},"storageClassName":"standard"},"storageType":"Durable","terminationPolicy":"Delete","version":"xpack-8.2.0"}} + {"apiVersion":"kubedb.com/v1alpha2","kind":"Elasticsearch","metadata":{"annotations":{},"name":"es-quickstart","namespace":"demo"},"spec":{"enableSSL":true,"replicas":3,"storage":{"accessModes":["ReadWriteOnce"],"resources":{"requests":{"storage":"1Gi"}},"storageClassName":"standard"},"storageType":"Durable","terminationPolicy":"Delete","version":"xpack-8.2.3"}} creationTimestamp: "2022-12-29T05:03:33Z" generation: 1 labels: diff --git a/docs/guides/elasticsearch/concepts/catalog/index.md b/docs/guides/elasticsearch/concepts/catalog/index.md index bea6a30b88..3d68655a56 100644 --- a/docs/guides/elasticsearch/concepts/catalog/index.md +++ b/docs/guides/elasticsearch/concepts/catalog/index.md @@ -41,7 +41,7 @@ metadata: app.kubernetes.io/name: kubedb-catalog app.kubernetes.io/version: v2022.12.28 helm.sh/chart: kubedb-catalog-v2022.12.28 - name: xpack-7.14.0 + name: xpack-8.11.1 resourceVersion: "1844" uid: db8b5122-bce8-4e80-b608-e314954f2980 spec: @@ -90,7 +90,7 @@ We follow this convention for naming ElasticsearchVersion CRD: - Name format: `{Security Plugin Name}-{Application Version}-{Modification Tag}` -- Samples: `searchguard-7.9.3`, `xpack-7.9.1-v1`, `opendistro-1.12.0`, etc. +- Samples: `xpack-8.11.1`, `xpack-8.11.1`, `opensearch-2.8.0`, etc. We use the original Elasticsearch docker image provided by the distributors. Then we bundle the image with the necessary sidecar and init container images which facilitate features like sysctl kernel settings, custom configuration, monitoring matrices, etc. An image with a higher modification tag will have more features and fixes than an image with a lower modification tag. Hence, it is recommended to use ElasticsearchVersion CRD with the highest modification tag to take advantage of the latest features. diff --git a/docs/guides/elasticsearch/concepts/elasticsearch-ops-request/index.md b/docs/guides/elasticsearch/concepts/elasticsearch-ops-request/index.md index 513f9e4547..565c97532e 100644 --- a/docs/guides/elasticsearch/concepts/elasticsearch-ops-request/index.md +++ b/docs/guides/elasticsearch/concepts/elasticsearch-ops-request/index.md @@ -35,7 +35,7 @@ spec: databaseRef: name: es updateVersion: - targetVersion: searchguard-7.5.2-v1 + targetVersion: xpack-8.11.1 status: conditions: - lastTransitionTime: "2020-08-25T18:22:38Z" @@ -81,7 +81,7 @@ It specifies the desired version information required for the Elasticsearch vers > KubeDB does not support downgrade for Elasticsearch. **Samples:** -Let's assume we have and Elasticsearch cluster of version `xpack-8.2.0`. The Elasticsearch custom resource is named `es-quickstart` and it's provisioned in demo namespace. Now, you want to update your Elasticsearch cluster to `xpack-8.5.2`. Apply this YAML to update to your desired version. +Let's assume we have and Elasticsearch cluster of version `xpack-8.2.3`. The Elasticsearch custom resource is named `es-quickstart` and it's provisioned in demo namespace. Now, you want to update your Elasticsearch cluster to `xpack-8.5.2`. Apply this YAML to update to your desired version. ```yaml apiVersion: ops.kubedb.com/v1alpha1 kind: ElasticsearchOpsRequest diff --git a/docs/guides/elasticsearch/concepts/elasticsearch/index.md b/docs/guides/elasticsearch/concepts/elasticsearch/index.md index a2b538299a..24437f1686 100644 --- a/docs/guides/elasticsearch/concepts/elasticsearch/index.md +++ b/docs/guides/elasticsearch/concepts/elasticsearch/index.md @@ -154,7 +154,7 @@ spec: timeoutSeconds: 10 failureThreshold: 2 disableWriteCheck: false - version: searchguard-7.9.3 + version: xpack-8.11.1 ``` ### spec.autoOps AutoOps is an optional field to control the generation of versionUpdate & TLS-related recommendations. @@ -164,11 +164,11 @@ AutoOps is an optional field to control the generation of versionUpdate & TLS-re - Name format: `{Security Plugin Name}-{Application Version}-{Modification Tag}` -- Samples: `xpack-8.2.0`, `xpack-7.9.1-v1`, `opensearch-1.3.0`, etc. +- Samples: `xpack-8.2.3`, `xpack-8.11.1`, `opensearch-1.3.0`, etc. ```yaml spec: - version: searchguard-7.9.3 + version: xpack-8.11.1 ``` ### spec.kernelSettings diff --git a/docs/guides/elasticsearch/configuration/combined-cluster/index.md b/docs/guides/elasticsearch/configuration/combined-cluster/index.md index ede0fc93d1..aad3ebea11 100644 --- a/docs/guides/elasticsearch/configuration/combined-cluster/index.md +++ b/docs/guides/elasticsearch/configuration/combined-cluster/index.md @@ -101,7 +101,7 @@ metadata: name: es-multinode namespace: demo spec: - version: xpack-7.9.1-v1 + version: xpack-8.11.1 enableSSL: true replicas: 3 configSecret: @@ -129,9 +129,9 @@ Now, wait for the Elasticsearch to become ready: ```bash $ kubectl get es -n demo -w NAME VERSION STATUS AGE -es-multinode xpack-7.9.1-v1 Provisioning 18s -es-multinode xpack-7.9.1-v1 Provisioning 2m5s -es-multinode xpack-7.9.1-v1 Ready 2m5s +es-multinode xpack-8.11.1 Provisioning 18s +es-multinode xpack-8.11.1 Provisioning 2m5s +es-multinode xpack-8.11.1 Ready 2m5s ``` ## Verify Configuration diff --git a/docs/guides/elasticsearch/configuration/combined-cluster/yamls/es-combined.yaml b/docs/guides/elasticsearch/configuration/combined-cluster/yamls/es-combined.yaml index 7ce98e4f85..b0d4213cd8 100644 --- a/docs/guides/elasticsearch/configuration/combined-cluster/yamls/es-combined.yaml +++ b/docs/guides/elasticsearch/configuration/combined-cluster/yamls/es-combined.yaml @@ -4,7 +4,7 @@ metadata: name: es-multinode namespace: demo spec: - version: xpack-7.9.1-v1 + version: xpack-8.11.1 enableSSL: true replicas: 3 configSecret: diff --git a/docs/guides/elasticsearch/configuration/jvm-options/index.md b/docs/guides/elasticsearch/configuration/jvm-options/index.md index 0ac5df8147..e9cd8759f3 100644 --- a/docs/guides/elasticsearch/configuration/jvm-options/index.md +++ b/docs/guides/elasticsearch/configuration/jvm-options/index.md @@ -85,7 +85,7 @@ spec: configSecret: name: es-custom-config enableSSL: false - version: opendistro-1.12.0 + version: opensearch-2.8.0 storageType: Durable terminationPolicy: WipeOut topology: @@ -133,7 +133,7 @@ Wait for the Elasticsearch to become ready: ```bash $ kubectl get elasticsearch -n demo -w NAME VERSION STATUS AGE -es-test opendistro-1.12.0 Provisioning 12s -es-test opendistro-1.12.0 Provisioning 2m2s -es-test opendistro-1.12.0 Ready 2m2s +es-test opensearch-2.8.0 Provisioning 12s +es-test opensearch-2.8.0 Provisioning 2m2s +es-test opensearch-2.8.0 Ready 2m2s ``` diff --git a/docs/guides/elasticsearch/configuration/jvm-options/yamls/elasticsearch.yaml b/docs/guides/elasticsearch/configuration/jvm-options/yamls/elasticsearch.yaml index aeda4ce8cf..ef78df2eaf 100644 --- a/docs/guides/elasticsearch/configuration/jvm-options/yamls/elasticsearch.yaml +++ b/docs/guides/elasticsearch/configuration/jvm-options/yamls/elasticsearch.yaml @@ -7,7 +7,7 @@ spec: configSecret: name: es-custom-config enableSSL: false - version: opendistro-1.12.0 + version: opensearch-2.8.0 storageType: Durable terminationPolicy: WipeOut topology: diff --git a/docs/guides/elasticsearch/configuration/overview/index.md b/docs/guides/elasticsearch/configuration/overview/index.md index 4be04a4625..1ed741f289 100644 --- a/docs/guides/elasticsearch/configuration/overview/index.md +++ b/docs/guides/elasticsearch/configuration/overview/index.md @@ -61,7 +61,7 @@ metadata: name: es-custom-config namespace: demo spec: - version: searchguard-7.9.3 + version: xpack-8.11.1 configSecret: name: es-custom-config ``` diff --git a/docs/guides/elasticsearch/configuration/topology-cluster/index.md b/docs/guides/elasticsearch/configuration/topology-cluster/index.md index 72481c5503..cdf47cc418 100644 --- a/docs/guides/elasticsearch/configuration/topology-cluster/index.md +++ b/docs/guides/elasticsearch/configuration/topology-cluster/index.md @@ -140,7 +140,7 @@ metadata: namespace: demo spec: enableSSL: true - version: xpack-7.9.1-v1 + version: xpack-8.11.1 configSecret: name: es-custom-config # mentioned here! storageType: Durable @@ -187,9 +187,9 @@ Now, wait for the Elasticsearch to become ready: ```bash $ kubectl get elasticsearch -n demo -w NAME VERSION STATUS AGE -es-topology xpack-7.9.1-v1 Provisioning 12s -es-topology xpack-7.9.1-v1 Provisioning 2m2s -es-topology xpack-7.9.1-v1 Ready 2m2s +es-topology xpack-8.11.1 Provisioning 12s +es-topology xpack-8.11.1 Provisioning 2m2s +es-topology xpack-8.11.1 Ready 2m2s ``` ## Verify Configuration diff --git a/docs/guides/elasticsearch/configuration/topology-cluster/yamls/es-topology.yaml b/docs/guides/elasticsearch/configuration/topology-cluster/yamls/es-topology.yaml index 0bfbf3a465..61ddb8e43e 100644 --- a/docs/guides/elasticsearch/configuration/topology-cluster/yamls/es-topology.yaml +++ b/docs/guides/elasticsearch/configuration/topology-cluster/yamls/es-topology.yaml @@ -5,7 +5,7 @@ metadata: namespace: demo spec: enableSSL: true - version: xpack-7.9.1-v1 + version: xpack-8.11.1 configSecret: name: es-custom-config storageType: Durable diff --git a/docs/guides/elasticsearch/custom-rbac/using-custom-rbac.md b/docs/guides/elasticsearch/custom-rbac/using-custom-rbac.md index 39282d994f..22d5d05792 100644 --- a/docs/guides/elasticsearch/custom-rbac/using-custom-rbac.md +++ b/docs/guides/elasticsearch/custom-rbac/using-custom-rbac.md @@ -142,7 +142,7 @@ metadata: name: quick-elasticsearch namespace: demo spec: - version: searchguard-7.9.3 + version: xpack-8.11.1 podTemplate: spec: serviceAccountName: my-custom-serviceaccount @@ -193,7 +193,7 @@ metadata: name: minute-elasticsearch namespace: demo spec: - version: searchguard-7.9.3 + version: xpack-8.11.1 storageType: Durable podTemplate: spec: diff --git a/docs/guides/elasticsearch/elasticsearch-dashboard/kibana/index.md b/docs/guides/elasticsearch/elasticsearch-dashboard/kibana/index.md index ef10ed5bf7..ebed2c9bf5 100644 --- a/docs/guides/elasticsearch/elasticsearch-dashboard/kibana/index.md +++ b/docs/guides/elasticsearch/elasticsearch-dashboard/kibana/index.md @@ -47,7 +47,7 @@ Here, we have `standard` StorageClass in our cluster from [Local Path Provisione ## Create an Elasticsearch Cluster -We are going to create a Elasticsearch Simple Dedicated Cluster in topology mode. Our cluster will be consist of 2 master nodes, 3 data nodes, 2 ingest nodes. Here, we are using Elasticsearch version (`xpack-8.2.0`) of Elasticsearch distribution for this demo. To learn more about the Elasticsearch CR, visit [here](/docs/guides/elasticsearch/concepts/elasticsearch/index.md). +We are going to create a Elasticsearch Simple Dedicated Cluster in topology mode. Our cluster will be consist of 2 master nodes, 3 data nodes, 2 ingest nodes. Here, we are using Elasticsearch version (`xpack-8.2.3`) of Elasticsearch distribution for this demo. To learn more about the Elasticsearch CR, visit [here](/docs/guides/elasticsearch/concepts/elasticsearch/index.md). ```yaml apiVersion: kubedb.com/v1alpha2 @@ -57,7 +57,7 @@ metadata: namespace: demo spec: enableSSL: true - version: xpack-8.2.0 + version: xpack-8.2.3 storageType: Durable topology: master: @@ -91,7 +91,7 @@ spec: Here, -- `spec.version` - is the name of the ElasticsearchVersion CR. Here, we are using Elasticsearch version `xpack-8.2.0` of Elasticsearch distribution. +- `spec.version` - is the name of the ElasticsearchVersion CR. Here, we are using Elasticsearch version `xpack-8.2.3` of Elasticsearch distribution. - `spec.enableSSL` - specifies whether the HTTP layer is secured with certificates or not. - `spec.storageType` - specifies the type of storage that will be used for Elasticsearch database. It can be `Durable` or `Ephemeral`. The default value of this field is `Durable`. If `Ephemeral` is used then KubeDB will create the Elasticsearch database using `EmptyDir` volume. In this case, you don't have to specify `spec.storage` field. This is useful for testing purposes. - `spec.topology` - specifies the node-specific properties for the Elasticsearch cluster. @@ -116,7 +116,7 @@ KubeDB will create the necessary resources to deploy the Elasticsearch cluster a ```bash $ watch kubectl get elasticsearch -n demo NAME VERSION STATUS AGE -es-cluster xpack-8.2.0 Ready 4m32s +es-cluster xpack-8.2.3 Ready 4m32s ``` Here, Elasticsearch is in `Ready` state. It means the database is ready to accept connections. @@ -296,7 +296,7 @@ Spec: Storage: 1Gi Storage Class Name: standard Suffix: master - Version: xpack-8.2.0 + Version: xpack-8.2.3 Status: Conditions: Last Transition Time: 2022-06-08T11:03:43Z diff --git a/docs/guides/elasticsearch/elasticsearch-dashboard/kibana/yamls/es-cluster.yaml b/docs/guides/elasticsearch/elasticsearch-dashboard/kibana/yamls/es-cluster.yaml index 1df6d65e43..4b849aef86 100644 --- a/docs/guides/elasticsearch/elasticsearch-dashboard/kibana/yamls/es-cluster.yaml +++ b/docs/guides/elasticsearch/elasticsearch-dashboard/kibana/yamls/es-cluster.yaml @@ -5,7 +5,7 @@ metadata: namespace: demo spec: enableSSL: true - version: xpack-8.2.0 + version: xpack-8.2.3 storageType: Durable topology: master: diff --git a/docs/guides/elasticsearch/elasticsearch-dashboard/opensearch-dashboards/index.md b/docs/guides/elasticsearch/elasticsearch-dashboard/opensearch-dashboards/index.md index 3f2ee1f196..9a06173708 100644 --- a/docs/guides/elasticsearch/elasticsearch-dashboard/opensearch-dashboards/index.md +++ b/docs/guides/elasticsearch/elasticsearch-dashboard/opensearch-dashboards/index.md @@ -49,7 +49,7 @@ Here, we have `standard` StorageClass in our cluster from [Local Path Provisione ## Create an OpenSearch Cluster -We are going to create a OpenSearch Cluster in topology mode. Our cluster will be consist of 2 master nodes, 3 data nodes, 2 ingest nodes. Here, we are using Elasticsearch version ( `opensearch-1.3.2` ) of OpenSearch distribution for this demo. To learn more about the Elasticsearch CR, visit [here](/docs/guides/elasticsearch/concepts/elasticsearch/index.md). +We are going to create a OpenSearch Cluster in topology mode. Our cluster will be consist of 2 master nodes, 3 data nodes, 2 ingest nodes. Here, we are using Elasticsearch version ( `opensearch-2.8.0` ) of OpenSearch distribution for this demo. To learn more about the Elasticsearch CR, visit [here](/docs/guides/elasticsearch/concepts/elasticsearch/index.md). ```yaml apiVersion: kubedb.com/v1alpha2 @@ -59,7 +59,7 @@ metadata: namespace: demo spec: enableSSL: true - version: opensearch-1.3.2 + version: opensearch-2.8.0 storageType: Durable topology: master: @@ -93,7 +93,7 @@ spec: Here, -- `spec.version` - is the name of the ElasticsearchVersion CR. Here, we are using Elasticsearch version `opensearch-1.3.2` of OpenSearch distribution. +- `spec.version` - is the name of the ElasticsearchVersion CR. Here, we are using Elasticsearch version `opensearch-2.8.0` of OpenSearch distribution. - `spec.enableSSL` - specifies whether the HTTP layer is secured with certificates or not. - `spec.storageType` - specifies the type of storage that will be used for OpenSearch database. It can be `Durable` or `Ephemeral`. The default value of this field is `Durable`. If `Ephemeral` is used then KubeDB will create the OpenSearch database using `EmptyDir` volume. In this case, you don't have to specify `spec.storage` field. This is useful for testing purposes. - `spec.topology` - specifies the node-specific properties for the OpenSearch cluster. @@ -118,7 +118,7 @@ KubeDB will create the necessary resources to deploy the OpenSearch cluster acco ```bash $ watch kubectl get elasticsearch -n demo NAME VERSION STATUS AGE -os-cluster opensearch-1.3.2 Ready 3m25s +os-cluster opensearch-2.8.0 Ready 3m25s ``` Here, OpenSearch is in `Ready` state. It means the database is ready to accept connections. @@ -295,7 +295,7 @@ Spec: Storage: 1Gi Storage Class Name: standard Suffix: master - Version: opensearch-1.3.2 + Version: opensearch-2.8.0 Status: Conditions: Last Transition Time: 2022-06-08T06:01:54Z diff --git a/docs/guides/elasticsearch/elasticsearch-dashboard/opensearch-dashboards/yamls/os-cluster.yaml b/docs/guides/elasticsearch/elasticsearch-dashboard/opensearch-dashboards/yamls/os-cluster.yaml index f2ddbec7b7..c16bcdd228 100644 --- a/docs/guides/elasticsearch/elasticsearch-dashboard/opensearch-dashboards/yamls/os-cluster.yaml +++ b/docs/guides/elasticsearch/elasticsearch-dashboard/opensearch-dashboards/yamls/os-cluster.yaml @@ -5,7 +5,7 @@ metadata: namespace: demo spec: enableSSL: true - version: opensearch-1.3.2 + version: opensearch-2.8.0 storageType: Durable topology: master: diff --git a/docs/guides/elasticsearch/monitoring/using-builtin-prometheus.md b/docs/guides/elasticsearch/monitoring/using-builtin-prometheus.md index 2aa6f15939..a95ae971d8 100644 --- a/docs/guides/elasticsearch/monitoring/using-builtin-prometheus.md +++ b/docs/guides/elasticsearch/monitoring/using-builtin-prometheus.md @@ -49,7 +49,7 @@ metadata: name: builtin-prom-es namespace: demo spec: - version: searchguard-7.9.3 + version: xpack-8.11.1 terminationPolicy: WipeOut storage: storageClassName: "standard" diff --git a/docs/guides/elasticsearch/monitoring/using-prometheus-operator.md b/docs/guides/elasticsearch/monitoring/using-prometheus-operator.md index 5b722cf7d2..00168b94aa 100644 --- a/docs/guides/elasticsearch/monitoring/using-prometheus-operator.md +++ b/docs/guides/elasticsearch/monitoring/using-prometheus-operator.md @@ -95,7 +95,7 @@ metadata: name: coreos-prom-es namespace: demo spec: - version: searchguard-7.9.3 + version: xpack-8.11.1 terminationPolicy: WipeOut storage: storageClassName: "standard" diff --git a/docs/guides/elasticsearch/plugins-backup/overview/index.md b/docs/guides/elasticsearch/plugins-backup/overview/index.md index e1f5043904..f4e0907a85 100644 --- a/docs/guides/elasticsearch/plugins-backup/overview/index.md +++ b/docs/guides/elasticsearch/plugins-backup/overview/index.md @@ -35,7 +35,7 @@ $ kubectl get elasticsearchversions NAME VERSION DISTRIBUTION DB_IMAGE DEPRECATED AGE kubedb-xpack-7.12.0 7.12.0 KubeDB kubedb/elasticsearch:7.12.0-xpack-v2021.08.23 4h44m kubedb-xpack-7.13.2 7.13.2 KubeDB kubedb/elasticsearch:7.13.2-xpack-v2021.08.23 4h44m -kubedb-xpack-7.14.0 7.14.0 KubeDB kubedb/elasticsearch:7.14.0-xpack-v2021.08.23 4h44m +xpack-8.11.1 7.14.0 KubeDB kubedb/elasticsearch:7.14.0-xpack-v2021.08.23 4h44m kubedb-xpack-7.9.1 7.9.1 KubeDB kubedb/elasticsearch:7.9.1-xpack-v2021.08.23 4h44m ``` diff --git a/docs/guides/elasticsearch/plugins-backup/s3-repository/index.md b/docs/guides/elasticsearch/plugins-backup/s3-repository/index.md index f0a1840b24..f452de508f 100644 --- a/docs/guides/elasticsearch/plugins-backup/s3-repository/index.md +++ b/docs/guides/elasticsearch/plugins-backup/s3-repository/index.md @@ -116,7 +116,7 @@ spec: name: es-secure-settings enableSSL: true # we are using ElasticsearchVersion with pre-installed s3 repository plugin - version: kubedb-xpack-7.14.0 + version: xpack-8.11.1 storageType: Durable replicas: 3 storage: @@ -138,9 +138,9 @@ elasticsearch.kubedb.com/sample-es created ```bash $ kubectl get es -n demo -w NAME VERSION STATUS AGE -sample-es kubedb-xpack-7.14.0 0s -sample-es kubedb-xpack-7.14.0 Provisioning 19s -sample-es kubedb-xpack-7.14.0 Ready 41s +sample-es xpack-8.11.1 0s +sample-es xpack-8.11.1 Provisioning 19s +sample-es xpack-8.11.1 Ready 41s ``` ### Populate Data diff --git a/docs/guides/elasticsearch/plugins-backup/s3-repository/yamls/elasticsearch.yaml b/docs/guides/elasticsearch/plugins-backup/s3-repository/yamls/elasticsearch.yaml index 8975d2a4fd..0ec15069ef 100644 --- a/docs/guides/elasticsearch/plugins-backup/s3-repository/yamls/elasticsearch.yaml +++ b/docs/guides/elasticsearch/plugins-backup/s3-repository/yamls/elasticsearch.yaml @@ -12,7 +12,7 @@ spec: name: es-secure-settings enableSSL: true # we are using ElasticsearchVersion with pre-installed s3 repository plugin - version: kubedb-xpack-7.14.0 + version: xpack-8.11.1 storageType: Durable replicas: 3 storage: diff --git a/docs/guides/elasticsearch/plugins/x-pack/configuration.md b/docs/guides/elasticsearch/plugins/x-pack/configuration.md index e3e1c39916..8de5078534 100644 --- a/docs/guides/elasticsearch/plugins/x-pack/configuration.md +++ b/docs/guides/elasticsearch/plugins/x-pack/configuration.md @@ -51,7 +51,7 @@ kubectl get elasticsearchversions 7.3.2 -o yaml apiVersion: catalog.kubedb.com/v1alpha1 kind: ElasticsearchVersion metadata: - name: xpack-7.9.1-v1 + name: xpack-8.11.1 spec: authPlugin: X-Pack db: @@ -92,7 +92,7 @@ metadata: name: config-elasticsearch namespace: demo spec: - version: searchguard-7.9.3 + version: xpack-8.11.1 storage: storageClassName: "standard" accessModes: @@ -143,7 +143,7 @@ spec: storageClassName: standard storageType: Durable terminationPolicy: Halt - version: searchguard-7.9.3 + version: xpack-8.11.1 status: observedGeneration: 1$4210395375389091791 phase: Running diff --git a/docs/guides/elasticsearch/plugins/x-pack/disable-xpack.md b/docs/guides/elasticsearch/plugins/x-pack/disable-xpack.md index 7797b0f9f3..60373ba62e 100644 --- a/docs/guides/elasticsearch/plugins/x-pack/disable-xpack.md +++ b/docs/guides/elasticsearch/plugins/x-pack/disable-xpack.md @@ -53,7 +53,7 @@ $ kubectl get elasticsearchversions 7.3.2 -o yaml apiVersion: catalog.kubedb.com/v1alpha1 kind: ElasticsearchVersion metadata: - name: searchguard-7.9.3 + name: xpack-8.11.1 spec: authPlugin: SearchGuard db: @@ -91,7 +91,7 @@ metadata: name: es-xpack-disabled namespace: demo spec: - version: searchguard-7.9.3 + version: xpack-8.11.1 disableSecurity: true storage: storageClassName: "standard" diff --git a/docs/guides/elasticsearch/plugins/x-pack/issue-certificate.md b/docs/guides/elasticsearch/plugins/x-pack/issue-certificate.md index a265f25db8..753fbcb132 100644 --- a/docs/guides/elasticsearch/plugins/x-pack/issue-certificate.md +++ b/docs/guides/elasticsearch/plugins/x-pack/issue-certificate.md @@ -306,7 +306,7 @@ metadata: name: custom-certificate-es-ssl namespace: demo spec: - version: searchguard-7.9.3 + version: xpack-8.11.1 enableSSL: true storage: storageClassName: "standard" diff --git a/docs/guides/elasticsearch/plugins/x-pack/use-tls.md b/docs/guides/elasticsearch/plugins/x-pack/use-tls.md index 86c573a21b..113eb8e9f3 100644 --- a/docs/guides/elasticsearch/plugins/x-pack/use-tls.md +++ b/docs/guides/elasticsearch/plugins/x-pack/use-tls.md @@ -48,7 +48,7 @@ metadata: name: ssl-elasticsearch namespace: demo spec: - version: searchguard-7.9.3 + version: xpack-8.11.1 replicas: 2 enableSSL: true storage: diff --git a/docs/guides/elasticsearch/private-registry/using-private-registry.md b/docs/guides/elasticsearch/private-registry/using-private-registry.md index 7edd9f71c9..4e6efc7a9d 100644 --- a/docs/guides/elasticsearch/private-registry/using-private-registry.md +++ b/docs/guides/elasticsearch/private-registry/using-private-registry.md @@ -86,7 +86,7 @@ Here, is an example of ElasticsearchVersion crd. Replace ` Note: An image with a higher modification tag will have more features and fixes than an image with a lower modification tag. Hence, it is recommended to use ElasticsearchVersion CRD with the highest modification tag to take advantage of the latest features. For example, use `xpack-7.9.1-v1` over `7.9.1-xpack`. +> Note: An image with a higher modification tag will have more features and fixes than an image with a lower modification tag. Hence, it is recommended to use ElasticsearchVersion CRD with the highest modification tag to take advantage of the latest features. For example, use `xpack-8.11.1` over `7.9.1-xpack`. ## Create an Elasticsearch Cluster @@ -148,7 +148,7 @@ metadata: name: es-quickstart namespace: demo spec: - version: xpack-8.2.0 + version: xpack-8.2.3 enableSSL: true replicas: 3 storageType: Durable @@ -185,9 +185,9 @@ The Elasticsearch's `STATUS` will go from `Provisioning` to `Ready` state within ```bash $ kubectl get elasticsearch -n demo -w NAME VERSION STATUS AGE -es-quickstart xpack-8.2.0 Provisioning 7s +es-quickstart xpack-8.2.3 Provisioning 7s ... ... -es-quickstart xpack-8.2.0 Ready 39s +es-quickstart xpack-8.2.3 Ready 39s ``` Describe the Elasticsearch object to observe the progress if something goes wrong or the status is not changing for a long period of time: @@ -384,7 +384,7 @@ Spec: Subject: Organizations: kubedb - Version: xpack-8.2.0 + Version: xpack-8.2.3 Status: Conditions: Last Transition Time: 2022-12-27T05:25:39Z diff --git a/docs/guides/elasticsearch/quickstart/overview/elasticsearch/yamls/elasticsearch.yaml b/docs/guides/elasticsearch/quickstart/overview/elasticsearch/yamls/elasticsearch.yaml index 34704e4200..6446a26577 100644 --- a/docs/guides/elasticsearch/quickstart/overview/elasticsearch/yamls/elasticsearch.yaml +++ b/docs/guides/elasticsearch/quickstart/overview/elasticsearch/yamls/elasticsearch.yaml @@ -4,7 +4,7 @@ metadata: name: es-quickstart namespace: demo spec: - version: xpack-8.2.0 + version: xpack-8.2.3 enableSSL: true replicas: 3 storageType: Durable diff --git a/docs/guides/elasticsearch/quickstart/overview/opensearch/index.md b/docs/guides/elasticsearch/quickstart/overview/opensearch/index.md index 97294d3c87..b6fd76c136 100644 --- a/docs/guides/elasticsearch/quickstart/overview/opensearch/index.md +++ b/docs/guides/elasticsearch/quickstart/overview/opensearch/index.md @@ -63,16 +63,16 @@ $ kubectl get elasticsearchversions NAME VERSION DISTRIBUTION DB_IMAGE DEPRECATED AGE kubedb-xpack-7.12.0 7.12.0 KubeDB kubedb/elasticsearch:7.12.0-xpack-v2021.08.23 17h kubedb-xpack-7.13.2 7.13.2 KubeDB kubedb/elasticsearch:7.13.2-xpack-v2021.08.23 17h -kubedb-xpack-7.14.0 7.14.0 KubeDB kubedb/elasticsearch:7.14.0-xpack-v2021.08.23 17h -kubedb-xpack-7.16.2 7.16.2 KubeDB kubedb/elasticsearch:7.16.2-xpack-v2021.12.24 17h +xpack-8.11.1 7.14.0 KubeDB kubedb/elasticsearch:7.14.0-xpack-v2021.08.23 17h +kubedb-xpack-8.11.1 7.16.2 KubeDB kubedb/elasticsearch:7.16.2-xpack-v2021.12.24 17h kubedb-xpack-7.9.1 7.9.1 KubeDB kubedb/elasticsearch:7.9.1-xpack-v2021.08.23 17h opendistro-1.0.2 7.0.1 OpenDistro amazon/opendistro-for-elasticsearch:1.0.2 17h opendistro-1.0.2-v1 7.0.1 OpenDistro amazon/opendistro-for-elasticsearch:1.0.2 17h opendistro-1.1.0 7.1.1 OpenDistro amazon/opendistro-for-elasticsearch:1.1.0 17h opendistro-1.1.0-v1 7.1.1 OpenDistro amazon/opendistro-for-elasticsearch:1.1.0 17h opendistro-1.10.1 7.9.1 OpenDistro amazon/opendistro-for-elasticsearch:1.10.1 17h -opendistro-1.11.0 7.9.1 OpenDistro amazon/opendistro-for-elasticsearch:1.10.1 17h -opendistro-1.12.0 7.10.0 OpenDistro amazon/opendistro-for-elasticsearch:1.12.0 17h +opensearch-2.8.0 7.9.1 OpenDistro amazon/opendistro-for-elasticsearch:1.10.1 17h +opensearch-2.8.0 7.10.0 OpenDistro amazon/opendistro-for-elasticsearch:1.12.0 17h opendistro-1.13.2 7.10.2 OpenDistro amazon/opendistro-for-elasticsearch:1.13.2 17h opendistro-1.2.1 7.2.1 OpenDistro amazon/opendistro-for-elasticsearch:1.2.1 17h opendistro-1.2.1-v1 7.2.1 OpenDistro amazon/opendistro-for-elasticsearch:1.2.1 17h @@ -89,7 +89,7 @@ opendistro-1.8.0-v1 7.7.0 OpenDistro amazon/opendistro-for-elasticsea opendistro-1.9.0 7.8.0 OpenDistro amazon/opendistro-for-elasticsearch:1.9.0 17h opendistro-1.9.0-v1 7.8.0 OpenDistro amazon/opendistro-for-elasticsearch:1.9.0 17h opensearch-1.1.0 1.1.0 OpenSearch opensearchproject/opensearch:1.1.0 17h -opensearch-1.2.2 1.2.2 OpenSearch opensearchproject/opensearch:1.2.2 17h +opensearch-2.8.0 1.2.2 OpenSearch opensearchproject/opensearch:1.2.2 17h searchguard-6.8.1 6.8.1 SearchGuard floragunncom/sg-elasticsearch:6.8.1-oss-25.1 17h searchguard-6.8.1-v1 6.8.1 SearchGuard floragunncom/sg-elasticsearch:6.8.1-oss-25.1 17h searchguard-7.0.1 7.0.1 SearchGuard floragunncom/sg-elasticsearch:7.0.1-oss-35.0.0 17h @@ -97,12 +97,12 @@ searchguard-7.0.1-v1 7.0.1 SearchGuard floragunncom/sg-elasticsearch:7. searchguard-7.1.1 7.1.1 SearchGuard floragunncom/sg-elasticsearch:7.1.1-oss-35.0.0 17h searchguard-7.1.1-v1 7.1.1 SearchGuard floragunncom/sg-elasticsearch:7.1.1-oss-35.0.0 17h searchguard-7.10.2 7.10.2 SearchGuard floragunncom/sg-elasticsearch:7.10.2-oss-49.0.0 17h -searchguard-7.14.2 7.14.2 SearchGuard floragunncom/sg-elasticsearch:7.14.2-52.3.0 17h +xpack-8.11.1 7.14.2 SearchGuard floragunncom/sg-elasticsearch:7.14.2-52.3.0 17h searchguard-7.3.2 7.3.2 SearchGuard floragunncom/sg-elasticsearch:7.3.2-oss-37.0.0 17h searchguard-7.5.2 7.5.2 SearchGuard floragunncom/sg-elasticsearch:7.5.2-oss-40.0.0 17h -searchguard-7.5.2-v1 7.5.2 SearchGuard floragunncom/sg-elasticsearch:7.5.2-oss-40.0.0 17h +xpack-8.11.1 7.5.2 SearchGuard floragunncom/sg-elasticsearch:7.5.2-oss-40.0.0 17h searchguard-7.8.1 7.8.1 SearchGuard floragunncom/sg-elasticsearch:7.8.1-oss-43.0.0 17h -searchguard-7.9.3 7.9.3 SearchGuard floragunncom/sg-elasticsearch:7.9.3-oss-47.1.0 17h +xpack-8.11.1 7.9.3 SearchGuard floragunncom/sg-elasticsearch:7.9.3-oss-47.1.0 17h xpack-6.8.10-v1 6.8.10 ElasticStack elasticsearch:6.8.10 17h xpack-6.8.16 6.8.16 ElasticStack elasticsearch:6.8.16 17h xpack-6.8.22 6.8.22 ElasticStack elasticsearch:6.8.22 17h @@ -111,8 +111,8 @@ xpack-7.1.1-v1 7.1.1 ElasticStack elasticsearch:7.1.1 xpack-7.12.0 7.12.0 ElasticStack elasticsearch:7.12.0 17h xpack-7.12.0-v1 7.12.0 ElasticStack elasticsearch:7.12.0 17h xpack-7.13.2 7.13.2 ElasticStack elasticsearch:7.13.2 17h -xpack-7.14.0 7.14.0 ElasticStack elasticsearch:7.14.0 17h -xpack-7.16.2 7.16.2 ElasticStack elasticsearch:7.16.2 17h +xpack-8.11.1 7.14.0 ElasticStack elasticsearch:7.14.0 17h +xpack-8.11.1 7.16.2 ElasticStack elasticsearch:7.16.2 17h xpack-7.2.1-v1 7.2.1 ElasticStack elasticsearch:7.2.1 17h xpack-7.3.2-v1 7.3.2 ElasticStack elasticsearch:7.3.2 17h xpack-7.4.2-v1 7.4.2 ElasticStack elasticsearch:7.4.2 17h @@ -120,15 +120,15 @@ xpack-7.5.2-v1 7.5.2 ElasticStack elasticsearch:7.5.2 xpack-7.6.2-v1 7.6.2 ElasticStack elasticsearch:7.6.2 17h xpack-7.7.1-v1 7.7.1 ElasticStack elasticsearch:7.7.1 17h xpack-7.8.0-v1 7.8.0 ElasticStack elasticsearch:7.8.0 17h -xpack-7.9.1-v1 7.9.1 ElasticStack elasticsearch:7.9.1 17h +xpack-8.11.1 7.9.1 ElasticStack elasticsearch:7.9.1 17h xpack-7.9.1-v2 7.9.1 ElasticStack elasticsearch:7.9.1 17h ``` Notice the `DEPRECATED` column. Here, `true` means that this ElasticsearchVersion is deprecated for the current KubeDB version. KubeDB will not work for deprecated ElasticsearchVersion. -In this tutorial, we will use `opensearch-1.2.2` ElasticsearchVersion CR to create an OpenSearch cluster. +In this tutorial, we will use `opensearch-2.8.0` ElasticsearchVersion CR to create an OpenSearch cluster. -> Note: An image with a higher modification tag will have more features and fixes than an image with a lower modification tag. Hence, it is recommended to use ElasticsearchVersion CRD with the highest modification tag to take advantage of the latest features. For example, we are using `opensearch-1.2.2` over `opensearch-1.1.0`. +> Note: An image with a higher modification tag will have more features and fixes than an image with a lower modification tag. Hence, it is recommended to use ElasticsearchVersion CRD with the highest modification tag to take advantage of the latest features. For example, we are using `opensearch-2.8.0` over `opensearch-1.1.0`. ## Create an OpenSearch Cluster @@ -143,7 +143,7 @@ metadata: name: sample-opensearch namespace: demo spec: - version: opensearch-1.2.2 + version: opensearch-2.8.0 enableSSL: true replicas: 3 storageType: Durable @@ -159,7 +159,7 @@ spec: Here, -- `spec.version` - is the name of the ElasticsearchVersion CR. Here, we are using `opensearch-1.2.2` version. +- `spec.version` - is the name of the ElasticsearchVersion CR. Here, we are using `opensearch-2.8.0` version. - `spec.enableSSL` - specifies whether the HTTP layer is secured with certificates or not. - `spec.replicas` - specifies the number of OpenSearch nodes. - `spec.storageType` - specifies the type of storage that will be used for OpenSearch database. It can be `Durable` or `Ephemeral`. The default value of this field is `Durable`. If `Ephemeral` is used then KubeDB will create the OpenSearch database using `EmptyDir` volume. In this case, you don't have to specify `spec.storage` field. This is useful for testing purposes. @@ -180,11 +180,11 @@ Wait for few minutes until the `STATUS` will go from `Provisioning` to `Ready`. ```bash $ kubectl get elasticsearch -n demo -w NAME VERSION STATUS AGE -sample-opensearch opensearch-1.2.2 Provisioning 49s +sample-opensearch opensearch-2.8.0 Provisioning 49s ... ... $ kubectl get elasticsearch -n demo -w NAME VERSION STATUS AGE -sample-opensearch opensearch-1.2.2 Ready 5m4s +sample-opensearch opensearch-2.8.0 Ready 5m4s ``` Describe the object to observe the progress if something goes wrong or the status is not changing for a long period of time: @@ -317,7 +317,7 @@ Spec: Subject: Organizations: kubedb - Version: opensearch-1.2.2 + Version: opensearch-2.8.0 Status: Conditions: Last Transition Time: 2022-02-15T07:00:21Z diff --git a/docs/guides/elasticsearch/quickstart/overview/opensearch/yamls/opensearch.yaml b/docs/guides/elasticsearch/quickstart/overview/opensearch/yamls/opensearch.yaml index 2f4948dc7d..48b93f6dff 100644 --- a/docs/guides/elasticsearch/quickstart/overview/opensearch/yamls/opensearch.yaml +++ b/docs/guides/elasticsearch/quickstart/overview/opensearch/yamls/opensearch.yaml @@ -4,7 +4,7 @@ metadata: name: sample-opensearch namespace: demo spec: - version: opensearch-1.2.2 + version: opensearch-2.8.0 enableSSL: true replicas: 3 storageType: Durable diff --git a/docs/guides/mongodb/arbiter/replicaset.md b/docs/guides/mongodb/arbiter/replicaset.md index 483fe792e0..cc40ab4f28 100644 --- a/docs/guides/mongodb/arbiter/replicaset.md +++ b/docs/guides/mongodb/arbiter/replicaset.md @@ -48,7 +48,7 @@ metadata: name: mongo-arb namespace: demo spec: - version: "4.4.6" + version: "4.4.26" replicaSet: name: "rs0" replicas: 2 @@ -165,7 +165,7 @@ Auth Secret: AppBinding: Metadata: Annotations: - kubectl.kubernetes.io/last-applied-configuration: {"apiVersion":"kubedb.com/v1alpha2","kind":"MongoDB","metadata":{"annotations":{},"name":"mongo-arb","namespace":"demo"},"spec":{"arbiter":{"podTemplate":null},"replicaSet":{"name":"rs0"},"replicas":2,"storage":{"accessModes":["ReadWriteOnce"],"resources":{"requests":{"storage":"500Mi"}},"storageClassName":"standard"},"storageType":"Durable","terminationPolicy":"WipeOut","version":"4.4.6"}} + kubectl.kubernetes.io/last-applied-configuration: {"apiVersion":"kubedb.com/v1alpha2","kind":"MongoDB","metadata":{"annotations":{},"name":"mongo-arb","namespace":"demo"},"spec":{"arbiter":{"podTemplate":null},"replicaSet":{"name":"rs0"},"replicas":2,"storage":{"accessModes":["ReadWriteOnce"],"resources":{"requests":{"storage":"500Mi"}},"storageClassName":"standard"},"storageType":"Durable","terminationPolicy":"WipeOut","version":"4.4.26"}} Creation Timestamp: 2022-04-21T08:40:21Z Labels: @@ -195,7 +195,7 @@ AppBinding: Secret: Name: mongo-arb-auth Type: kubedb.com/mongodb - Version: 4.4.6 + Version: 4.4.26 Events: Type Reason Age From Message @@ -241,7 +241,7 @@ kind: MongoDB metadata: annotations: kubectl.kubernetes.io/last-applied-configuration: | - {"apiVersion":"kubedb.com/v1alpha2","kind":"MongoDB","metadata":{"annotations":{},"name":"mongo-arb","namespace":"demo"},"spec":{"arbiter":{"podTemplate":null},"replicaSet":{"name":"rs0"},"replicas":2,"storage":{"accessModes":["ReadWriteOnce"],"resources":{"requests":{"storage":"500Mi"}},"storageClassName":"standard"},"storageType":"Durable","terminationPolicy":"WipeOut","version":"4.4.6"}} + {"apiVersion":"kubedb.com/v1alpha2","kind":"MongoDB","metadata":{"annotations":{},"name":"mongo-arb","namespace":"demo"},"spec":{"arbiter":{"podTemplate":null},"replicaSet":{"name":"rs0"},"replicas":2,"storage":{"accessModes":["ReadWriteOnce"],"resources":{"requests":{"storage":"500Mi"}},"storageClassName":"standard"},"storageType":"Durable","terminationPolicy":"WipeOut","version":"4.4.26"}} creationTimestamp: "2022-04-21T08:39:32Z" finalizers: - kubedb.com @@ -391,7 +391,7 @@ spec: storageEngine: wiredTiger storageType: Durable terminationPolicy: WipeOut - version: 4.4.6 + version: 4.4.26 status: conditions: - lastTransitionTime: "2022-04-21T08:39:32Z" @@ -447,9 +447,9 @@ OX4yb!IFm;~yAHkD $ kubectl exec -it mongo-arb-0 -n demo bash mongodb@mongo-arb-0:/$ mongo admin -u root -p 'OX4yb!IFm;~yAHkD' -MongoDB shell version v4.4.6 +MongoDB shell version v4.4.26 connecting to: mongodb://127.0.0.1:27017/admin -MongoDB server version: 4.4.6 +MongoDB server version: 4.4.26 Welcome to the MongoDB shell. rs0:PRIMARY> rs.status() @@ -637,9 +637,9 @@ We will exec in `mongo-arb-1`(which is secondary member right now) to check the ```bash $ kubectl exec -it mongo-arb-1 -n demo bash mongodb@mongo-arb-1:/$ mongo admin -u root -p 'OX4yb!IFm;~yAHkD' -MongoDB shell version v4.4.6 +MongoDB shell version v4.4.26 connecting to: mongodb://127.0.0.1:27017/admin -MongoDB server version: 4.4.6 +MongoDB server version: 4.4.26 Welcome to the MongoDB shell. rs0:SECONDARY> rs.slaveOk() @@ -708,9 +708,9 @@ Now verify the automatic failover, Let's exec in `mongo-arb-0` pod, ```bash $ kubectl exec -it mongo-arb-0 -n demo bash mongodb@mongo-arb-1:/$ mongo admin -u root -p 'OX4yb!IFm;~yAHkD' -MongoDB shell version v4.4.6 +MongoDB shell version v4.4.26 connecting to: mongodb://127.0.0.1:27017/admin -MongoDB server version: 4.4.6 +MongoDB server version: 4.4.26 Welcome to the MongoDB shell. rs0:SECONDARY> rs.isMaster().primary @@ -763,7 +763,7 @@ Now, you can run the following command to get all mongodb resources in demo name ```bash $ kubectl get mg,sts,svc,secret,pvc -n demo NAME VERSION STATUS AGE -mongodb.kubedb.com/mongo-arb 4.4.6 Halted 21m +mongodb.kubedb.com/mongo-arb 4.4.26 Halted 21m NAME TYPE DATA AGE secret/default-token-nzk64 kubernetes.io/service-account-token 3 146m @@ -791,7 +791,7 @@ When the database is resumed successfully, you can see the database Status is se ```bash $ kubectl get mg -n demo NAME VERSION STATUS AGE -mongodb.kubedb.com/mongo-arb 4.4.6 Ready 23m +mongodb.kubedb.com/mongo-arb 4.4.26 Ready 23m ``` Now, If you again exec into the primary `pod` and look for previous data, you will see that, all the data persists. diff --git a/docs/guides/mongodb/arbiter/sharding.md b/docs/guides/mongodb/arbiter/sharding.md index eb4ffe8258..8776f10b55 100644 --- a/docs/guides/mongodb/arbiter/sharding.md +++ b/docs/guides/mongodb/arbiter/sharding.md @@ -48,7 +48,7 @@ metadata: name: mongo-sh-arb namespace: demo spec: - version: "4.4.6" + version: "4.4.26" shardTopology: configServer: replicas: 3 @@ -119,7 +119,7 @@ MongoDB `mongo-sh-arb` state, ```bash $ kubectl get mg -n demo NAME VERSION STATUS AGE -mongodb.kubedb.com/mongo-sh-arb 4.4.6 Ready 97s +mongodb.kubedb.com/mongo-sh-arb 4.4.26 Ready 97s ``` All the types of nodes `Shard`, `ConfigServer` & `Mongos` are deployed as statefulset. @@ -184,7 +184,7 @@ kind: MongoDB metadata: annotations: kubectl.kubernetes.io/last-applied-configuration: | - {"apiVersion":"kubedb.com/v1alpha2","kind":"MongoDB","metadata":{"annotations":{},"name":"mongo-sh-arb","namespace":"demo"},"spec":{"arbiter":{"podTemplate":{"spec":{"requests":{"cpu":"200m","memory":"200Mi"},"resources":null}}},"shardTopology":{"configServer":{"replicas":3,"storage":{"resources":{"requests":{"storage":"500Mi"}},"storageClassName":"standard"}},"mongos":{"replicas":2},"shard":{"podTemplate":{"spec":{"resources":{"requests":{"cpu":"400m","memory":"300Mi"}}}},"replicas":2,"shards":2,"storage":{"resources":{"requests":{"storage":"500Mi"}},"storageClassName":"standard"}}},"terminationPolicy":"WipeOut","version":"4.4.6"}} + {"apiVersion":"kubedb.com/v1alpha2","kind":"MongoDB","metadata":{"annotations":{},"name":"mongo-sh-arb","namespace":"demo"},"spec":{"arbiter":{"podTemplate":{"spec":{"requests":{"cpu":"200m","memory":"200Mi"},"resources":null}}},"shardTopology":{"configServer":{"replicas":3,"storage":{"resources":{"requests":{"storage":"500Mi"}},"storageClassName":"standard"}},"mongos":{"replicas":2},"shard":{"podTemplate":{"spec":{"resources":{"requests":{"cpu":"400m","memory":"300Mi"}}}},"replicas":2,"shards":2,"storage":{"resources":{"requests":{"storage":"500Mi"}},"storageClassName":"standard"}}},"terminationPolicy":"WipeOut","version":"4.4.26"}} creationTimestamp: "2022-04-21T09:29:07Z" finalizers: - kubedb.com @@ -478,7 +478,7 @@ spec: storageEngine: wiredTiger storageType: Durable terminationPolicy: WipeOut - version: 4.4.6 + version: 4.4.26 status: conditions: - lastTransitionTime: "2022-04-21T09:29:07Z" @@ -553,10 +553,10 @@ mongo-sh-arb-mongos-1 1/1 Running 0 6m20s $ kubectl exec -it mongo-sh-arb-mongos-0 -n demo bash mongodb@mongo-sh-mongos-0:/$ mongo admin -u root -p '6&UiN5;qq)Tnai=7' -MongoDB shell version v4.4.6 +MongoDB shell version v4.4.26 connecting to: mongodb://127.0.0.1:27017/admin?compressors=disabled&gssapiServiceName=mongodb Implicit session: session { "id" : UUID("bf87addd-4245-45b1-a470-fabb3dcc19ab") } -MongoDB server version: 4.4.6 +MongoDB server version: 4.4.26 Welcome to the MongoDB shell. For interactive help, type "help". For more comprehensive documentation, see @@ -616,7 +616,7 @@ mongos> sh.status() { "_id" : "shard0", "host" : "shard0/mongo-sh-arb-shard0-0.mongo-sh-arb-shard0-pods.demo.svc.cluster.local:27017,mongo-sh-arb-shard0-1.mongo-sh-arb-shard0-pods.demo.svc.cluster.local:27017", "state" : 1 } { "_id" : "shard1", "host" : "shard1/mongo-sh-arb-shard1-0.mongo-sh-arb-shard1-pods.demo.svc.cluster.local:27017,mongo-sh-arb-shard1-1.mongo-sh-arb-shard1-pods.demo.svc.cluster.local:27017", "state" : 1 } active mongoses: - "4.4.6" : 2 + "4.4.26" : 2 autosplit: Currently enabled: yes balancer: @@ -659,9 +659,9 @@ As `sh.status()` command only shows the data bearing members, if we want to assu kubectl exec -it pod/mongo-sh-arb-shard0-1 -n demo bash root@mongo-sh-arb-shard0-1:/ mongo admin -u root -p '6&UiN5;qq)Tnai=7' -MongoDB shell version v4.4.6 +MongoDB shell version v4.4.26 connecting to: mongodb://127.0.0.1:27017/admin -MongoDB server version: 4.4.6 +MongoDB server version: 4.4.26 Welcome to the MongoDB shell. shard0:PRIMARY> rs.status().members @@ -797,7 +797,7 @@ mongos> sh.status(); { "_id" : "shard0", "host" : "shard0/mongo-sh-arb-shard0-0.mongo-sh-arb-shard0-pods.demo.svc.cluster.local:27017,mongo-sh-arb-shard0-1.mongo-sh-arb-shard0-pods.demo.svc.cluster.local:27017", "state" : 1 } { "_id" : "shard1", "host" : "shard1/mongo-sh-arb-shard1-0.mongo-sh-arb-shard1-pods.demo.svc.cluster.local:27017,mongo-sh-arb-shard1-1.mongo-sh-arb-shard1-pods.demo.svc.cluster.local:27017", "state" : 1 } active mongoses: - "4.4.6" : 2 + "4.4.26" : 2 autosplit: Currently enabled: yes balancer: @@ -867,7 +867,7 @@ mongos> sh.status() { "_id" : "shard0", "host" : "shard0/mongo-sh-arb-shard0-0.mongo-sh-arb-shard0-pods.demo.svc.cluster.local:27017,mongo-sh-arb-shard0-1.mongo-sh-arb-shard0-pods.demo.svc.cluster.local:27017", "state" : 1 } { "_id" : "shard1", "host" : "shard1/mongo-sh-arb-shard1-0.mongo-sh-arb-shard1-pods.demo.svc.cluster.local:27017,mongo-sh-arb-shard1-1.mongo-sh-arb-shard1-pods.demo.svc.cluster.local:27017", "state" : 1 } active mongoses: - "4.4.6" : 2 + "4.4.26" : 2 autosplit: Currently enabled: yes balancer: @@ -934,7 +934,7 @@ Now, you can run the following command to get all mongodb resources in demo name ```bash $ kubectl get mg,sts,svc,secret,pvc -n demo NAME VERSION STATUS AGE -mongodb.kubedb.com/mongo-sh-arb 4.4.6 Halted 26m +mongodb.kubedb.com/mongo-sh-arb 4.4.26 Halted 26m NAME TYPE DATA AGE secret/default-token-bg2wb kubernetes.io/service-account-token 3 26m @@ -969,7 +969,7 @@ When the database is resumed successfully, you can see the database Status is se ```bash $ kubectl get mg -n demo NAME VERSION STATUS AGE -mongodb.kubedb.com/mongo-sh-arb 4.4.6 Ready 28m +mongodb.kubedb.com/mongo-sh-arb 4.4.26 Ready 28m ``` Now, If you again exec into `pod` and look for previous data, you will see that, all the data persists. @@ -1004,7 +1004,7 @@ mongos> sh.status() { "_id" : "shard0", "host" : "shard0/mongo-sh-arb-shard0-0.mongo-sh-arb-shard0-pods.demo.svc.cluster.local:27017,mongo-sh-arb-shard0-1.mongo-sh-arb-shard0-pods.demo.svc.cluster.local:27017", "state" : 1 } { "_id" : "shard1", "host" : "shard1/mongo-sh-arb-shard1-0.mongo-sh-arb-shard1-pods.demo.svc.cluster.local:27017,mongo-sh-arb-shard1-1.mongo-sh-arb-shard1-pods.demo.svc.cluster.local:27017", "state" : 1 } active mongoses: - "4.4.6" : 2 + "4.4.26" : 2 autosplit: Currently enabled: yes balancer: diff --git a/docs/guides/mongodb/autoscaler/compute/replicaset.md b/docs/guides/mongodb/autoscaler/compute/replicaset.md index 225eb8f68e..0e8cfff2a5 100644 --- a/docs/guides/mongodb/autoscaler/compute/replicaset.md +++ b/docs/guides/mongodb/autoscaler/compute/replicaset.md @@ -47,7 +47,7 @@ Here, we are going to deploy a `MongoDB` Replicaset using a supported version by #### Deploy MongoDB Replicaset -In this section, we are going to deploy a MongoDB Replicaset database with version `4.4.6`. Then, in the next section we will set up autoscaling for this database using `MongoDBAutoscaler` CRD. Below is the YAML of the `MongoDB` CR that we are going to create, +In this section, we are going to deploy a MongoDB Replicaset database with version `4.4.26`. Then, in the next section we will set up autoscaling for this database using `MongoDBAutoscaler` CRD. Below is the YAML of the `MongoDB` CR that we are going to create, ```yaml apiVersion: kubedb.com/v1alpha2 @@ -56,7 +56,7 @@ metadata: name: mg-rs namespace: demo spec: - version: "4.2.3" + version: "4.4.26" replicaSet: name: "replicaset" replicas: 3 @@ -90,7 +90,7 @@ Now, wait until `mg-rs` has status `Ready`. i.e, ```bash $ kubectl get mg -n demo NAME VERSION STATUS AGE -mg-rs 4.2.3 Ready 2m53s +mg-rs 4.4.26 Ready 2m53s ``` Let's check the Pod containers resources, diff --git a/docs/guides/mongodb/autoscaler/compute/sharding.md b/docs/guides/mongodb/autoscaler/compute/sharding.md index 4fc10a335d..955b3dc496 100644 --- a/docs/guides/mongodb/autoscaler/compute/sharding.md +++ b/docs/guides/mongodb/autoscaler/compute/sharding.md @@ -47,7 +47,7 @@ Here, we are going to deploy a `MongoDB` sharded database using a supported vers #### Deploy MongoDB Sharded Database -In this section, we are going to deploy a MongoDB sharded database with version `4.2.3`. Then, in the next section we will set up autoscaling for this database using `MongoDBAutoscaler` CRD. Below is the YAML of the `MongoDB` CR that we are going to create, +In this section, we are going to deploy a MongoDB sharded database with version `4.4.26`. Then, in the next section we will set up autoscaling for this database using `MongoDBAutoscaler` CRD. Below is the YAML of the `MongoDB` CR that we are going to create, ```yaml apiVersion: kubedb.com/v1alpha2 @@ -56,7 +56,7 @@ metadata: name: mg-sh namespace: demo spec: - version: "4.2.3" + version: "4.4.26" storageType: Durable shardTopology: configServer: @@ -107,7 +107,7 @@ Now, wait until `mg-sh` has status `Ready`. i.e, ```bash $ kubectl get mg -n demo NAME VERSION STATUS AGE -mg-sh 4.2.3 Ready 3m57s +mg-sh 4.4.26 Ready 3m57s ``` Let's check a shard Pod containers resources, diff --git a/docs/guides/mongodb/autoscaler/compute/standalone.md b/docs/guides/mongodb/autoscaler/compute/standalone.md index 519a1c9f97..fc02bbb534 100644 --- a/docs/guides/mongodb/autoscaler/compute/standalone.md +++ b/docs/guides/mongodb/autoscaler/compute/standalone.md @@ -47,7 +47,7 @@ Here, we are going to deploy a `MongoDB` standalone using a supported version by #### Deploy MongoDB standalone -In this section, we are going to deploy a MongoDB standalone database with version `4.2.3`. Then, in the next section we will set up autoscaling for this database using `MongoDBAutoscaler` CRD. Below is the YAML of the `MongoDB` CR that we are going to create, +In this section, we are going to deploy a MongoDB standalone database with version `4.4.26`. Then, in the next section we will set up autoscaling for this database using `MongoDBAutoscaler` CRD. Below is the YAML of the `MongoDB` CR that we are going to create, ```yaml apiVersion: kubedb.com/v1alpha2 @@ -56,7 +56,7 @@ metadata: name: mg-standalone namespace: demo spec: - version: "4.2.3" + version: "4.4.26" storageType: Durable storage: resources: @@ -86,7 +86,7 @@ Now, wait until `mg-standalone` has status `Ready`. i.e, ```bash $ kubectl get mg -n demo NAME VERSION STATUS AGE -mg-standalone 4.2.3 Ready 2m53s +mg-standalone 4.4.26 Ready 2m53s ``` Let's check the Pod containers resources, diff --git a/docs/guides/mongodb/autoscaler/storage/replicaset.md b/docs/guides/mongodb/autoscaler/storage/replicaset.md index afbeca8e0d..0bc6adecce 100644 --- a/docs/guides/mongodb/autoscaler/storage/replicaset.md +++ b/docs/guides/mongodb/autoscaler/storage/replicaset.md @@ -62,7 +62,7 @@ Now, we are going to deploy a `MongoDB` replicaset using a supported version by #### Deploy MongoDB replicaset -In this section, we are going to deploy a MongoDB replicaset database with version `4.2.3`. Then, in the next section we will set up autoscaling for this database using `MongoDBAutoscaler` CRD. Below is the YAML of the `MongoDB` CR that we are going to create, +In this section, we are going to deploy a MongoDB replicaset database with version `4.4.26`. Then, in the next section we will set up autoscaling for this database using `MongoDBAutoscaler` CRD. Below is the YAML of the `MongoDB` CR that we are going to create, ```yaml apiVersion: kubedb.com/v1alpha2 @@ -71,7 +71,7 @@ metadata: name: mg-rs namespace: demo spec: - version: "4.2.3" + version: "4.4.26" replicaSet: name: "replicaset" replicas: 3 @@ -96,7 +96,7 @@ Now, wait until `mg-rs` has status `Ready`. i.e, ```bash $ kubectl get mg -n demo NAME VERSION STATUS AGE -mg-rs 4.2.3 Ready 2m53s +mg-rs 4.4.26 Ready 2m53s ``` Let's check volume size from statefulset, and from the persistent volume, diff --git a/docs/guides/mongodb/autoscaler/storage/sharding.md b/docs/guides/mongodb/autoscaler/storage/sharding.md index 00499383f2..b70bb7f491 100644 --- a/docs/guides/mongodb/autoscaler/storage/sharding.md +++ b/docs/guides/mongodb/autoscaler/storage/sharding.md @@ -62,7 +62,7 @@ Now, we are going to deploy a `MongoDB` sharded database using a supported versi #### Deploy MongoDB Sharded Database -In this section, we are going to deploy a MongoDB sharded database with version `4.2.3`. Then, in the next section we will set up autoscaling for this database using `MongoDBAutoscaler` CRD. Below is the YAML of the `MongoDB` CR that we are going to create, +In this section, we are going to deploy a MongoDB sharded database with version `4.4.26`. Then, in the next section we will set up autoscaling for this database using `MongoDBAutoscaler` CRD. Below is the YAML of the `MongoDB` CR that we are going to create, ```yaml apiVersion: kubedb.com/v1alpha2 @@ -71,7 +71,7 @@ metadata: name: mg-sh namespace: demo spec: - version: "4.2.3" + version: "4.4.26" storageType: Durable shardTopology: configServer: @@ -106,7 +106,7 @@ Now, wait until `mg-sh` has status `Ready`. i.e, ```bash $ kubectl get mg -n demo NAME VERSION STATUS AGE -mg-sh 4.2.3 Ready 3m51s +mg-sh 4.4.26 Ready 3m51s ``` Let's check volume size from one of the shard statefulset, and from the persistent volume, diff --git a/docs/guides/mongodb/autoscaler/storage/standalone.md b/docs/guides/mongodb/autoscaler/storage/standalone.md index f77a0eef30..ba8eb9ebba 100644 --- a/docs/guides/mongodb/autoscaler/storage/standalone.md +++ b/docs/guides/mongodb/autoscaler/storage/standalone.md @@ -62,7 +62,7 @@ Now, we are going to deploy a `MongoDB` standalone using a supported version by #### Deploy MongoDB standalone -In this section, we are going to deploy a MongoDB standalone database with version `4.2.3`. Then, in the next section we will set up autoscaling for this database using `MongoDBAutoscaler` CRD. Below is the YAML of the `MongoDB` CR that we are going to create, +In this section, we are going to deploy a MongoDB standalone database with version `4.4.26`. Then, in the next section we will set up autoscaling for this database using `MongoDBAutoscaler` CRD. Below is the YAML of the `MongoDB` CR that we are going to create, ```yaml apiVersion: kubedb.com/v1alpha2 @@ -71,7 +71,7 @@ metadata: name: mg-standalone namespace: demo spec: - version: "4.2.3" + version: "4.4.26" storageType: Durable storage: storageClassName: topolvm-provisioner @@ -93,7 +93,7 @@ Now, wait until `mg-standalone` has status `Ready`. i.e, ```bash $ kubectl get mg -n demo NAME VERSION STATUS AGE -mg-standalone 4.2.3 Ready 2m53s +mg-standalone 4.4.26 Ready 2m53s ``` Let's check volume size from statefulset, and from the persistent volume, diff --git a/docs/guides/mongodb/backup/auto-backup/examples/sample-mongodb-2.yaml b/docs/guides/mongodb/backup/auto-backup/examples/sample-mongodb-2.yaml index 55496e47b2..c02836a447 100644 --- a/docs/guides/mongodb/backup/auto-backup/examples/sample-mongodb-2.yaml +++ b/docs/guides/mongodb/backup/auto-backup/examples/sample-mongodb-2.yaml @@ -7,7 +7,7 @@ metadata: stash.appscode.com/backup-blueprint: mongodb-backup-template stash.appscode.com/schedule: "*/3 * * * *" spec: - version: "4.4.6" + version: "4.4.26" storageType: Durable storage: storageClassName: "standard" diff --git a/docs/guides/mongodb/backup/auto-backup/examples/sample-mongodb-3.yaml b/docs/guides/mongodb/backup/auto-backup/examples/sample-mongodb-3.yaml index e115295d2a..acd02f214b 100644 --- a/docs/guides/mongodb/backup/auto-backup/examples/sample-mongodb-3.yaml +++ b/docs/guides/mongodb/backup/auto-backup/examples/sample-mongodb-3.yaml @@ -7,7 +7,7 @@ metadata: stash.appscode.com/backup-blueprint: mongodb-backup-template params.stash.appscode.com/args: "--db=testdb" spec: - version: "4.4.6" + version: "4.4.26" storageType: Durable storage: storageClassName: "standard" diff --git a/docs/guides/mongodb/backup/auto-backup/examples/sample-mongodb.yaml b/docs/guides/mongodb/backup/auto-backup/examples/sample-mongodb.yaml index c1cb68ae01..a7a3c2f237 100644 --- a/docs/guides/mongodb/backup/auto-backup/examples/sample-mongodb.yaml +++ b/docs/guides/mongodb/backup/auto-backup/examples/sample-mongodb.yaml @@ -6,7 +6,7 @@ metadata: annotations: stash.appscode.com/backup-blueprint: mongodb-backup-template spec: - version: "4.4.6" + version: "4.4.26" storageType: Durable storage: storageClassName: "standard" diff --git a/docs/guides/mongodb/backup/auto-backup/index.md b/docs/guides/mongodb/backup/auto-backup/index.md index 344b6a1312..bb3ab37780 100644 --- a/docs/guides/mongodb/backup/auto-backup/index.md +++ b/docs/guides/mongodb/backup/auto-backup/index.md @@ -62,7 +62,7 @@ mongodb-backup-4.0.5 23h mongodb-backup-4.1.13 23h mongodb-backup-4.1.4 23h mongodb-backup-4.1.7 23h -mongodb-backup-4.2.3 23h +mongodb-backup-4.4.6 23h mongodb-backup-4.4.6 23h mongodb-backup-5.0.3 23h mongodb-restore-3.4.17 23h @@ -75,7 +75,7 @@ mongodb-restore-4.0.5 23h mongodb-restore-4.1.13 23h mongodb-restore-4.1.4 23h mongodb-restore-4.1.7 23h -mongodb-restore-4.2.3 23h +mongodb-restore-4.4.6 23h mongodb-restore-4.4.6 23h mongodb-restore-5.0.3 23h @@ -154,7 +154,7 @@ metadata: annotations: stash.appscode.com/backup-blueprint: mongodb-backup-template spec: - version: "4.4.6" + version: "4.4.26" storageType: Durable storage: storageClassName: "standard" @@ -329,7 +329,7 @@ metadata: stash.appscode.com/backup-blueprint: mongodb-backup-template stash.appscode.com/schedule: "*/3 * * * *" spec: - version: "4.4.6" + version: "4.4.26" storageType: Durable storage: storageClassName: "standard" @@ -515,7 +515,7 @@ metadata: stash.appscode.com/backup-blueprint: mongodb-backup-template params.stash.appscode.com/args: "--db=testdb" spec: - version: "4.4.6" + version: "4.4.26" storageType: Durable storage: storageClassName: "standard" diff --git a/docs/guides/mongodb/backup/customization/examples/sample-mariadb.yaml b/docs/guides/mongodb/backup/customization/examples/sample-mariadb.yaml index 67cdae04a8..d254e8cc4f 100644 --- a/docs/guides/mongodb/backup/customization/examples/sample-mariadb.yaml +++ b/docs/guides/mongodb/backup/customization/examples/sample-mariadb.yaml @@ -4,7 +4,7 @@ metadata: name: sample-mongodb namespace: demo spec: - version: "4.4.6" + version: "4.4.26" storageType: Durable storage: storageClassName: "standard" diff --git a/docs/guides/mongodb/backup/logical/replicaset/examples/mongodb-replicaset.yaml b/docs/guides/mongodb/backup/logical/replicaset/examples/mongodb-replicaset.yaml index b6cad02ed7..9cbd6dc992 100644 --- a/docs/guides/mongodb/backup/logical/replicaset/examples/mongodb-replicaset.yaml +++ b/docs/guides/mongodb/backup/logical/replicaset/examples/mongodb-replicaset.yaml @@ -4,7 +4,7 @@ metadata: name: sample-mgo-rs namespace: demo spec: - version: "4.2.3" + version: "4.4.26" replicas: 3 replicaSet: name: rs0 diff --git a/docs/guides/mongodb/backup/logical/replicaset/examples/restored-mongodb-replicaset.yaml b/docs/guides/mongodb/backup/logical/replicaset/examples/restored-mongodb-replicaset.yaml index 724871121c..228e44dd78 100644 --- a/docs/guides/mongodb/backup/logical/replicaset/examples/restored-mongodb-replicaset.yaml +++ b/docs/guides/mongodb/backup/logical/replicaset/examples/restored-mongodb-replicaset.yaml @@ -4,7 +4,7 @@ metadata: name: restored-mgo-rs namespace: demo spec: - version: "4.2.3" + version: "4.4.26" replicas: 3 replicaSet: name: rs0 diff --git a/docs/guides/mongodb/backup/logical/replicaset/examples/restored-standalone.yaml b/docs/guides/mongodb/backup/logical/replicaset/examples/restored-standalone.yaml index ba49736fd5..43d845dba4 100644 --- a/docs/guides/mongodb/backup/logical/replicaset/examples/restored-standalone.yaml +++ b/docs/guides/mongodb/backup/logical/replicaset/examples/restored-standalone.yaml @@ -4,7 +4,7 @@ metadata: name: restored-mongodb namespace: demo spec: - version: "4.2.3" + version: "4.4.26" storageType: Durable storage: storageClassName: "standard" diff --git a/docs/guides/mongodb/backup/logical/replicaset/examples/restoresession-standalone.yaml b/docs/guides/mongodb/backup/logical/replicaset/examples/restoresession-standalone.yaml index f64157d2d4..d22fea850e 100644 --- a/docs/guides/mongodb/backup/logical/replicaset/examples/restoresession-standalone.yaml +++ b/docs/guides/mongodb/backup/logical/replicaset/examples/restoresession-standalone.yaml @@ -5,7 +5,7 @@ metadata: namespace: demo spec: task: - name: mongodb-restore-4.2.3 + name: mongodb-restore-4.4.6 repository: name: gcs-repo-custom target: diff --git a/docs/guides/mongodb/backup/logical/replicaset/examples/standalone-backup.yaml b/docs/guides/mongodb/backup/logical/replicaset/examples/standalone-backup.yaml index 1fed8f4eb0..da807d2839 100644 --- a/docs/guides/mongodb/backup/logical/replicaset/examples/standalone-backup.yaml +++ b/docs/guides/mongodb/backup/logical/replicaset/examples/standalone-backup.yaml @@ -33,7 +33,7 @@ metadata: spec: schedule: "*/5 * * * *" task: - name: mongodb-backup-4.2.3 + name: mongodb-backup-4.4.6 repository: name: gcs-repo-custom target: diff --git a/docs/guides/mongodb/backup/logical/replicaset/index.md b/docs/guides/mongodb/backup/logical/replicaset/index.md index ad7523ca61..842ba6aca3 100644 --- a/docs/guides/mongodb/backup/logical/replicaset/index.md +++ b/docs/guides/mongodb/backup/logical/replicaset/index.md @@ -57,7 +57,7 @@ metadata: name: sample-mgo-rs namespace: demo spec: - version: "4.2.3" + version: "4.4.26" replicas: 3 replicaSet: name: rs0 @@ -85,7 +85,7 @@ Let's check if the database is ready to use, ```console $ kubectl get mg -n demo sample-mgo-rs NAME VERSION STATUS AGE -sample-mgo-rs 4.2.3 Ready 1m +sample-mgo-rs 4.4.26 Ready 1m ``` The database is `Running`. Verify that KubeDB has created a Secret and a Service for this database using the following commands, @@ -126,7 +126,7 @@ kind: AppBinding metadata: annotations: kubectl.kubernetes.io/last-applied-configuration: | - {"apiVersion":"kubedb.com/v1alpha2","kind":"MongoDB","metadata":{"annotations":{},"name":"sample-mgo-rs","namespace":"demo"},"spec":{"replicaSet":{"name":"rs0"},"replicas":3,"storage":{"accessModes":["ReadWriteOnce"],"resources":{"requests":{"storage":"1Gi"}},"storageClassName":"standard"},"terminationPolicy":"WipeOut","version":"4.2.3"}} + {"apiVersion":"kubedb.com/v1alpha2","kind":"MongoDB","metadata":{"annotations":{},"name":"sample-mgo-rs","namespace":"demo"},"spec":{"replicaSet":{"name":"rs0"},"replicas":3,"storage":{"accessModes":["ReadWriteOnce"],"resources":{"requests":{"storage":"1Gi"}},"storageClassName":"standard"},"terminationPolicy":"WipeOut","version":"4.4.26"}} creationTimestamp: "2022-10-26T04:42:05Z" generation: 1 labels: @@ -164,13 +164,13 @@ spec: stash: addon: backupTask: - name: mongodb-backup-4.2.3 + name: mongodb-backup-4.4.6 restoreTask: - name: mongodb-restore-4.2.3 + name: mongodb-restore-4.4.6 secret: name: sample-mgo-rs-auth type: kubedb.com/mongodb - version: 4.2.3 + version: 4.4.26 ``` Stash uses the `AppBinding` crd to connect with the target database. It requires the following two fields to set in AppBinding's `Spec` section. @@ -335,7 +335,7 @@ If everything goes well, the phase of the `BackupConfiguration` should be `Ready ```console $ kubectl get backupconfiguration -n demo NAME TASK SCHEDULE PAUSED PHASE AGE -sample-mgo-rs-backup mongodb-backup-4.2.3 */5 * * * * Ready 11s +sample-mgo-rs-backup mongodb-backup-4.4.6 */5 * * * * Ready 11s ``` **Verify CronJob:** @@ -402,7 +402,7 @@ Now, wait for a moment. Stash will pause the BackupConfiguration. Verify that th ```console $ kubectl get backupconfiguration -n demo sample-mgo-rs-backup NAME TASK SCHEDULE PAUSED PHASE AGE -sample-mgo-rs-backup mongodb-backup-4.2.3 */5 * * * * true Ready 26m +sample-mgo-rs-backup mongodb-backup-4.4.6 */5 * * * * true Ready 26m ``` Notice the `PAUSED` column. Value `true` for this field means that the BackupConfiguration has been paused. @@ -570,7 +570,7 @@ metadata: spec: schedule: "*/5 * * * *" task: - name: mongodb-backup-4.2.3 + name: mongodb-backup-4.4.6 repository: name: gcs-repo-custom target: @@ -616,7 +616,7 @@ metadata: name: restored-mongodb namespace: demo spec: - version: "4.2.3" + version: "4.4.26" storageType: Durable storage: storageClassName: "standard" @@ -640,7 +640,7 @@ metadata: namespace: demo spec: task: - name: mongodb-restore-4.2.3 + name: mongodb-restore-4.4.6 repository: name: gcs-repo-custom target: @@ -658,14 +658,14 @@ mongodb.kubedb.com/restored-mongodb created $ kubectl get mg -n demo restored-mongodb NAME VERSION STATUS AGE -restored-mongodb 4.2.3 Provisioning 56s +restored-mongodb 4.4.26 Provisioning 56s $ kubectl create -f https://github.com/kubedb/docs/raw/{{< param "info.version" >}}/docs/guides/mongodb/backup/logical/replicaset/rexamples/estoresession-standalone.yaml restoresession.stash.appscode.com/sample-mongodb-restore created $ kubectl get mg -n demo restored-mongodb NAME VERSION STATUS AGE -restored-mongodb 4.2.3 Ready 2m +restored-mongodb 4.4.26 Ready 2m ``` Now, exec into the database pod and list available tables, diff --git a/docs/guides/mongodb/backup/logical/sharding/examples/mongodb-sharding.yaml b/docs/guides/mongodb/backup/logical/sharding/examples/mongodb-sharding.yaml index 401ac10901..c4538f6e4f 100644 --- a/docs/guides/mongodb/backup/logical/sharding/examples/mongodb-sharding.yaml +++ b/docs/guides/mongodb/backup/logical/sharding/examples/mongodb-sharding.yaml @@ -4,7 +4,7 @@ metadata: name: sample-mgo-sh namespace: demo spec: - version: 4.2.3 + version: 4.4.26 shardTopology: configServer: replicas: 3 diff --git a/docs/guides/mongodb/backup/logical/sharding/examples/restored-mongodb-sharding.yaml b/docs/guides/mongodb/backup/logical/sharding/examples/restored-mongodb-sharding.yaml index 7905bfa710..a3d78a9ecc 100644 --- a/docs/guides/mongodb/backup/logical/sharding/examples/restored-mongodb-sharding.yaml +++ b/docs/guides/mongodb/backup/logical/sharding/examples/restored-mongodb-sharding.yaml @@ -4,7 +4,7 @@ metadata: name: restored-mgo-sh namespace: demo spec: - version: 4.2.3 + version: 4.4.26 shardTopology: configServer: replicas: 3 diff --git a/docs/guides/mongodb/backup/logical/sharding/examples/restored-standalone.yaml b/docs/guides/mongodb/backup/logical/sharding/examples/restored-standalone.yaml index ba49736fd5..43d845dba4 100644 --- a/docs/guides/mongodb/backup/logical/sharding/examples/restored-standalone.yaml +++ b/docs/guides/mongodb/backup/logical/sharding/examples/restored-standalone.yaml @@ -4,7 +4,7 @@ metadata: name: restored-mongodb namespace: demo spec: - version: "4.2.3" + version: "4.4.26" storageType: Durable storage: storageClassName: "standard" diff --git a/docs/guides/mongodb/backup/logical/sharding/examples/restoresession-standalone.yaml b/docs/guides/mongodb/backup/logical/sharding/examples/restoresession-standalone.yaml index f64157d2d4..d22fea850e 100644 --- a/docs/guides/mongodb/backup/logical/sharding/examples/restoresession-standalone.yaml +++ b/docs/guides/mongodb/backup/logical/sharding/examples/restoresession-standalone.yaml @@ -5,7 +5,7 @@ metadata: namespace: demo spec: task: - name: mongodb-restore-4.2.3 + name: mongodb-restore-4.4.6 repository: name: gcs-repo-custom target: diff --git a/docs/guides/mongodb/backup/logical/sharding/examples/standalone-backup.yaml b/docs/guides/mongodb/backup/logical/sharding/examples/standalone-backup.yaml index 6683daaf68..4a9aecf3e4 100644 --- a/docs/guides/mongodb/backup/logical/sharding/examples/standalone-backup.yaml +++ b/docs/guides/mongodb/backup/logical/sharding/examples/standalone-backup.yaml @@ -33,7 +33,7 @@ metadata: spec: schedule: "*/5 * * * *" task: - name: mongodb-backup-4.2.3 + name: mongodb-backup-4.4.6 repository: name: gcs-repo-custom target: diff --git a/docs/guides/mongodb/backup/logical/sharding/index.md b/docs/guides/mongodb/backup/logical/sharding/index.md index 151d7225c7..22f8079665 100644 --- a/docs/guides/mongodb/backup/logical/sharding/index.md +++ b/docs/guides/mongodb/backup/logical/sharding/index.md @@ -57,7 +57,7 @@ metadata: name: sample-mgo-sh namespace: demo spec: - version: 4.2.3 + version: 4.4.26 shardTopology: configServer: replicas: 3 @@ -93,7 +93,7 @@ Let's check if the database is ready to use, ```console $ kubectl get mg -n demo sample-mgo-sh NAME VERSION STATUS AGE -sample-mgo-sh 4.2.3 Ready 35m +sample-mgo-sh 4.4.26 Ready 35m ``` The database is `Ready`. Verify that KubeDB has created a Secret and a Service for this database using the following commands, @@ -137,7 +137,7 @@ kind: AppBinding metadata: annotations: kubectl.kubernetes.io/last-applied-configuration: | - {"apiVersion":"kubedb.com/v1alpha2","kind":"MongoDB","metadata":{"annotations":{},"name":"sample-mgo-sh","namespace":"demo"},"spec":{"shardTopology":{"configServer":{"replicas":3,"storage":{"resources":{"requests":{"storage":"1Gi"}},"storageClassName":"standard"}},"mongos":{"replicas":2},"shard":{"replicas":3,"shards":3,"storage":{"resources":{"requests":{"storage":"1Gi"}},"storageClassName":"standard"}}},"terminationPolicy":"WipeOut","version":"4.2.3"}} + {"apiVersion":"kubedb.com/v1alpha2","kind":"MongoDB","metadata":{"annotations":{},"name":"sample-mgo-sh","namespace":"demo"},"spec":{"shardTopology":{"configServer":{"replicas":3,"storage":{"resources":{"requests":{"storage":"1Gi"}},"storageClassName":"standard"}},"mongos":{"replicas":2},"shard":{"replicas":3,"shards":3,"storage":{"resources":{"requests":{"storage":"1Gi"}},"storageClassName":"standard"}}},"terminationPolicy":"WipeOut","version":"4.4.26"}} creationTimestamp: "2022-10-26T05:11:20Z" generation: 1 labels: @@ -178,13 +178,13 @@ spec: stash: addon: backupTask: - name: mongodb-backup-4.2.3 + name: mongodb-backup-4.4.6 restoreTask: - name: mongodb-restore-4.2.3 + name: mongodb-restore-4.4.6 secret: name: sample-mgo-sh-auth type: kubedb.com/mongodb - version: 4.2.3 + version: 4.4.26 ``` Stash uses the `AppBinding` crd to connect with the target database. It requires the following two fields to set in AppBinding's `Spec` section. @@ -346,7 +346,7 @@ If everything goes well, the phase of the `BackupConfiguration` should be `Ready ```console $ kubectl get backupconfiguration -n demo NAME TASK SCHEDULE PAUSED PHASE AGE -sample-mgo-sh-backup mongodb-backup-4.2.3 */5 * * * * Ready 11s +sample-mgo-sh-backup mongodb-backup-4.4.6 */5 * * * * Ready 11s ``` **Verify CronJob:** @@ -415,7 +415,7 @@ Now, wait for a moment. Stash will pause the BackupConfiguration. Verify that th ```console $ kubectl get backupconfiguration -n demo sample-mgo-sh-backup NAME TASK SCHEDULE PAUSED PHASE AGE -sample-mgo-sh-backup mongodb-restore-4.2.3 */5 * * * * true Ready 26m +sample-mgo-sh-backup mongodb-restore-4.4.6 */5 * * * * true Ready 26m ``` Notice the `PAUSED` column. Value `true` for this field means that the BackupConfiguration has been paused. @@ -579,7 +579,7 @@ metadata: spec: schedule: "*/5 * * * *" task: - name: mongodb-backup-4.2.3 + name: mongodb-backup-4.4.6 repository: name: gcs-repo-custom target: @@ -625,7 +625,7 @@ metadata: name: restored-mongodb namespace: demo spec: - version: "4.2.3" + version: "4.4.26" storageType: Durable storage: storageClassName: "standard" @@ -649,7 +649,7 @@ metadata: namespace: demo spec: task: - name: mongodb-restore-4.2.3 + name: mongodb-restore-4.4.6 repository: name: gcs-repo-custom target: @@ -667,14 +667,14 @@ mongodb.kubedb.com/restored-mongodb created $ kubectl get mg -n demo restored-mongodb NAME VERSION STATUS AGE -restored-mongodb 4.2.3 Provisioning 56s +restored-mongodb 4.4.26 Provisioning 56s $ kubectl create -f https://github.com/kubedb/docs/raw/{{< param "info.version" >}}/docs/guides/mongodb/backup/logical/sharding/examples/restoresession-standalone.yaml restoresession.stash.appscode.com/sample-mongodb-restore created $ kubectl get mg -n demo restored-mongodb NAME VERSION STATUS AGE -restored-mongodb 4.2.3 Ready 56s +restored-mongodb 4.4.26 Ready 56s ``` Now, exec into the database pod and list available tables, diff --git a/docs/guides/mongodb/backup/logical/standalone/examples/mongodb.yaml b/docs/guides/mongodb/backup/logical/standalone/examples/mongodb.yaml index bc205087e1..3515b48a2e 100644 --- a/docs/guides/mongodb/backup/logical/standalone/examples/mongodb.yaml +++ b/docs/guides/mongodb/backup/logical/standalone/examples/mongodb.yaml @@ -4,7 +4,7 @@ metadata: name: sample-mongodb namespace: demo spec: - version: "4.2.3" + version: "4.4.26" storageType: Durable storage: storageClassName: "standard" diff --git a/docs/guides/mongodb/backup/logical/standalone/examples/restored-mongodb.yaml b/docs/guides/mongodb/backup/logical/standalone/examples/restored-mongodb.yaml index ba49736fd5..43d845dba4 100644 --- a/docs/guides/mongodb/backup/logical/standalone/examples/restored-mongodb.yaml +++ b/docs/guides/mongodb/backup/logical/standalone/examples/restored-mongodb.yaml @@ -4,7 +4,7 @@ metadata: name: restored-mongodb namespace: demo spec: - version: "4.2.3" + version: "4.4.26" storageType: Durable storage: storageClassName: "standard" diff --git a/docs/guides/mongodb/backup/logical/standalone/index.md b/docs/guides/mongodb/backup/logical/standalone/index.md index 588a1d149e..42df2603cc 100644 --- a/docs/guides/mongodb/backup/logical/standalone/index.md +++ b/docs/guides/mongodb/backup/logical/standalone/index.md @@ -57,7 +57,7 @@ metadata: name: sample-mongodb namespace: demo spec: - version: "4.2.3" + version: "4.4.26" storageType: Durable storage: storageClassName: "standard" @@ -83,7 +83,7 @@ Let's check if the database is ready to use, ```console $ kubectl get mg -n demo sample-mongodb NAME VERSION STATUS AGE -sample-mongodb 4.2.3 Ready 2m9s +sample-mongodb 4.4.26 Ready 2m9s ``` The database is `Ready`. Verify that KubeDB has created a Secret and a Service for this database using the following commands, @@ -123,7 +123,7 @@ kind: AppBinding metadata: annotations: kubectl.kubernetes.io/last-applied-configuration: | - {"apiVersion":"kubedb.com/v1alpha2","kind":"MongoDB","metadata":{"annotations":{},"name":"sample-mongodb","namespace":"demo"},"spec":{"storage":{"accessModes":["ReadWriteOnce"],"resources":{"requests":{"storage":"1Gi"}},"storageClassName":"standard"},"storageType":"Durable","terminationPolicy":"WipeOut","version":"4.2.3"}} + {"apiVersion":"kubedb.com/v1alpha2","kind":"MongoDB","metadata":{"annotations":{},"name":"sample-mongodb","namespace":"demo"},"spec":{"storage":{"accessModes":["ReadWriteOnce"],"resources":{"requests":{"storage":"1Gi"}},"storageClassName":"standard"},"storageType":"Durable","terminationPolicy":"WipeOut","version":"4.4.26"}} creationTimestamp: "2022-10-26T05:13:07Z" generation: 1 labels: @@ -159,13 +159,13 @@ spec: stash: addon: backupTask: - name: mongodb-backup-4.2.3 + name: mongodb-backup-4.4.6 restoreTask: - name: mongodb-restore-4.2.3 + name: mongodb-restore-4.4.6 secret: name: sample-mongodb-auth type: kubedb.com/mongodb - version: 4.2.3 + version: 4.4.26 ``` Stash uses the `AppBinding` crd to connect with the target database. It requires the following two fields to set in AppBinding's `Spec` section. @@ -323,7 +323,7 @@ If everything goes well, the phase of the `BackupConfiguration` should be `Ready ```console $ kubectl get backupconfiguration -n demo NAME TASK SCHEDULE PAUSED PHASE AGE -sample-mongodb-backup mongodb-backup-4.2.3 */5 * * * * Ready 11s +sample-mongodb-backup mongodb-backup-4.4.6 */5 * * * * Ready 11s ``` **Verify CronJob:** @@ -391,7 +391,7 @@ Now, wait for a moment. Stash will pause the BackupConfiguration. Verify that th ```console $ kubectl get backupconfiguration -n demo sample-mongodb-backup NAME TASK SCHEDULE PAUSED PHASE AGE -sample-mongodb-backup mongodb-backup-4.2.3 */5 * * * * true Ready 26m +sample-mongodb-backup mongodb-backup-4.4.6 */5 * * * * true Ready 26m ``` Notice the `PAUSED` column. Value `true` for this field means that the BackupConfiguration has been paused. diff --git a/docs/guides/mongodb/clustering/replicaset.md b/docs/guides/mongodb/clustering/replicaset.md index 153dca08e6..1e117f8b0d 100644 --- a/docs/guides/mongodb/clustering/replicaset.md +++ b/docs/guides/mongodb/clustering/replicaset.md @@ -48,7 +48,7 @@ metadata: name: mgo-replicaset namespace: demo spec: - version: "4.2.3" + version: "4.4.26" replicas: 3 replicaSet: name: rs0 @@ -146,7 +146,7 @@ Auth Secret: AppBinding: Metadata: Annotations: - kubectl.kubernetes.io/last-applied-configuration: {"apiVersion":"kubedb.com/v1alpha2","kind":"MongoDB","metadata":{"annotations":{},"name":"mgo-replicaset","namespace":"demo"},"spec":{"replicaSet":{"name":"rs0"},"replicas":3,"storage":{"accessModes":["ReadWriteOnce"],"resources":{"requests":{"storage":"1Gi"}},"storageClassName":"standard"},"version":"4.2.3"}} + kubectl.kubernetes.io/last-applied-configuration: {"apiVersion":"kubedb.com/v1alpha2","kind":"MongoDB","metadata":{"annotations":{},"name":"mgo-replicaset","namespace":"demo"},"spec":{"replicaSet":{"name":"rs0"},"replicas":3,"storage":{"accessModes":["ReadWriteOnce"],"resources":{"requests":{"storage":"1Gi"}},"storageClassName":"standard"},"version":"4.4.26"}} Creation Timestamp: 2021-02-10T05:07:10Z Labels: @@ -170,7 +170,7 @@ AppBinding: Secret: Name: mgo-replicaset-auth Type: kubedb.com/mongodb - Version: 4.2.3 + Version: 4.4.26 Events: Type Reason Age From Message @@ -227,7 +227,7 @@ kind: MongoDB metadata: annotations: kubectl.kubernetes.io/last-applied-configuration: | - {"apiVersion":"kubedb.com/v1alpha2","kind":"MongoDB","metadata":{"annotations":{},"name":"mgo-replicaset","namespace":"demo"},"spec":{"replicaSet":{"name":"rs0"},"replicas":3,"storage":{"accessModes":["ReadWriteOnce"],"resources":{"requests":{"storage":"1Gi"}},"storageClassName":"standard"},"version":"4.2.3"}} + {"apiVersion":"kubedb.com/v1alpha2","kind":"MongoDB","metadata":{"annotations":{},"name":"mgo-replicaset","namespace":"demo"},"spec":{"replicaSet":{"name":"rs0"},"replicas":3,"storage":{"accessModes":["ReadWriteOnce"],"resources":{"requests":{"storage":"1Gi"}},"storageClassName":"standard"},"version":"4.4.26"}} creationTimestamp: "2021-02-11T04:29:29Z" finalizers: - kubedb.com @@ -364,7 +364,7 @@ spec: storageEngine: wiredTiger storageType: Durable terminationPolicy: Delete - version: 4.2.3 + version: 4.4.26 status: conditions: - lastTransitionTime: "2021-02-11T04:29:29Z" @@ -419,9 +419,9 @@ $ kubectl get secrets -n demo mgo-replicaset-auth -o jsonpath='{.data.\password} $ kubectl exec -it mgo-replicaset-0 -n demo bash mongodb@mgo-replicaset-0:/$ mongo admin -u root -p 5O4R2ze2bWXcWsdP -MongoDB shell version v4.2.3 +MongoDB shell version v4.4.26 connecting to: mongodb://127.0.0.1:27017/admin -MongoDB server version: 4.2.3 +MongoDB server version: 4.4.26 Welcome to the MongoDB shell. rs0:PRIMARY> > rs.isMaster().primary @@ -470,9 +470,9 @@ We will exec in `mgo-replicaset-1`(which is secondary member right now) to check ```bash $ kubectl exec -it mgo-replicaset-1 -n demo bash mongodb@mgo-replicaset-1:/$ mongo admin -u root -p 5O4R2ze2bWXcWsdP -MongoDB shell version v4.2.3 +MongoDB shell version v4.4.26 connecting to: mongodb://127.0.0.1:27017/admin -MongoDB server version: 4.2.3 +MongoDB server version: 4.4.26 Welcome to the MongoDB shell. rs0:SECONDARY> rs.slaveOk() @@ -538,9 +538,9 @@ Now verify the automatic failover, Let's exec in `mgo-replicaset-1` pod, ```bash $ kubectl exec -it mgo-replicaset-1 -n demo bash mongodb@mgo-replicaset-1:/$ mongo admin -u root -p 5O4R2ze2bWXcWsdP -MongoDB shell version v4.2.3 +MongoDB shell version v4.4.26 connecting to: mongodb://127.0.0.1:27017/admin -MongoDB server version: 4.2.3 +MongoDB server version: 4.4.26 Welcome to the MongoDB shell. rs0:SECONDARY> rs.isMaster().primary @@ -606,7 +606,7 @@ Now, you can run the following command to get all mongodb resources in demo name ```bash $ kubectl get mg,sts,svc,secret,pvc -n demo NAME VERSION STATUS AGE -mongodb.kubedb.com/mgo-replicaset 4.2.3 Halted 9m43s +mongodb.kubedb.com/mgo-replicaset 4.4.26 Halted 9m43s NAME TYPE DATA AGE secret/default-token-x2zcl kubernetes.io/service-account-token 3 47h @@ -634,7 +634,7 @@ When the database is resumed successfully, you can see the database Status is se ```bash $ kubectl get mg -n demo NAME VERSION STATUS AGE -mgo-replicaset 4.2.3 Ready 6m27s +mgo-replicaset 4.4.26 Ready 6m27s ``` Now, If you again exec into the primary `pod` and look for previous data, you will see that, all the data persists. diff --git a/docs/guides/mongodb/clustering/sharding.md b/docs/guides/mongodb/clustering/sharding.md index 6f224fd348..5487513d27 100644 --- a/docs/guides/mongodb/clustering/sharding.md +++ b/docs/guides/mongodb/clustering/sharding.md @@ -48,7 +48,7 @@ metadata: name: mongo-sh namespace: demo spec: - version: 4.2.3 + version: 4.4.26 shardTopology: configServer: replicas: 3 @@ -104,7 +104,7 @@ MongoDB `mongo-sh` state, ```bash $ kubectl get mg -n demo NAME VERSION STATUS AGE -mongo-sh 4.2.3 Ready 9m41s +mongo-sh 4.4.26 Ready 9m41s ``` All the types of nodes `Shard`, `ConfigServer` & `Mongos` are deployed as statefulset. @@ -168,7 +168,7 @@ kind: MongoDB metadata: annotations: kubectl.kubernetes.io/last-applied-configuration: | - {"apiVersion":"kubedb.com/v1alpha2","kind":"MongoDB","metadata":{"annotations":{},"name":"mongo-sh","namespace":"demo"},"spec":{"shardTopology":{"configServer":{"replicas":3,"storage":{"resources":{"requests":{"storage":"1Gi"}},"storageClassName":"standard"}},"mongos":{"replicas":2},"shard":{"replicas":3,"shards":2,"storage":{"resources":{"requests":{"storage":"1Gi"}},"storageClassName":"standard"}}},"version":"4.2.3"}} + {"apiVersion":"kubedb.com/v1alpha2","kind":"MongoDB","metadata":{"annotations":{},"name":"mongo-sh","namespace":"demo"},"spec":{"shardTopology":{"configServer":{"replicas":3,"storage":{"resources":{"requests":{"storage":"1Gi"}},"storageClassName":"standard"}},"mongos":{"replicas":2},"shard":{"replicas":3,"shards":2,"storage":{"resources":{"requests":{"storage":"1Gi"}},"storageClassName":"standard"}}},"version":"4.4.26"}} creationTimestamp: "2021-02-10T12:57:03Z" finalizers: - kubedb.com @@ -464,7 +464,7 @@ spec: storageEngine: wiredTiger storageType: Durable terminationPolicy: Delete - version: 4.2.3 + version: 4.4.26 status: conditions: - lastTransitionTime: "2021-02-10T12:57:03Z" @@ -538,10 +538,10 @@ mongo-sh-mongos-1 1/1 Running 0 49m $ kubectl exec -it mongo-sh-mongos-0 -n demo bash mongodb@mongo-sh-mongos-0:/$ mongo admin -u root -p 7QiqLcuSCmZ8PU5a -MongoDB shell version v4.2.3 +MongoDB shell version v4.4.26 connecting to: mongodb://127.0.0.1:27017/admin?gssapiServiceName=mongodb Implicit session: session { "id" : UUID("8b7abf57-09e4-4e30-b4a0-a37ebf065e8f") } -MongoDB server version: 4.2.3 +MongoDB server version: 4.4.26 Welcome to the MongoDB shell. For interactive help, type "help". For more comprehensive documentation, see @@ -593,7 +593,7 @@ mongos> sh.status() { "_id" : "shard0", "host" : "shard0/mongo-sh-shard0-0.mongo-sh-shard0-pods.demo.svc.cluster.local:27017,mongo-sh-shard0-1.mongo-sh-shard0-pods.demo.svc.cluster.local:27017,mongo-sh-shard0-2.mongo-sh-shard0-pods.demo.svc.cluster.local:27017", "state" : 1 } { "_id" : "shard1", "host" : "shard1/mongo-sh-shard1-0.mongo-sh-shard1-pods.demo.svc.cluster.local:27017,mongo-sh-shard1-1.mongo-sh-shard1-pods.demo.svc.cluster.local:27017,mongo-sh-shard1-2.mongo-sh-shard1-pods.demo.svc.cluster.local:27017", "state" : 1 } active mongoses: - "4.2.3" : 2 + "4.4.26" : 2 autosplit: Currently enabled: yes balancer: @@ -676,7 +676,7 @@ mongos> sh.status(); { "_id" : "shard0", "host" : "shard0/mongo-sh-shard0-0.mongo-sh-shard0-pods.demo.svc.cluster.local:27017,mongo-sh-shard0-1.mongo-sh-shard0-pods.demo.svc.cluster.local:27017,mongo-sh-shard0-2.mongo-sh-shard0-pods.demo.svc.cluster.local:27017", "state" : 1 } { "_id" : "shard1", "host" : "shard1/mongo-sh-shard1-0.mongo-sh-shard1-pods.demo.svc.cluster.local:27017,mongo-sh-shard1-1.mongo-sh-shard1-pods.demo.svc.cluster.local:27017,mongo-sh-shard1-2.mongo-sh-shard1-pods.demo.svc.cluster.local:27017", "state" : 1 } active mongoses: - "4.2.3" : 2 + "4.4.26" : 2 autosplit: Currently enabled: yes balancer: @@ -737,7 +737,7 @@ mongos> sh.status() { "_id" : "shard0", "host" : "shard0/mongo-sh-shard0-0.mongo-sh-shard0-pods.demo.svc.cluster.local:27017,mongo-sh-shard0-1.mongo-sh-shard0-pods.demo.svc.cluster.local:27017,mongo-sh-shard0-2.mongo-sh-shard0-pods.demo.svc.cluster.local:27017", "state" : 1 } { "_id" : "shard1", "host" : "shard1/mongo-sh-shard1-0.mongo-sh-shard1-pods.demo.svc.cluster.local:27017,mongo-sh-shard1-1.mongo-sh-shard1-pods.demo.svc.cluster.local:27017,mongo-sh-shard1-2.mongo-sh-shard1-pods.demo.svc.cluster.local:27017", "state" : 1 } active mongoses: - "4.2.3" : 2 + "4.4.26" : 2 autosplit: Currently enabled: yes balancer: @@ -795,7 +795,7 @@ Now, you can run the following command to get all mongodb resources in demo name ```bash $ kubectl get mg,sts,svc,secret,pvc -n demo NAME VERSION STATUS AGE -mongodb.kubedb.com/mongo-sh 4.2.3 Halted 74m +mongodb.kubedb.com/mongo-sh 4.4.26 Halted 74m NAME TYPE DATA AGE secret/default-token-x2zcl kubernetes.io/service-account-token 3 32h @@ -830,7 +830,7 @@ When the database is resumed successfully, you can see the database Status is se ```bash $ kubectl get mg -n demo NAME VERSION STATUS AGE -mongo-sh 4.2.3 Ready 6m27s +mongo-sh 4.4.26 Ready 6m27s ``` Now, If you again exec into `pod` and look for previous data, you will see that, all the data persists. @@ -865,7 +865,7 @@ mongos> sh.status() { "_id" : "shard0", "host" : "shard0/mongo-sh-shard0-0.mongo-sh-shard0-pods.demo.svc.cluster.local:27017,mongo-sh-shard0-1.mongo-sh-shard0-pods.demo.svc.cluster.local:27017,mongo-sh-shard0-2.mongo-sh-shard0-pods.demo.svc.cluster.local:27017", "state" : 1 } { "_id" : "shard1", "host" : "shard1/mongo-sh-shard1-0.mongo-sh-shard1-pods.demo.svc.cluster.local:27017,mongo-sh-shard1-1.mongo-sh-shard1-pods.demo.svc.cluster.local:27017,mongo-sh-shard1-2.mongo-sh-shard1-pods.demo.svc.cluster.local:27017", "state" : 1 } active mongoses: - "4.2.3" : 2 + "4.4.26" : 2 autosplit: Currently enabled: yes balancer: diff --git a/docs/guides/mongodb/clustering/standalone.md b/docs/guides/mongodb/clustering/standalone.md index 3fa3d12246..493c93a0ef 100644 --- a/docs/guides/mongodb/clustering/standalone.md +++ b/docs/guides/mongodb/clustering/standalone.md @@ -46,7 +46,7 @@ metadata: name: mg-alone namespace: demo spec: - version: "4.2.3" + version: "4.4.26" podTemplate: spec: resources: @@ -143,7 +143,7 @@ Auth Secret: AppBinding: Metadata: Annotations: - kubectl.kubernetes.io/last-applied-configuration: {"apiVersion":"kubedb.com/v1alpha2","kind":"MongoDB","metadata":{"annotations":{},"name":"mg-alone","namespace":"demo"},"spec":{"podTemplate":{"spec":{"resources":{"requests":{"cpu":"300m","memory":"400Mi"}}}},"storage":{"resources":{"requests":{"storage":"500Mi"}},"storageClassName":"standard"},"terminationPolicy":"WipeOut","version":"4.2.3"}} + kubectl.kubernetes.io/last-applied-configuration: {"apiVersion":"kubedb.com/v1alpha2","kind":"MongoDB","metadata":{"annotations":{},"name":"mg-alone","namespace":"demo"},"spec":{"podTemplate":{"spec":{"resources":{"requests":{"cpu":"300m","memory":"400Mi"}}}},"storage":{"resources":{"requests":{"storage":"500Mi"}},"storageClassName":"standard"},"terminationPolicy":"WipeOut","version":"4.4.26"}} Creation Timestamp: 2022-11-04T04:30:14Z Labels: @@ -165,13 +165,13 @@ AppBinding: Stash: Addon: Backup Task: - Name: mongodb-backup-4.2.3 + Name: mongodb-backup-4.4.6 Restore Task: - Name: mongodb-restore-4.2.3 + Name: mongodb-restore-4.4.6 Secret: Name: mg-alone-auth Type: kubedb.com/mongodb - Version: 4.2.3 + Version: 4.4.26 Events: Type Reason Age From Message @@ -217,7 +217,7 @@ kind: MongoDB metadata: annotations: kubectl.kubernetes.io/last-applied-configuration: | - {"apiVersion":"kubedb.com/v1alpha2","kind":"MongoDB","metadata":{"annotations":{},"name":"mg-alone","namespace":"demo"},"spec":{"podTemplate":{"spec":{"resources":{"requests":{"cpu":"300m","memory":"400Mi"}}}},"storage":{"resources":{"requests":{"storage":"500Mi"}},"storageClassName":"standard"},"terminationPolicy":"WipeOut","version":"4.2.3"}} + {"apiVersion":"kubedb.com/v1alpha2","kind":"MongoDB","metadata":{"annotations":{},"name":"mg-alone","namespace":"demo"},"spec":{"podTemplate":{"spec":{"resources":{"requests":{"cpu":"300m","memory":"400Mi"}}}},"storage":{"resources":{"requests":{"storage":"500Mi"}},"storageClassName":"standard"},"terminationPolicy":"WipeOut","version":"4.4.26"}} creationTimestamp: "2022-11-04T04:30:07Z" finalizers: - kubedb.com @@ -309,7 +309,7 @@ spec: storageEngine: wiredTiger storageType: Durable terminationPolicy: WipeOut - version: 4.2.3 + version: 4.4.26 status: conditions: - lastTransitionTime: "2022-11-04T04:30:07Z" @@ -365,9 +365,9 @@ $ kubectl get secrets -n demo mg-alone-auth -o jsonpath='{.data.\password}' | ba $ kubectl exec -it mg-alone-0 -n demo bash mongodb@mg-alone-0:/$ mongo admin -u root -p 5O4R2ze2bWXcWsdP -MongoDB shell version v4.2.3 +MongoDB shell version v4.4.26 connecting to: mongodb://127.0.0.1:27017/admin -MongoDB server version: 4.2.3 +MongoDB server version: 4.4.26 Welcome to the MongoDB shell. > rs.isMaster() @@ -455,7 +455,7 @@ Now, you can run the following command to get all mongodb resources in demo name ```bash $ kubectl get mg,sts,svc,secret,pvc -n demo NAME VERSION STATUS AGE -mongodb.kubedb.com/mg-alone 4.2.3 Halted 2m4s +mongodb.kubedb.com/mg-alone 4.4.26 Halted 2m4s NAME TYPE DATA AGE secret/mg-alone-auth kubernetes.io/basic-auth 2 2m4s @@ -481,7 +481,7 @@ When the database is resumed successfully, you can see the database Status is se ```bash $ kubectl get mg -n demo NAME VERSION STATUS AGE -mg-alone 4.2.3 Ready 6m27s +mg-alone 4.4.26 Ready 6m27s ``` Now, If you again exec into the primary `pod` and look for previous data, you will see that, all the data persists. diff --git a/docs/guides/mongodb/concepts/appbinding.md b/docs/guides/mongodb/concepts/appbinding.md index c054235057..f1f2d5afef 100644 --- a/docs/guides/mongodb/concepts/appbinding.md +++ b/docs/guides/mongodb/concepts/appbinding.md @@ -34,7 +34,7 @@ kind: AppBinding metadata: annotations: kubectl.kubernetes.io/last-applied-configuration: | - {"apiVersion":"kubedb.com/v1alpha2","kind":"MongoDB","metadata":{"annotations":{},"name":"sample-mgo-rs","namespace":"demo"},"spec":{"replicaSet":{"name":"rs0"},"replicas":3,"storage":{"accessModes":["ReadWriteOnce"],"resources":{"requests":{"storage":"1Gi"}},"storageClassName":"standard"},"terminationPolicy":"WipeOut","version":"4.2.3"}} + {"apiVersion":"kubedb.com/v1alpha2","kind":"MongoDB","metadata":{"annotations":{},"name":"sample-mgo-rs","namespace":"demo"},"spec":{"replicaSet":{"name":"rs0"},"replicas":3,"storage":{"accessModes":["ReadWriteOnce"],"resources":{"requests":{"storage":"1Gi"}},"storageClassName":"standard"},"terminationPolicy":"WipeOut","version":"4.4.26"}} creationTimestamp: "2022-10-26T04:42:05Z" generation: 1 labels: @@ -72,13 +72,13 @@ spec: stash: addon: backupTask: - name: mongodb-backup-4.2.3 + name: mongodb-backup-4.4.6 restoreTask: - name: mongodb-restore-4.2.3 + name: mongodb-restore-4.4.6 secret: name: sample-mgo-rs-auth type: kubedb.com/mongodb - version: 4.2.3 + version: 4.4.26 ``` Here, we are going to describe the sections of an `AppBinding` crd. diff --git a/docs/guides/mongodb/concepts/catalog.md b/docs/guides/mongodb/concepts/catalog.md index 75df6a95ae..a95ab7dbfb 100644 --- a/docs/guides/mongodb/concepts/catalog.md +++ b/docs/guides/mongodb/concepts/catalog.md @@ -30,12 +30,12 @@ As with all other Kubernetes objects, a MongoDBVersion needs `apiVersion`, `kind apiVersion: catalog.kubedb.com/v1alpha1 kind: MongoDBVersion metadata: - name: "4.2.3" + name: "4.4.26" labels: app: kubedb spec: db: - image: mongo:4.2.3 + image: mongo:4.4.26 distribution: Official exporter: image: kubedb/mongodb_exporter:v0.32.0 @@ -48,13 +48,13 @@ spec: stash: addon: backupTask: - name: mongodb-backup-4.2.3 + name: mongodb-backup-4.4.6 restoreTask: - name: mongodb-restore-4.2.3 + name: mongodb-restore-4.4.6 updateConstraints: allowlist: - '>= 4.4.0, < 5.0.0' - version: 4.2.3 + version: 4.4.26 ``` ### metadata.name diff --git a/docs/guides/mongodb/concepts/mongodb.md b/docs/guides/mongodb/concepts/mongodb.md index 72f912da04..6ca52b80a3 100644 --- a/docs/guides/mongodb/concepts/mongodb.md +++ b/docs/guides/mongodb/concepts/mongodb.md @@ -31,7 +31,7 @@ metadata: spec: autoOps: disabled: true - version: "4.2.3" + version: "4.4.26" replicas: 3 authSecret: name: mgo1-auth @@ -184,10 +184,10 @@ AutoOps is an optional field to control the generation of versionUpdate & TLS-re `spec.version` is a required field specifying the name of the [MongoDBVersion](/docs/guides/mongodb/concepts/catalog.md) crd where the docker images are specified. Currently, when you install KubeDB, it creates the following `MongoDBVersion` resources, - `3.4.17-v1`, `3.4.22-v1` -- `3.6.13-v1`, `3.6.8-v1`, -- `4.0.3-v1`, `4.0.5-v3`, `4.0.11-v1`, -- `4.1.4-v1`, `4.1.7-v3`, `4.1.13-v1` -- `4.2.3`, `4.4.6` +- `3.6.13-v1`, `4.4.26`, +- `4.0.3-v1`, `4.4.26`, `4.0.11-v1`, +- `4.1.4-v1`, `4.1.7-v3`, `4.4.26` +- `4.4.26`, `4.4.26` - `5.0.2`, `5.0.3` - `percona-3.6.18` - `percona-4.0.10`, `percona-4.2.7`, `percona-4.4.10` @@ -428,7 +428,7 @@ metadata: name: mgo1 namespace: demo spec: - version: 4.2.3 + version: 4.4.26 init: script: configMap: diff --git a/docs/guides/mongodb/concepts/opsrequest.md b/docs/guides/mongodb/concepts/opsrequest.md index ef48cbe799..7a9c4bf768 100644 --- a/docs/guides/mongodb/concepts/opsrequest.md +++ b/docs/guides/mongodb/concepts/opsrequest.md @@ -39,7 +39,7 @@ spec: databaseRef: name: mg-standalone updateVersion: - targetVersion: 4.0.5-v3 + targetVersion: 4.4.26 status: conditions: - lastTransitionTime: "2020-08-25T18:22:38Z" diff --git a/docs/guides/mongodb/configuration/using-config-file.md b/docs/guides/mongodb/configuration/using-config-file.md index ae7ad35dd6..704e4c8728 100644 --- a/docs/guides/mongodb/configuration/using-config-file.md +++ b/docs/guides/mongodb/configuration/using-config-file.md @@ -94,7 +94,7 @@ metadata: name: mgo-custom-config namespace: demo spec: - version: "4.2.3" + version: "4.4.26" storageType: Durable storage: storageClassName: "standard" diff --git a/docs/guides/mongodb/configuration/using-podtemplate.md b/docs/guides/mongodb/configuration/using-podtemplate.md index 4146cf1127..501df990a0 100644 --- a/docs/guides/mongodb/configuration/using-podtemplate.md +++ b/docs/guides/mongodb/configuration/using-podtemplate.md @@ -76,7 +76,7 @@ metadata: name: mgo-misc-config namespace: demo spec: - version: "4.2.3" + version: "4.4.26" storageType: "Durable" storage: storageClassName: "standard" diff --git a/docs/guides/mongodb/custom-rbac/using-custom-rbac.md b/docs/guides/mongodb/custom-rbac/using-custom-rbac.md index 8afedbfba7..f6099419ac 100644 --- a/docs/guides/mongodb/custom-rbac/using-custom-rbac.md +++ b/docs/guides/mongodb/custom-rbac/using-custom-rbac.md @@ -142,7 +142,7 @@ metadata: name: quick-mongodb namespace: demo spec: - version: "4.2.3" + version: "4.4.26" storageType: Durable podTemplate: spec: @@ -206,7 +206,7 @@ metadata: name: minute-mongodb namespace: demo spec: - version: "4.2.3" + version: "4.4.26" podTemplate: spec: serviceAccountName: my-custom-serviceaccount diff --git a/docs/guides/mongodb/initialization/using-script.md b/docs/guides/mongodb/initialization/using-script.md index f66f3e9533..9b26456257 100644 --- a/docs/guides/mongodb/initialization/using-script.md +++ b/docs/guides/mongodb/initialization/using-script.md @@ -60,7 +60,7 @@ metadata: name: mgo-init-script namespace: demo spec: - version: "4.2.3" + version: "4.4.26" storage: storageClassName: "standard" accessModes: @@ -162,7 +162,7 @@ Init: AppBinding: Metadata: Annotations: - kubectl.kubernetes.io/last-applied-configuration: {"apiVersion":"kubedb.com/v1alpha2","kind":"MongoDB","metadata":{"annotations":{},"name":"mgo-init-script","namespace":"demo"},"spec":{"init":{"script":{"configMap":{"name":"mg-init-script"}}},"storage":{"accessModes":["ReadWriteOnce"],"resources":{"requests":{"storage":"1Gi"}},"storageClassName":"standard"},"version":"4.2.3"}} + kubectl.kubernetes.io/last-applied-configuration: {"apiVersion":"kubedb.com/v1alpha2","kind":"MongoDB","metadata":{"annotations":{},"name":"mgo-init-script","namespace":"demo"},"spec":{"init":{"script":{"configMap":{"name":"mg-init-script"}}},"storage":{"accessModes":["ReadWriteOnce"],"resources":{"requests":{"storage":"1Gi"}},"storageClassName":"standard"},"version":"4.4.26"}} Creation Timestamp: 2021-02-11T04:58:42Z Labels: @@ -181,7 +181,7 @@ AppBinding: Secret: Name: mgo-init-script-auth Type: kubedb.com/mongodb - Version: 4.2.3 + Version: 4.4.26 Events: Type Reason Age From Message @@ -221,7 +221,7 @@ kind: MongoDB metadata: annotations: kubectl.kubernetes.io/last-applied-configuration: | - {"apiVersion":"kubedb.com/v1alpha2","kind":"MongoDB","metadata":{"annotations":{},"name":"mgo-init-script","namespace":"demo"},"spec":{"init":{"script":{"configMap":{"name":"mg-init-script"}}},"storage":{"accessModes":["ReadWriteOnce"],"resources":{"requests":{"storage":"1Gi"}},"storageClassName":"standard"},"version":"4.2.3"}} + {"apiVersion":"kubedb.com/v1alpha2","kind":"MongoDB","metadata":{"annotations":{},"name":"mgo-init-script","namespace":"demo"},"spec":{"init":{"script":{"configMap":{"name":"mg-init-script"}}},"storage":{"accessModes":["ReadWriteOnce"],"resources":{"requests":{"storage":"1Gi"}},"storageClassName":"standard"},"version":"4.4.26"}} creationTimestamp: "2021-02-10T04:38:52Z" finalizers: - kubedb.com @@ -360,7 +360,7 @@ spec: storageEngine: wiredTiger storageType: Durable terminationPolicy: Delete - version: 4.2.3 + version: 4.4.26 status: conditions: - lastTransitionTime: "2021-02-10T04:38:53Z" diff --git a/docs/guides/mongodb/monitoring/overview.md b/docs/guides/mongodb/monitoring/overview.md index f9d6b57f54..c74e35fa04 100644 --- a/docs/guides/mongodb/monitoring/overview.md +++ b/docs/guides/mongodb/monitoring/overview.md @@ -53,7 +53,7 @@ metadata: name: sample-mongo namespace: databases spec: - version: "4.2.3" + version: "4.4.26" terminationPolicy: WipeOut configSecret: name: config @@ -95,7 +95,7 @@ spec: Here, we have specified that we are going to monitor this server using Prometheus operator through `spec.monitor.agent: prometheus.io/operator`. KubeDB will create a `ServiceMonitor` crd in databases namespace and this `ServiceMonitor` will have `release: prometheus` label. One thing to note that, we internally use `--collect-all` args, if the mongodb exporter version >= v0.31.0 . You can check the exporter version by getting the mgversion object, like this, -`kubectl get mgversion -o=jsonpath='{.spec.exporter.image}' 4.2.3` +`kubectl get mgversion -o=jsonpath='{.spec.exporter.image}' 4.4.26` In that case, specifying args to collect something (as we used `--collect.database` above) will not have any effect. ## Next Steps diff --git a/docs/guides/mongodb/monitoring/using-builtin-prometheus.md b/docs/guides/mongodb/monitoring/using-builtin-prometheus.md index bd22235e6d..0e9ddd7bf8 100644 --- a/docs/guides/mongodb/monitoring/using-builtin-prometheus.md +++ b/docs/guides/mongodb/monitoring/using-builtin-prometheus.md @@ -49,7 +49,7 @@ metadata: name: builtin-prom-mgo namespace: demo spec: - version: "4.2.3" + version: "4.4.26" terminationPolicy: WipeOut storage: storageClassName: "standard" @@ -78,7 +78,7 @@ Now, wait for the database to go into `Running` state. ```bash $ kubectl get mg -n demo builtin-prom-mgo NAME VERSION STATUS AGE -builtin-prom-mgo 4.2.3 Ready 2m34s +builtin-prom-mgo 4.4.26 Ready 2m34s ``` KubeDB will create a separate stats service with name `{MongoDB crd name}-stats` for monitoring purpose. diff --git a/docs/guides/mongodb/monitoring/using-prometheus-operator.md b/docs/guides/mongodb/monitoring/using-prometheus-operator.md index ac354e4a97..e654ec0f67 100644 --- a/docs/guides/mongodb/monitoring/using-prometheus-operator.md +++ b/docs/guides/mongodb/monitoring/using-prometheus-operator.md @@ -138,7 +138,7 @@ metadata: name: coreos-prom-mgo namespace: demo spec: - version: "4.2.3" + version: "4.4.26" terminationPolicy: WipeOut storage: storageClassName: "standard" @@ -174,7 +174,7 @@ Now, wait for the database to go into `Running` state. ```bash $ kubectl get mg -n demo coreos-prom-mgo NAME VERSION STATUS AGE -coreos-prom-mgo 4.2.3 Ready 34s +coreos-prom-mgo 4.4.26 Ready 34s ``` KubeDB will create a separate stats service with name `{MongoDB crd name}-stats` for monitoring purpose. diff --git a/docs/guides/mongodb/private-registry/using-private-registry.md b/docs/guides/mongodb/private-registry/using-private-registry.md index 52db85ec6c..239e251433 100644 --- a/docs/guides/mongodb/private-registry/using-private-registry.md +++ b/docs/guides/mongodb/private-registry/using-private-registry.md @@ -32,15 +32,15 @@ KubeDB operator supports using private Docker registry. This tutorial will show 3.4.17-v1 3.4.17 kubedb/mongodb-init:4.1-v7 mongo:3.4.17 kubedb/mongodb_exporter:v0.20.4 3.4.22-v1 3.4.22 kubedb/mongodb-init:4.1-v7 mongo:3.4.22 kubedb/mongodb_exporter:v0.32.0 3.6.13-v1 3.6.13 kubedb/mongodb-init:4.1-v7 mongo:3.6.13 kubedb/mongodb_exporter:v0.32.0 - 3.6.8-v1 3.6.8 kubedb/mongodb-init:4.1-v7 mongo:3.6.8 kubedb/mongodb_exporter:v0.32.0 + 4.4.26 3.6.8 kubedb/mongodb-init:4.1-v7 mongo:3.6.8 kubedb/mongodb_exporter:v0.32.0 4.0.11-v1 4.0.11 kubedb/mongodb-init:4.1-v7 mongo:4.0.11 kubedb/mongodb_exporter:v0.32.0 4.0.3-v1 4.0.3 kubedb/mongodb-init:4.1-v7 mongo:4.0.3 kubedb/mongodb_exporter:v0.32.0 - 4.0.5-v3 4.0.5 kubedb/mongodb-init:4.1-v7 mongo:4.0.5 kubedb/mongodb_exporter:v0.32.0 - 4.1.13-v1 4.1.13 kubedb/mongodb-init:4.2-v7 mongo:4.1.13 kubedb/mongodb_exporter:v0.32.0 + 4.4.26 4.0.5 kubedb/mongodb-init:4.1-v7 mongo:4.0.5 kubedb/mongodb_exporter:v0.32.0 + 4.4.26 4.1.13 kubedb/mongodb-init:4.2-v7 mongo:4.1.13 kubedb/mongodb_exporter:v0.32.0 4.1.4-v1 4.1.4 kubedb/mongodb-init:4.1.4-v7 mongo:4.1.4 kubedb/mongodb_exporter:v0.32.0 4.1.7-v3 4.1.7 kubedb/mongodb-init:4.2-v7 mongo:4.1.7 kubedb/mongodb_exporter:v0.32.0 - 4.2.3 4.2.3 kubedb/mongodb-init:4.2-v7 mongo:4.2.3 kubedb/mongodb_exporter:v0.32.0 - 4.4.6 4.4.6 kubedb/mongodb-init:4.2-v7 mongo:4.4.6 kubedb/mongodb_exporter:v0.32.0 + 4.4.26 4.4.26 kubedb/mongodb-init:4.2-v7 mongo:4.4.26 kubedb/mongodb_exporter:v0.32.0 + 4.4.26 4.4.26 kubedb/mongodb-init:4.2-v7 mongo:4.4.26 kubedb/mongodb_exporter:v0.32.0 5.0.2 5.0.2 kubedb/mongodb-init:4.2-v7 mongo:5.0.2 kubedb/mongodb_exporter:v0.32.0 5.0.3 5.0.3 kubedb/mongodb-init:4.2-v7 mongo:5.0.3 kubedb/mongodb_exporter:v0.32.0 percona-3.6.18 3.6.18 kubedb/mongodb-init:4.1-v7 percona/percona-server-mongodb:3.6.18 kubedb/mongodb_exporter:v0.32.0 @@ -71,13 +71,13 @@ Follow the steps [install KubeDB operator](/docs/setup/README.md) properly. The apiVersion: catalog.kubedb.com/v1alpha1 kind: MongoDBVersion metadata: - name: "4.2.3" + name: "4.4.26" labels: app: kubedb spec: - version: "4.2.3" + version: "4.4.26" db: - image: "PRIVATE_DOCKER_REGISTRY/mongo:4.2.3" + image: "PRIVATE_DOCKER_REGISTRY/mongo:4.4.26" exporter: image: "PRIVATE_DOCKER_REGISTRY/percona-mongodb-exporter:v0.8.0" initContainer: @@ -130,7 +130,7 @@ metadata: name: mgo-pvt-reg namespace: demo spec: - version: 4.2.3 + version: 4.4.26 storage: storageClassName: "standard" accessModes: @@ -161,7 +161,7 @@ mgo-pvt-reg-0 1/1 Running 0 5m $ kubectl get mg -n demo NAME VERSION STATUS AGE -mgo-pvt-reg 4.2.3 Ready 38s +mgo-pvt-reg 4.4.26 Ready 38s ``` ## Cleaning up diff --git a/docs/guides/mongodb/quickstart/quickstart.md b/docs/guides/mongodb/quickstart/quickstart.md index eb3d870401..4c8ed4dede 100644 --- a/docs/guides/mongodb/quickstart/quickstart.md +++ b/docs/guides/mongodb/quickstart/quickstart.md @@ -54,15 +54,15 @@ NAME VERSION DISTRIBUTION DB_IMAGE 3.4.17-v1 3.4.17 Official mongo:3.4.17 68s 3.4.22-v1 3.4.22 Official mongo:3.4.22 68s 3.6.13-v1 3.6.13 Official mongo:3.6.13 68s -3.6.8-v1 3.6.8 Official mongo:3.6.8 68s +4.4.26 3.6.8 Official mongo:3.6.8 68s 4.0.11-v1 4.0.11 Official mongo:4.0.11 68s 4.0.3-v1 4.0.3 Official mongo:4.0.3 68s -4.0.5-v3 4.0.5 Official mongo:4.0.5 68s -4.1.13-v1 4.1.13 Official mongo:4.1.13 68s +4.4.26 4.0.5 Official mongo:4.0.5 68s +4.4.26 4.1.13 Official mongo:4.1.13 68s 4.1.4-v1 4.1.4 Official mongo:4.1.4 68s 4.1.7-v3 4.1.7 Official mongo:4.1.7 68s -4.2.3 4.2.3 Official mongo:4.2.3 68s -4.4.6 4.4.6 Official mongo:4.4.6 68s +4.4.26 4.4.26 Official mongo:4.4.26 68s +4.4.26 4.4.26 Official mongo:4.4.26 68s 5.0.2 5.0.2 Official mongo:5.0.2 68s 5.0.3 5.0.3 Official mongo:5.0.3 68s percona-3.6.18 3.6.18 Percona percona/percona-server-mongodb:3.6.18 68s @@ -83,7 +83,7 @@ metadata: name: mgo-quickstart namespace: demo spec: - version: "4.4.6" + version: "4.4.26" replicaSet: name: "rs1" replicas: 3 @@ -105,7 +105,7 @@ mongodb.kubedb.com/mgo-quickstart created Here, -- `spec.version` is name of the MongoDBVersion crd where the docker images are specified. In this tutorial, a MongoDB 4.4.6 database is created. +- `spec.version` is name of the MongoDBVersion crd where the docker images are specified. In this tutorial, a MongoDB 4.4.26 database is created. - `spec.storageType` specifies the type of storage that will be used for MongoDB database. It can be `Durable` or `Ephemeral`. Default value of this field is `Durable`. If `Ephemeral` is used then KubeDB will create MongoDB database using `EmptyDir` volume. In this case, you don't have to specify `spec.storage` field. This is useful for testing purposes. - `spec.storage` specifies PVC spec that will be dynamically allocated to store data for this database. This storage spec will be passed to the StatefulSet created by KubeDB operator to run database pods. You can specify any StorageClass available in your cluster with appropriate resource requests. - `spec.terminationPolicy` gives flexibility whether to `nullify`(reject) the delete operation of `MongoDB` crd or which resources KubeDB should keep or delete when you delete `MongoDB` crd. If admission webhook is enabled, It prevents users from deleting the database as long as the `spec.terminationPolicy` is set to `DoNotTerminate`. Learn details of all `TerminationPolicy` [here](/docs/guides/mongodb/concepts/mongodb.md#specterminationpolicy) @@ -186,7 +186,7 @@ Auth Secret: AppBinding: Metadata: Annotations: - kubectl.kubernetes.io/last-applied-configuration: {"apiVersion":"kubedb.com/v1alpha2","kind":"MongoDB","metadata":{"annotations":{},"name":"mgo-quickstart","namespace":"demo"},"spec":{"replicaSet":{"name":"rs1"},"replicas":3,"storage":{"accessModes":["ReadWriteOnce"],"resources":{"requests":{"storage":"1Gi"}},"storageClassName":"standard"},"storageType":"Durable","terminationPolicy":"DoNotTerminate","version":"4.4.6"}} + kubectl.kubernetes.io/last-applied-configuration: {"apiVersion":"kubedb.com/v1alpha2","kind":"MongoDB","metadata":{"annotations":{},"name":"mgo-quickstart","namespace":"demo"},"spec":{"replicaSet":{"name":"rs1"},"replicas":3,"storage":{"accessModes":["ReadWriteOnce"],"resources":{"requests":{"storage":"1Gi"}},"storageClassName":"standard"},"storageType":"Durable","terminationPolicy":"DoNotTerminate","version":"4.4.26"}} Creation Timestamp: 2022-06-13T12:01:55Z Labels: @@ -216,7 +216,7 @@ AppBinding: Secret: Name: mgo-quickstart-auth Type: kubedb.com/mongodb - Version: 4.4.6 + Version: 4.4.26 Events: Type Reason Age From Message @@ -259,7 +259,7 @@ kind: MongoDB metadata: annotations: kubectl.kubernetes.io/last-applied-configuration: | - {"apiVersion":"kubedb.com/v1alpha2","kind":"MongoDB","metadata":{"annotations":{},"name":"mgo-quickstart","namespace":"demo"},"spec":{"replicaSet":{"name":"rs1"},"replicas":3,"storage":{"accessModes":["ReadWriteOnce"],"resources":{"requests":{"storage":"1Gi"}},"storageClassName":"standard"},"storageType":"Durable","terminationPolicy":"DoNotTerminate","version":"4.4.6"}} + {"apiVersion":"kubedb.com/v1alpha2","kind":"MongoDB","metadata":{"annotations":{},"name":"mgo-quickstart","namespace":"demo"},"spec":{"replicaSet":{"name":"rs1"},"replicas":3,"storage":{"accessModes":["ReadWriteOnce"],"resources":{"requests":{"storage":"1Gi"}},"storageClassName":"standard"},"storageType":"Durable","terminationPolicy":"DoNotTerminate","version":"4.4.26"}} creationTimestamp: "2022-06-13T12:01:55Z" finalizers: - kubedb.com @@ -354,7 +354,7 @@ spec: storageEngine: wiredTiger storageType: Durable terminationPolicy: Delete - version: 4.4.6 + version: 4.4.26 status: conditions: - lastTransitionTime: "2022-06-13T12:01:55Z" @@ -490,7 +490,7 @@ Now, you can run the following command to get all mongodb resources in demo name ```bash $ kubectl get mg,sts,svc,secret,pvc -n demo NAME VERSION STATUS AGE -mongodb.kubedb.com/mgo-quickstart 4.4.6 Halted 12m +mongodb.kubedb.com/mgo-quickstart 4.4.26 Halted 12m NAME TYPE DATA AGE secret/default-token-swg6h kubernetes.io/service-account-token 3 12m @@ -518,7 +518,7 @@ When the database is resumed successfully, you can see the database Status is se ```bash $ kubectl get mg -n demo NAME VERSION STATUS AGE -mgo-quickstart 4.4.6 Ready 13m +mgo-quickstart 4.4.26 Ready 13m ``` Now, If you again exec into the `pod` and look for previous data, you will see that, all the data persists. diff --git a/docs/guides/mongodb/reconfigure-tls/reconfigure-tls.md b/docs/guides/mongodb/reconfigure-tls/reconfigure-tls.md index a5dfc47c0a..91a1934f56 100644 --- a/docs/guides/mongodb/reconfigure-tls/reconfigure-tls.md +++ b/docs/guides/mongodb/reconfigure-tls/reconfigure-tls.md @@ -50,7 +50,7 @@ metadata: name: mg-rs namespace: demo spec: - version: "4.2.3" + version: "4.4.26" replicas: 3 replicaSet: name: rs0 @@ -75,7 +75,7 @@ Now, wait until `mg-replicaset` has status `Ready`. i.e, ```bash $ kubectl get mg -n demo NAME VERSION STATUS AGE -mg-rs 4.2.3 Ready 10m +mg-rs 4.4.26 Ready 10m $ kubectl dba describe mongodb mg-rs -n demo Name: mg-rs @@ -146,7 +146,7 @@ Auth Secret: AppBinding: Metadata: Annotations: - kubectl.kubernetes.io/last-applied-configuration: {"apiVersion":"kubedb.com/v1alpha2","kind":"MongoDB","metadata":{"annotations":{},"name":"mg-rs","namespace":"demo"},"spec":{"replicaSet":{"name":"rs0"},"replicas":3,"storage":{"accessModes":["ReadWriteOnce"],"resources":{"requests":{"storage":"1Gi"}},"storageClassName":"standard"},"version":"4.2.3"}} + kubectl.kubernetes.io/last-applied-configuration: {"apiVersion":"kubedb.com/v1alpha2","kind":"MongoDB","metadata":{"annotations":{},"name":"mg-rs","namespace":"demo"},"spec":{"replicaSet":{"name":"rs0"},"replicas":3,"storage":{"accessModes":["ReadWriteOnce"],"resources":{"requests":{"storage":"1Gi"}},"storageClassName":"standard"},"version":"4.4.26"}} Creation Timestamp: 2021-03-11T07:26:44Z Labels: @@ -170,13 +170,13 @@ AppBinding: Stash: Addon: Backup Task: - Name: mongodb-backup-4.2.3-v6 + Name: mongodb-backup-4.4.6-v6 Restore Task: - Name: mongodb-restore-4.2.3-v6 + Name: mongodb-restore-4.4.6-v6 Secret: Name: mg-rs-auth Type: kubedb.com/mongodb - Version: 4.2.3 + Version: 4.4.26 Events: Type Reason Age From Message diff --git a/docs/guides/mongodb/reconfigure/replicaset.md b/docs/guides/mongodb/reconfigure/replicaset.md index 7043d6c8ec..ad78613666 100644 --- a/docs/guides/mongodb/reconfigure/replicaset.md +++ b/docs/guides/mongodb/reconfigure/replicaset.md @@ -43,7 +43,7 @@ Now, we are going to deploy a `MongoDB` Replicaset using a supported version by ### Prepare MongoDB Replicaset -Now, we are going to deploy a `MongoDB` Replicaset database with version `4.2.3`. +Now, we are going to deploy a `MongoDB` Replicaset database with version `4.4.26`. ### Deploy MongoDB @@ -72,7 +72,7 @@ metadata: name: mg-replicaset namespace: demo spec: - version: "4.2.3" + version: "4.4.26" replicas: 3 replicaSet: name: rs0 @@ -100,7 +100,7 @@ Now, wait until `mg-replicaset` has status `Ready`. i.e, ```bash $ kubectl get mg -n demo NAME VERSION STATUS AGE -mg-replicaset 4.2.3 Ready 19m +mg-replicaset 4.4.26 Ready 19m ``` Now, we will check if the database has started with the custom configuration we have provided. diff --git a/docs/guides/mongodb/reconfigure/sharding.md b/docs/guides/mongodb/reconfigure/sharding.md index 044a857961..cdcba63cd3 100644 --- a/docs/guides/mongodb/reconfigure/sharding.md +++ b/docs/guides/mongodb/reconfigure/sharding.md @@ -43,7 +43,7 @@ Now, we are going to deploy a `MongoDB` sharded database using a supported vers ### Prepare MongoDB Shard -Now, we are going to deploy a `MongoDB` sharded database with version `4.2.3`. +Now, we are going to deploy a `MongoDB` sharded database with version `4.4.26`. ### Deploy MongoDB database @@ -72,7 +72,7 @@ metadata: name: mg-sharding namespace: demo spec: - version: 4.2.3 + version: 4.4.26 shardTopology: configServer: replicas: 3 @@ -111,7 +111,7 @@ Now, wait until `mg-sharding` has status `Ready`. i.e, ```bash $ kubectl get mg -n demo NAME VERSION STATUS AGE -mg-sharding 4.2.3 Ready 3m23s +mg-sharding 4.4.26 Ready 3m23s ``` Now, we will check if the database has started with the custom configuration we have provided. diff --git a/docs/guides/mongodb/reconfigure/standalone.md b/docs/guides/mongodb/reconfigure/standalone.md index 1097ec4cec..41da228531 100644 --- a/docs/guides/mongodb/reconfigure/standalone.md +++ b/docs/guides/mongodb/reconfigure/standalone.md @@ -42,7 +42,7 @@ Now, we are going to deploy a `MongoDB` standalone using a supported version by ### Prepare MongoDB Standalone Database -Now, we are going to deploy a `MongoDB` standalone database with version `4.2.3`. +Now, we are going to deploy a `MongoDB` standalone database with version `4.4.26`. ### Deploy MongoDB standalone @@ -71,7 +71,7 @@ metadata: name: mg-standalone namespace: demo spec: - version: "4.2.3" + version: "4.4.26" storageType: Durable storage: storageClassName: "standard" @@ -96,7 +96,7 @@ Now, wait until `mg-standalone` has status `Ready`. i.e, ```bash $ kubectl get mg -n demo NAME VERSION STATUS AGE -mg-standalone 4.2.3 Ready 23s +mg-standalone 4.4.26 Ready 23s ``` Now, we will check if the database has started with the custom configuration we have provided. diff --git a/docs/guides/mongodb/reprovision/reprovision.md b/docs/guides/mongodb/reprovision/reprovision.md index 30fd82214c..9e3909402d 100644 --- a/docs/guides/mongodb/reprovision/reprovision.md +++ b/docs/guides/mongodb/reprovision/reprovision.md @@ -44,7 +44,7 @@ metadata: name: mongo namespace: demo spec: - version: "4.4.6" + version: "4.4.26" replicaSet: name: "replicaset" podTemplate: diff --git a/docs/guides/mongodb/restart/restart.md b/docs/guides/mongodb/restart/restart.md index 69f1e685f3..152f2e858e 100644 --- a/docs/guides/mongodb/restart/restart.md +++ b/docs/guides/mongodb/restart/restart.md @@ -44,7 +44,7 @@ metadata: name: mongo namespace: demo spec: - version: "4.4.6" + version: "4.4.26" replicaSet: name: "replicaset" podTemplate: diff --git a/docs/guides/mongodb/scaling/horizontal-scaling/replicaset.md b/docs/guides/mongodb/scaling/horizontal-scaling/replicaset.md index 97b09ec1cd..1637041a45 100644 --- a/docs/guides/mongodb/scaling/horizontal-scaling/replicaset.md +++ b/docs/guides/mongodb/scaling/horizontal-scaling/replicaset.md @@ -45,7 +45,7 @@ Here, we are going to deploy a `MongoDB` replicaset using a supported version b ### Prepare MongoDB Replicaset Database -Now, we are going to deploy a `MongoDB` replicaset database with version `4.2.3`. +Now, we are going to deploy a `MongoDB` replicaset database with version `4.4.26`. ### Deploy MongoDB replicaset @@ -58,7 +58,7 @@ metadata: name: mg-replicaset namespace: demo spec: - version: "4.2.3" + version: "4.4.26" replicaSet: name: "replicaset" replicas: 3 @@ -84,7 +84,7 @@ Now, wait until `mg-replicaset` has status `Ready`. i.e, ```bash $ kubectl get mg -n demo NAME VERSION STATUS AGE -mg-replicaset 4.2.3 Ready 2m36s +mg-replicaset 4.4.26 Ready 2m36s ``` Let's check the number of replicas this database has from the MongoDB object, number of pods the statefulset have, diff --git a/docs/guides/mongodb/scaling/horizontal-scaling/sharding.md b/docs/guides/mongodb/scaling/horizontal-scaling/sharding.md index 8a18937dc3..6fe36f64d6 100644 --- a/docs/guides/mongodb/scaling/horizontal-scaling/sharding.md +++ b/docs/guides/mongodb/scaling/horizontal-scaling/sharding.md @@ -45,7 +45,7 @@ Here, we are going to deploy a `MongoDB` sharded database using a supported ver ### Prepare MongoDB Sharded Database -Now, we are going to deploy a `MongoDB` sharded database with version `4.2.3`. +Now, we are going to deploy a `MongoDB` sharded database with version `4.4.26`. ### Deploy MongoDB Sharded Database @@ -58,7 +58,7 @@ metadata: name: mg-sharding namespace: demo spec: - version: 4.2.3 + version: 4.4.26 shardTopology: configServer: replicas: 3 @@ -91,7 +91,7 @@ Now, wait until `mg-sharding` has status `Ready`. i.e, ```bash $ kubectl get mg -n demo NAME VERSION STATUS AGE -mg-sharding 4.2.3 Ready 10m +mg-sharding 4.4.26 Ready 10m ``` ##### Verify Number of Shard and Shard Replicas @@ -150,7 +150,7 @@ $ kubectl exec -n demo mg-sharding-mongos-0 -- mongo admin -u root -p xBC-EwMF { "_id" : "shard0", "host" : "shard0/mg-sharding-shard0-0.mg-sharding-shard0-pods.demo.svc.cluster.local:27017,mg-sharding-shard0-1.mg-sharding-shard0-pods.demo.svc.cluster.local:27017,mg-sharding-shard0-2.mg-sharding-shard0-pods.demo.svc.cluster.local:27017", "state" : 1 } { "_id" : "shard1", "host" : "shard1/mg-sharding-shard1-0.mg-sharding-shard1-pods.demo.svc.cluster.local:27017,mg-sharding-shard1-1.mg-sharding-shard1-pods.demo.svc.cluster.local:27017,mg-sharding-shard1-2.mg-sharding-shard1-pods.demo.svc.cluster.local:27017", "state" : 1 } active mongoses: - "4.2.3" : 2 + "4.4.26" : 2 autosplit: Currently enabled: yes balancer: @@ -381,7 +381,7 @@ $ kubectl exec -n demo mg-sharding-mongos-0 -- mongo admin -u root -p xBC-EwMF { "_id" : "shard0", "host" : "shard0/mg-sharding-shard0-0.mg-sharding-shard0-pods.demo.svc.cluster.local:27017,mg-sharding-shard0-1.mg-sharding-shard0-pods.demo.svc.cluster.local:27017,mg-sharding-shard0-2.mg-sharding-shard0-pods.demo.svc.cluster.local:27017", "state" : 1 } { "_id" : "shard1", "host" : "shard1/mg-sharding-shard1-0.mg-sharding-shard1-pods.demo.svc.cluster.local:27017,mg-sharding-shard1-1.mg-sharding-shard1-pods.demo.svc.cluster.local:27017,mg-sharding-shard1-2.mg-sharding-shard1-pods.demo.svc.cluster.local:27017", "state" : 1 } active mongoses: - "4.2.3" : 2 + "4.4.26" : 2 autosplit: Currently enabled: yes balancer: @@ -619,7 +619,7 @@ $ kubectl exec -n demo mg-sharding-mongos-0 -- mongo admin -u root -p xBC-EwMF { "_id" : "shard1", "host" : "shard1/mg-sharding-shard1-0.mg-sharding-shard1-pods.demo.svc.cluster.local:27017,mg-sharding-shard1-1.mg-sharding-shard1-pods.demo.svc.cluster.local:27017,mg-sharding-shard1-2.mg-sharding-shard1-pods.demo.svc.cluster.local:27017,mg-sharding-shard1-3.mg-sharding-shard1-pods.demo.svc.cluster.local:27017", "state" : 1 } { "_id" : "shard2", "host" : "shard2/mg-sharding-shard2-0.mg-sharding-shard2-pods.demo.svc.cluster.local:27017,mg-sharding-shard2-1.mg-sharding-shard2-pods.demo.svc.cluster.local:27017,mg-sharding-shard2-2.mg-sharding-shard2-pods.demo.svc.cluster.local:27017,mg-sharding-shard2-3.mg-sharding-shard2-pods.demo.svc.cluster.local:27017", "state" : 1 } active mongoses: - "4.2.3" : 3 + "4.4.26" : 3 autosplit: Currently enabled: yes balancer: @@ -914,7 +914,7 @@ $ kubectl exec -n demo mg-sharding-mongos-0 -- mongo admin -u root -p xBC-EwMF { "_id" : "shard1", "host" : "shard1/mg-sharding-shard1-0.mg-sharding-shard1-pods.demo.svc.cluster.local:27017,mg-sharding-shard1-1.mg-sharding-shard1-pods.demo.svc.cluster.local:27017,mg-sharding-shard1-2.mg-sharding-shard1-pods.demo.svc.cluster.local:27017,mg-sharding-shard1-3.mg-sharding-shard1-pods.demo.svc.cluster.local:27017", "state" : 1 } { "_id" : "shard2", "host" : "shard2/mg-sharding-shard2-0.mg-sharding-shard2-pods.demo.svc.cluster.local:27017,mg-sharding-shard2-1.mg-sharding-shard2-pods.demo.svc.cluster.local:27017,mg-sharding-shard2-2.mg-sharding-shard2-pods.demo.svc.cluster.local:27017,mg-sharding-shard2-3.mg-sharding-shard2-pods.demo.svc.cluster.local:27017", "state" : 1 } active mongoses: - "4.2.3" : 3 + "4.4.26" : 3 autosplit: Currently enabled: yes balancer: @@ -1160,7 +1160,7 @@ $ kubectl exec -n demo mg-sharding-mongos-0 -- mongo admin -u root -p xBC-EwMF { "_id" : "shard0", "host" : "shard0/mg-sharding-shard0-0.mg-sharding-shard0-pods.demo.svc.cluster.local:27017,mg-sharding-shard0-1.mg-sharding-shard0-pods.demo.svc.cluster.local:27017,mg-sharding-shard0-2.mg-sharding-shard0-pods.demo.svc.cluster.local:27017", "state" : 1 } { "_id" : "shard1", "host" : "shard1/mg-sharding-shard1-0.mg-sharding-shard1-pods.demo.svc.cluster.local:27017,mg-sharding-shard1-1.mg-sharding-shard1-pods.demo.svc.cluster.local:27017,mg-sharding-shard1-2.mg-sharding-shard1-pods.demo.svc.cluster.local:27017", "state" : 1 } active mongoses: - "4.2.3" : 2 + "4.4.26" : 2 autosplit: Currently enabled: yes balancer: @@ -1402,7 +1402,7 @@ $ kubectl exec -n demo mg-sharding-mongos-0 -- mongo admin -u root -p xBC-EwMF { "_id" : "shard0", "host" : "shard0/mg-sharding-shard0-0.mg-sharding-shard0-pods.demo.svc.cluster.local:27017,mg-sharding-shard0-1.mg-sharding-shard0-pods.demo.svc.cluster.local:27017,mg-sharding-shard0-2.mg-sharding-shard0-pods.demo.svc.cluster.local:27017", "state" : 1 } { "_id" : "shard1", "host" : "shard1/mg-sharding-shard1-0.mg-sharding-shard1-pods.demo.svc.cluster.local:27017,mg-sharding-shard1-1.mg-sharding-shard1-pods.demo.svc.cluster.local:27017,mg-sharding-shard1-2.mg-sharding-shard1-pods.demo.svc.cluster.local:27017", "state" : 1 } active mongoses: - "4.2.3" : 2 + "4.4.26" : 2 autosplit: Currently enabled: yes balancer: diff --git a/docs/guides/mongodb/scaling/vertical-scaling/replicaset.md b/docs/guides/mongodb/scaling/vertical-scaling/replicaset.md index 70855a447f..5fa3e1a3a8 100644 --- a/docs/guides/mongodb/scaling/vertical-scaling/replicaset.md +++ b/docs/guides/mongodb/scaling/vertical-scaling/replicaset.md @@ -45,7 +45,7 @@ Here, we are going to deploy a `MongoDB` replicaset using a supported version b ### Prepare MongoDB Replicaset Database -Now, we are going to deploy a `MongoDB` replicaset database with version `4.2.3`. +Now, we are going to deploy a `MongoDB` replicaset database with version `4.4.26`. ### Deploy MongoDB replicaset @@ -58,7 +58,7 @@ metadata: name: mg-replicaset namespace: demo spec: - version: "4.2.3" + version: "4.4.26" replicaSet: name: "replicaset" replicas: 3 @@ -84,7 +84,7 @@ Now, wait until `mg-replicaset` has status `Ready`. i.e, ```bash $ kubectl get mg -n demo NAME VERSION STATUS AGE -mg-replicaset 4.2.3 Ready 3m46s +mg-replicaset 4.4.26 Ready 3m46s ``` Let's check the Pod containers resources, diff --git a/docs/guides/mongodb/scaling/vertical-scaling/sharding.md b/docs/guides/mongodb/scaling/vertical-scaling/sharding.md index 90183da2e4..38e3438ffa 100644 --- a/docs/guides/mongodb/scaling/vertical-scaling/sharding.md +++ b/docs/guides/mongodb/scaling/vertical-scaling/sharding.md @@ -45,7 +45,7 @@ Here, we are going to deploy a `MongoDB` sharded database using a supported ver ### Prepare MongoDB Sharded Database -Now, we are going to deploy a `MongoDB` sharded database with version `4.2.3`. +Now, we are going to deploy a `MongoDB` sharded database with version `4.4.26`. ### Deploy MongoDB Sharded Database @@ -58,7 +58,7 @@ metadata: name: mg-sharding namespace: demo spec: - version: 4.2.3 + version: 4.4.26 shardTopology: configServer: replicas: 3 @@ -91,7 +91,7 @@ Now, wait until `mg-sharding` has status `Ready`. i.e, ```bash $ kubectl get mg -n demo NAME VERSION STATUS AGE -mg-sharding 4.2.3 Ready 8m51s +mg-sharding 4.4.26 Ready 8m51s ``` Let's check the Pod containers resources of various components (mongos, shard, configserver etc.) of the database, diff --git a/docs/guides/mongodb/scaling/vertical-scaling/standalone.md b/docs/guides/mongodb/scaling/vertical-scaling/standalone.md index 6a36df526e..61474f2e49 100644 --- a/docs/guides/mongodb/scaling/vertical-scaling/standalone.md +++ b/docs/guides/mongodb/scaling/vertical-scaling/standalone.md @@ -44,7 +44,7 @@ Here, we are going to deploy a `MongoDB` standalone using a supported version b ### Prepare MongoDB Standalone Database -Now, we are going to deploy a `MongoDB` standalone database with version `4.2.3`. +Now, we are going to deploy a `MongoDB` standalone database with version `4.4.26`. ### Deploy MongoDB standalone @@ -57,7 +57,7 @@ metadata: name: mg-standalone namespace: demo spec: - version: "4.2.3" + version: "4.4.26" storageType: Durable storage: storageClassName: "standard" @@ -80,7 +80,7 @@ Now, wait until `mg-standalone` has status `Ready`. i.e, ```bash $ kubectl get mg -n demo NAME VERSION STATUS AGE -mg-standalone 4.2.3 Ready 5m56s +mg-standalone 4.4.26 Ready 5m56s ``` Let's check the Pod containers resources, diff --git a/docs/guides/mongodb/schema-manager/deploy-mongodbdatabase/index.md b/docs/guides/mongodb/schema-manager/deploy-mongodbdatabase/index.md index 72f212be08..7cf958ce49 100644 --- a/docs/guides/mongodb/schema-manager/deploy-mongodbdatabase/index.md +++ b/docs/guides/mongodb/schema-manager/deploy-mongodbdatabase/index.md @@ -65,7 +65,7 @@ spec: selector: matchLabels: "schema.kubedb.com": "mongo" - version: "4.4.6" + version: "4.4.26" replicaSet: name: "replicaset" podTemplate: @@ -88,7 +88,7 @@ spec: Here, -- `spec.version` is the name of the MongoDBVersion CR. Here, we are using MongoDB version `4.4.6`. +- `spec.version` is the name of the MongoDBVersion CR. Here, we are using MongoDB version `4.4.26`. - `spec.storageType` specifies the type of storage that will be used for MongoDB. It can be `Durable` or `Ephemeral`. The default value of this field is `Durable`. If `Ephemeral` is used then KubeDB will create the MongoDB using `EmptyDir` volume. - `spec.storage` specifies the StorageClass of PVC dynamically allocated to store data for this database. This storage spec will be passed to the StatefulSet created by KubeDB operator to run database pods. So, each members will have a pod of this storage configuration. You can specify any StorageClass available in your cluster with appropriate resource requests. - `spec.allowedSchemas` specifies the namespace and selectors of allowed `Schema Manager`. @@ -255,7 +255,7 @@ Here, we are going to connect to the database with the login credentials and ins ```bash $ kubectl exec -it -n demo mongodb-0 -c mongodb -- bash root@mongodb-0:/# mongo --authenticationDatabase=emptydb --username='v-kubernetes-demo-k8s-f7695915-1e-0NV83LXHuGMiittiObYE-1662635657' --password='u-kDmBcMITz9dLrZ7cAL' emptydb -MongoDB shell version v4.4.6 +MongoDB shell version v4.4.26 ... replicaset:PRIMARY> use emptydb @@ -286,7 +286,7 @@ Here, we can see that the `STATUS` of the `schema-manager` is `Expired` because ```bash $ kubectl exec -it -n demo mongodb-0 -c mongodb -- bash root@mongodb-0:/# mongo --authenticationDatabase=emptydb --username='v-kubernetes-demo-k8s-f7695915-1e-0NV83LXHuGMiittiObYE-1662635657' --password='u-kDmBcMITz9dLrZ7cAL' emptydb -MongoDB shell version v4.4.6 +MongoDB shell version v4.4.26 connecting to: mongodb://127.0.0.1:27017/emptydb?authSource=emptydb&compressors=disabled&gssapiServiceName=mongodb Error: Authentication failed. : connect@src/mongo/shell/mongo.js:374:17 diff --git a/docs/guides/mongodb/schema-manager/deploy-mongodbdatabase/yamls/mongodb.yaml b/docs/guides/mongodb/schema-manager/deploy-mongodbdatabase/yamls/mongodb.yaml index 14acba6484..e05eaef8ab 100644 --- a/docs/guides/mongodb/schema-manager/deploy-mongodbdatabase/yamls/mongodb.yaml +++ b/docs/guides/mongodb/schema-manager/deploy-mongodbdatabase/yamls/mongodb.yaml @@ -13,7 +13,7 @@ spec: selector: matchLabels: "schema.kubedb.com": "mongo" - version: "4.4.6" + version: "4.4.26" replicaSet: name: "replicaset" podTemplate: diff --git a/docs/guides/mongodb/schema-manager/initializing-with-script/index.md b/docs/guides/mongodb/schema-manager/initializing-with-script/index.md index 8051326353..40ba574869 100644 --- a/docs/guides/mongodb/schema-manager/initializing-with-script/index.md +++ b/docs/guides/mongodb/schema-manager/initializing-with-script/index.md @@ -65,7 +65,7 @@ spec: selector: matchLabels: "schema.kubedb.com": "mongo" - version: "4.4.6" + version: "4.4.26" replicaSet: name: "replicaset" podTemplate: @@ -88,7 +88,7 @@ spec: Here, -- `spec.version` is the name of the MongoDBVersion CR. Here, we are using MongoDB version `4.4.6`. +- `spec.version` is the name of the MongoDBVersion CR. Here, we are using MongoDB version `4.4.26`. - `spec.storageType` specifies the type of storage that will be used for MongoDB. It can be `Durable` or `Ephemeral`. The default value of this field is `Durable`. If `Ephemeral` is used then KubeDB will create the MongoDB using `EmptyDir` volume. - `spec.storage` specifies the StorageClass of PVC dynamically allocated to store data for this database. This storage spec will be passed to the StatefulSet created by KubeDB operator to run database pods. So, each members will have a pod of this storage configuration. You can specify any StorageClass available in your cluster with appropriate resource requests. - `spec.allowedSchemas` specifies the namespace and selectors of allowed `Schema Manager`. @@ -297,7 +297,7 @@ Here, we are going to connect to the database with the login credentials and ver ```bash $ kubectl exec -it -n demo mongodb-0 -c mongodb -- bash root@mongodb-0:/# mongo --authenticationDatabase=initdb --username='v-kubernetes-demo-k8s-f7695915-1e-6sXNTvVpPDtueRQWvoyH-1662641233' --password='-e4v396GFjjjMgPPuU7q' initdb -MongoDB shell version v4.4.6 +MongoDB shell version v4.4.26 ... replicaset:PRIMARY> show dbs @@ -326,7 +326,7 @@ Here, we can see that the `STATUS` of the `schema-manager` is `Expired` because ```bash $ kubectl exec -it -n demo mongodb-0 -c mongodb -- bash root@mongodb-0:/# mongo --authenticationDatabase=initdb --username='v-kubernetes-demo-k8s-f7695915-1e-6sXNTvVpPDtueRQWvoyH-1662641233' --password='-e4v396GFjjjMgPPuU7q' initdb -MongoDB shell version v4.4.6 +MongoDB shell version v4.4.26 connecting to: mongodb://127.0.0.1:27017/initdb?authSource=initdb&compressors=disabled&gssapiServiceName=mongodb Error: Authentication failed. : connect@src/mongo/shell/mongo.js:374:17 diff --git a/docs/guides/mongodb/schema-manager/initializing-with-script/yamls/mongodb.yaml b/docs/guides/mongodb/schema-manager/initializing-with-script/yamls/mongodb.yaml index 14acba6484..e05eaef8ab 100644 --- a/docs/guides/mongodb/schema-manager/initializing-with-script/yamls/mongodb.yaml +++ b/docs/guides/mongodb/schema-manager/initializing-with-script/yamls/mongodb.yaml @@ -13,7 +13,7 @@ spec: selector: matchLabels: "schema.kubedb.com": "mongo" - version: "4.4.6" + version: "4.4.26" replicaSet: name: "replicaset" podTemplate: diff --git a/docs/guides/mongodb/schema-manager/initializing-with-snapshot/index.md b/docs/guides/mongodb/schema-manager/initializing-with-snapshot/index.md index a4a9645e62..d0940bb68a 100644 --- a/docs/guides/mongodb/schema-manager/initializing-with-snapshot/index.md +++ b/docs/guides/mongodb/schema-manager/initializing-with-snapshot/index.md @@ -80,7 +80,7 @@ spec: allowedSchemas: namespaces: from: All - version: "4.4.6" + version: "4.4.26" replicaSet: name: "replicaset" podTemplate: @@ -103,7 +103,7 @@ spec: Here, -- `spec.version` is the name of the MongoDBVersion CR. Here, we are using MongoDB version `4.4.6`. +- `spec.version` is the name of the MongoDBVersion CR. Here, we are using MongoDB version `4.4.26`. - `spec.storageType` specifies the type of storage that will be used for MongoDB. It can be `Durable` or `Ephemeral`. The default value of this field is `Durable`. If `Ephemeral` is used then KubeDB will create the MongoDB using `EmptyDir` volume. - `spec.storage` specifies the StorageClass of PVC dynamically allocated to store data for this database. This storage spec will be passed to the StatefulSet created by KubeDB operator to run database pods. So, each members will have a pod of this storage configuration. You can specify any StorageClass available in your cluster with appropriate resource requests. - `spec.allowedSchemas` specifies the namespace and selectors of allowed `Schema Manager`. @@ -320,7 +320,7 @@ Here, we are going to connect to the database with the login credentials and ver ```bash $ kubectl exec -it -n demo mongodb-0 -c mongodb -- bash root@mongodb-0:/# mongo --authenticationDatabase=products --username='v-kubernetes-demo-k8s-f7695915-1e-2zXmduPS89LfvW6tr5Bw-1662639843' --password='6ykdBljJ7D8agXeoSp-f' products -MongoDB shell version v4.4.6 +MongoDB shell version v4.4.26 ... replicaset:PRIMARY> show dbs @@ -351,7 +351,7 @@ Here, we can see that the `STATUS` of the `schema-manager` is `Expired` because ```bash $ kubectl exec -it -n demo mongodb-0 -c mongodb -- bash root@mongodb-0:/# mongo --authenticationDatabase=products --username='v-kubernetes-demo-k8s-f7695915-1e-2zXmduPS89LfvW6tr5Bw-1662639843' --password='6ykdBljJ7D8agXeoSp-f' products -MongoDB shell version v4.4.6 +MongoDB shell version v4.4.26 connecting to: mongodb://127.0.0.1:27017/initdb?authSource=initdb&compressors=disabled&gssapiServiceName=mongodb Error: Authentication failed. : connect@src/mongo/shell/mongo.js:374:17 diff --git a/docs/guides/mongodb/schema-manager/initializing-with-snapshot/yamls/mongodb.yaml b/docs/guides/mongodb/schema-manager/initializing-with-snapshot/yamls/mongodb.yaml index 42b50893f2..34868bca70 100644 --- a/docs/guides/mongodb/schema-manager/initializing-with-snapshot/yamls/mongodb.yaml +++ b/docs/guides/mongodb/schema-manager/initializing-with-snapshot/yamls/mongodb.yaml @@ -7,7 +7,7 @@ spec: allowedSchemas: namespaces: from: All - version: "4.4.6" + version: "4.4.26" replicaSet: name: "replicaset" podTemplate: diff --git a/docs/guides/mongodb/tls/replicaset.md b/docs/guides/mongodb/tls/replicaset.md index 29b9c838a1..838c071a46 100644 --- a/docs/guides/mongodb/tls/replicaset.md +++ b/docs/guides/mongodb/tls/replicaset.md @@ -104,7 +104,7 @@ metadata: name: mgo-rs-tls namespace: demo spec: - version: "4.1.13-v1" + version: "4.4.26" sslMode: requireSSL tls: issuerRef: @@ -137,7 +137,7 @@ Now, wait until `mgo-rs-tls created` has status `Ready`. i.e, $ watch kubectl get mg -n demo Every 2.0s: kubectl get mongodb -n demo NAME VERSION STATUS AGE -mgo-rs-tls 4.1.13-v1 Ready 4m10s +mgo-rs-tls 4.4.26 Ready 4m10s ``` ### Verify TLS/SSL in MongoDB Replicaset diff --git a/docs/guides/mongodb/tls/sharding.md b/docs/guides/mongodb/tls/sharding.md index a2fc228cfb..4af043591e 100644 --- a/docs/guides/mongodb/tls/sharding.md +++ b/docs/guides/mongodb/tls/sharding.md @@ -104,7 +104,7 @@ metadata: name: mongo-sh-tls namespace: demo spec: - version: "4.1.13-v1" + version: "4.4.26" sslMode: requireSSL tls: issuerRef: @@ -147,7 +147,7 @@ Now, wait until `mongo-sh-tls created` has status `Ready`. ie, $ watch kubectl get mg -n demo Every 2.0s: kubectl get mongodb -n demo NAME VERSION STATUS AGE -mongo-sh-tls 4.1.13-v1 Ready 4m24s +mongo-sh-tls 4.4.26 Ready 4m24s ``` ### Verify TLS/SSL in MongoDB Sharding diff --git a/docs/guides/mongodb/tls/standalone.md b/docs/guides/mongodb/tls/standalone.md index 74ee927d7f..0366e70308 100644 --- a/docs/guides/mongodb/tls/standalone.md +++ b/docs/guides/mongodb/tls/standalone.md @@ -104,7 +104,7 @@ metadata: name: mgo-tls namespace: demo spec: - version: "4.1.13-v1" + version: "4.4.26" sslMode: requireSSL tls: issuerRef: @@ -133,7 +133,7 @@ Now, wait until `mgo-tls created` has status `Ready`. i.e, $ watch kubectl get mg -n demo Every 2.0s: kubectl get mongodb -n demo NAME VERSION STATUS AGE -mgo-tls 4.1.13-v1 Ready 14s +mgo-tls 4.4.26 Ready 14s ``` ### Verify TLS/SSL in MongoDB Standalone diff --git a/docs/guides/mongodb/update-version/replicaset.md b/docs/guides/mongodb/update-version/replicaset.md index 4bd4a74e01..98ad38f460 100644 --- a/docs/guides/mongodb/update-version/replicaset.md +++ b/docs/guides/mongodb/update-version/replicaset.md @@ -54,7 +54,7 @@ metadata: name: mg-replicaset namespace: demo spec: - version: "3.6.8-v1" + version: "4.4.26" replicaSet: name: "replicaset" replicas: 3 @@ -80,7 +80,7 @@ Now, wait until `mg-replicaset` created has status `Ready`. i.e, ```bash $ k get mongodb -n demo NAME VERSION STATUS AGE -mg-replicaset 3.6.8-v1 Ready 109s +mg-replicaset 4.4.26 Ready 109s ``` We are now ready to apply the `MongoDBOpsRequest` CR to update this database. @@ -104,7 +104,7 @@ spec: databaseRef: name: mg-replicaset updateVersion: - targetVersion: 4.0.5-v3 + targetVersion: 4.4.26 readinessCriteria: oplogMaxLagSeconds: 20 objectsCountDiffPercentage: 10 @@ -200,7 +200,7 @@ Spec: Timeout: 5m Type: UpdateVersion UpdateVersion: - Target Version: 4.0.5-v3 + Target Version: 4.4.26 Status: Conditions: Last Transition Time: 2022-10-26T10:21:20Z @@ -246,7 +246,7 @@ Now, we are going to verify whether the `MongoDB` and the related `StatefulSets` ```bash $ kubectl get mg -n demo mg-replicaset -o=jsonpath='{.spec.version}{"\n"}' -4.0.5-v3 +4.4.26 $ kubectl get sts -n demo mg-replicaset -o=jsonpath='{.spec.template.spec.containers[0].image}{"\n"}' mongo:4.0.5 diff --git a/docs/guides/mongodb/update-version/sharding.md b/docs/guides/mongodb/update-version/sharding.md index 236df82025..04dbcaf0a6 100644 --- a/docs/guides/mongodb/update-version/sharding.md +++ b/docs/guides/mongodb/update-version/sharding.md @@ -54,7 +54,7 @@ metadata: name: mg-sharding namespace: demo spec: - version: 3.6.8-v1 + version: 4.4.26 shardTopology: configServer: replicas: 2 @@ -87,7 +87,7 @@ Now, wait until `mg-sharding` created has status `Ready`. i.e, ```bash $ k get mongodb -n demo NAME VERSION STATUS AGE -mg-sharding 3.6.8-v1 Ready 2m9s +mg-sharding 4.4.26 Ready 2m9s ``` We are now ready to apply the `MongoDBOpsRequest` CR to update this database. @@ -111,7 +111,7 @@ spec: databaseRef: name: mg-sharding updateVersion: - targetVersion: 4.0.5-v3 + targetVersion: 4.4.26 readinessCriteria: oplogMaxLagSeconds: 20 objectsCountDiffPercentage: 10 @@ -208,7 +208,7 @@ Spec: Timeout: 5m Type: UpdateVersion UpdateVersion: - Target Version: 4.0.5-v3 + Target Version: 4.4.26 Status: Conditions: Last Transition Time: 2022-10-26T10:36:12Z @@ -286,7 +286,7 @@ Now, we are going to verify whether the `MongoDB` and the related `StatefulSets` ```bash $ kubectl get mg -n demo mg-sharding -o=jsonpath='{.spec.version}{"\n"}' -4.0.5-v3 +4.4.26 $ kubectl get sts -n demo mg-sharding-configsvr -o=jsonpath='{.spec.template.spec.containers[0].image}{"\n"}' mongo:4.0.5 diff --git a/docs/guides/mongodb/update-version/standalone.md b/docs/guides/mongodb/update-version/standalone.md index 99c3658f55..2a34feb06a 100644 --- a/docs/guides/mongodb/update-version/standalone.md +++ b/docs/guides/mongodb/update-version/standalone.md @@ -53,7 +53,7 @@ metadata: name: mg-standalone namespace: demo spec: - version: "3.6.8-v1" + version: "4.4.26" storageType: Durable storage: storageClassName: "standard" @@ -76,7 +76,7 @@ Now, wait until `mg-standalone` created has status `Ready`. i.e, ```bash $ kubectl get mg -n demo NAME VERSION STATUS AGE - mg-standalone 3.6.8-v1 Ready 8m58s + mg-standalone 4.4.26 Ready 8m58s ``` We are now ready to apply the `MongoDBOpsRequest` CR to update this database. @@ -100,7 +100,7 @@ spec: databaseRef: name: mg-standalone updateVersion: - targetVersion: 4.0.5-v3 + targetVersion: 4.4.26 readinessCriteria: oplogMaxLagSeconds: 20 objectsCountDiffPercentage: 10 @@ -197,7 +197,7 @@ Spec: Timeout: 5m Type: UpdateVersion UpdateVersion: - Target Version: 4.0.5-v3 + Target Version: 4.4.26 Status: Conditions: Last Transition Time: 2022-10-26T10:07:10Z @@ -244,7 +244,7 @@ Now, we are going to verify whether the `MongoDB` and the related `StatefulSets` ```bash $ kubectl get mg -n demo mg-standalone -o=jsonpath='{.spec.version}{"\n"}' -4.0.5-v3 +4.4.26 $ kubectl get sts -n demo mg-standalone -o=jsonpath='{.spec.template.spec.containers[0].image}{"\n"}' mongo:4.0.5 diff --git a/docs/guides/mongodb/volume-expansion/replicaset.md b/docs/guides/mongodb/volume-expansion/replicaset.md index 42078cb0c4..00c7f662bf 100644 --- a/docs/guides/mongodb/volume-expansion/replicaset.md +++ b/docs/guides/mongodb/volume-expansion/replicaset.md @@ -70,7 +70,7 @@ metadata: name: mg-replicaset namespace: demo spec: - version: "4.2.3" + version: "4.4.26" replicaSet: name: "replicaset" replicas: 3 @@ -96,7 +96,7 @@ Now, wait until `mg-replicaset` has status `Ready`. i.e, ```bash $ kubectl get mg -n demo NAME VERSION STATUS AGE -mg-replicaset 4.2.3 Ready 10m +mg-replicaset 4.4.26 Ready 10m ``` Let's check volume size from statefulset, and from the persistent volume, diff --git a/docs/guides/mongodb/volume-expansion/sharding.md b/docs/guides/mongodb/volume-expansion/sharding.md index 5a12b235b7..97318be039 100644 --- a/docs/guides/mongodb/volume-expansion/sharding.md +++ b/docs/guides/mongodb/volume-expansion/sharding.md @@ -57,7 +57,7 @@ standard (default) kubernetes.io/gce-pd Delete Immediate We can see from the output the `standard` storage class has `ALLOWVOLUMEEXPANSION` field as true. So, this storage class supports volume expansion. We can use it. -Now, we are going to deploy a `MongoDB` standalone database with version `4.2.3`. +Now, we are going to deploy a `MongoDB` standalone database with version `4.4.26`. ### Deploy MongoDB @@ -70,7 +70,7 @@ metadata: name: mg-sharding namespace: demo spec: - version: 4.2.3 + version: 4.4.26 shardTopology: configServer: replicas: 2 @@ -103,7 +103,7 @@ Now, wait until `mg-sharding` has status `Ready`. i.e, ```bash $ kubectl get mg -n demo NAME VERSION STATUS AGE -mg-sharding 4.2.3 Ready 2m45s +mg-sharding 4.4.26 Ready 2m45s ``` Let's check volume size from statefulset, and from the persistent volume of shards and config servers, diff --git a/docs/guides/mongodb/volume-expansion/standalone.md b/docs/guides/mongodb/volume-expansion/standalone.md index 9c09475b32..5da7b2abb1 100644 --- a/docs/guides/mongodb/volume-expansion/standalone.md +++ b/docs/guides/mongodb/volume-expansion/standalone.md @@ -56,7 +56,7 @@ standard (default) kubernetes.io/gce-pd Delete Immediate We can see from the output the `standard` storage class has `ALLOWVOLUMEEXPANSION` field as true. So, this storage class supports volume expansion. We can use it. -Now, we are going to deploy a `MongoDB` standalone database with version `4.2.3`. +Now, we are going to deploy a `MongoDB` standalone database with version `4.4.26`. #### Deploy MongoDB standalone @@ -69,7 +69,7 @@ metadata: name: mg-standalone namespace: demo spec: - version: "4.2.3" + version: "4.4.26" storageType: Durable storage: storageClassName: "standard" @@ -92,7 +92,7 @@ Now, wait until `mg-standalone` has status `Ready`. i.e, ```bash $ kubectl get mg -n demo NAME VERSION STATUS AGE -mg-standalone 4.2.3 Ready 2m53s +mg-standalone 4.4.26 Ready 2m53s ``` Let's check volume size from statefulset, and from the persistent volume,