diff --git a/README.md b/README.md index 3fab46bde..56627899e 100644 --- a/README.md +++ b/README.md @@ -36,7 +36,8 @@ Please pick a version of KubeDB that matches your Kubernetes installation. | KubeDB Version | Docs | Kubernetes Version | |------------------------------------------------------------------------------------|-------------------------------------------------------------|--------------------| -| [0.8.0](https://github.com/kubedb/cli/releases/tag/0.8.0) (uses CRD) | [User Guide](https://kubedb.com/docs/0.8.0/) | 1.9.x + | +| [0.9.0-beta.0](https://github.com/kubedb/cli/releases/tag/0.9.0-beta.0) (uses CRD) | [User Guide](https://kubedb.com/docs/0.9.0-beta.0/) | 1.9.x + (for qa) | +| [0.8.0](https://github.com/kubedb/cli/releases/tag/0.8.0) (uses CRD) | [User Guide](https://kubedb.com/docs/0.8.0/) | 1.9.x + | | [0.6.0](https://github.com/kubedb/cli/releases/tag/0.6.0) (uses TPR) | [User Guide](https://github.com/kubedb/cli/tree/0.6.0/docs) | 1.5.x - 1.7.x | ## Installation diff --git a/chart/kubedb-catalog/Chart.yaml b/chart/kubedb-catalog/Chart.yaml index 7c7ab20e2..56fe5f3d6 100644 --- a/chart/kubedb-catalog/Chart.yaml +++ b/chart/kubedb-catalog/Chart.yaml @@ -1,8 +1,8 @@ apiVersion: v1 description: 'KubeDB Catalog by AppsCode - Catalog for database versions' name: kubedb-catalog -version: 0.8.0 -appVersion: 0.8.0 +version: 0.9.0-beta.0 +appVersion: 0.9.0-beta.0 home: https://github.com/kubedb/cli icon: https://cdn.appscode.com/images/icon/kubedb.png sources: diff --git a/chart/kubedb/Chart.yaml b/chart/kubedb/Chart.yaml index 5adffcc24..083979ed1 100755 --- a/chart/kubedb/Chart.yaml +++ b/chart/kubedb/Chart.yaml @@ -1,8 +1,8 @@ apiVersion: v1 description: 'KubeDB by AppsCode - Production ready databases on Kubernetes' name: kubedb -version: 0.8.0 -appVersion: 0.8.0 +version: 0.9.0-beta.0 +appVersion: 0.9.0-beta.0 home: https://github.com/kubedb/cli icon: https://cdn.appscode.com/images/icon/kubedb.png sources: diff --git a/chart/kubedb/README.md b/chart/kubedb/README.md index 95d800b38..41638fde1 100644 --- a/chart/kubedb/README.md +++ b/chart/kubedb/README.md @@ -48,7 +48,7 @@ The following table lists the configurable parameters of the KubeDB chart and th | `replicaCount` | Number of kubedb operator replicas to create (only 1 is supported) | `1` | | `kubedb.registry` | Docker registry used to pull Kubedb operator image | `kubedb` | | `kubedb.repository` | Kubedb operator container image | `operator` | -| `kubedb.tag` | Kubedb operator container image tag | `0.8.0` | +| `kubedb.tag` | Kubedb operator container image tag | `0.9.0-beta.0` | | `imagePullSecrets` | Specify image pull secrets | `nil` (does not add image pull secrets to deployed pods) | | `imagePullPolicy` | Image pull policy | `IfNotPresent` | | `criticalAddon` | If true, installs KubeDB operator as critical addon | `false` | diff --git a/chart/kubedb/values.yaml b/chart/kubedb/values.yaml index ca0aea4eb..cc538e7d7 100644 --- a/chart/kubedb/values.yaml +++ b/chart/kubedb/values.yaml @@ -7,7 +7,7 @@ replicaCount: 1 kubedb: registry: kubedb repository: operator - tag: 0.8.0 + tag: 0.9.0-beta.0 ## Optionally specify an array of imagePullSecrets. ## Secrets must be manually created in the namespace. ## ref: https://kubernetes.io/docs/concepts/containers/images/#specifying-imagepullsecrets-on-a-pod diff --git a/docs/guides/elasticsearch/README.md b/docs/guides/elasticsearch/README.md index 7eb77147f..3238e4990 100644 --- a/docs/guides/elasticsearch/README.md +++ b/docs/guides/elasticsearch/README.md @@ -43,12 +43,13 @@ aliases: ## Supported Elasticsearch Version -| KubeDB Version | Elasticsearch:2.3 | Elasticsearch:5.6 | Elasticsearch:6.2 | -|----------------|:-----------------:|:-----------------:|:-----------------:| -| 0.1.0 - 0.7.0 | ✓ | ✗ | ✗ | -| 0.8.0-beta.2 | ✗ | ✓ | ✗ | -| 0.8.0-rc.0 | ✗ | ✓ | ✗ | -| 0.8.0 | ✗ | ✓ | ✓ | +| KubeDB Version | Elasticsearch:2.3 | Elasticsearch:5.6 | Elasticsearch:6.2 | Elasticsearch:6.2 | +|----------------|:-----------------:|:-----------------:|:-----------------:|:-----------------:| +| 0.1.0 - 0.7.0 | ✓ | ✗ | ✗ | ✗ | +| 0.8.0-beta.2 | ✗ | ✓ | ✗ | ✗ | +| 0.8.0-rc.0 | ✗ | ✓ | ✗ | ✗ | +| 0.8.0 | ✗ | ✓ | ✓ | ✓ | +| 0.9.0-beta.0 | ✗ | ✓ | ✓ | ✓ | ## External tools dependency diff --git a/docs/guides/elasticsearch/clustering/topology.md b/docs/guides/elasticsearch/clustering/topology.md index e0f3ad8f3..06f0fc078 100644 --- a/docs/guides/elasticsearch/clustering/topology.md +++ b/docs/guides/elasticsearch/clustering/topology.md @@ -69,7 +69,7 @@ Here, Create example above with following command ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/elasticsearch/clustering/multi-node-es.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/elasticsearch/clustering/multi-node-es.yaml elasticsearch "multi-node-es" created ``` @@ -159,7 +159,7 @@ Here, Lets create this Elasticsearch object ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/elasticsearch/clustering/topology-es.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/elasticsearch/clustering/topology-es.yaml elasticsearch "topology-es" created ``` diff --git a/docs/guides/elasticsearch/custom-config/with-topology.md b/docs/guides/elasticsearch/custom-config/with-topology.md index 9339a8a5a..6c39ab7d2 100644 --- a/docs/guides/elasticsearch/custom-config/with-topology.md +++ b/docs/guides/elasticsearch/custom-config/with-topology.md @@ -120,7 +120,7 @@ metadata: Now, create an Elasticsearch crd with topology specified, ```console -$ kubectl apply -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/elasticsearch/custom-config/es-custom-with-topology.yaml +$ kubectl apply -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/elasticsearch/custom-config/es-custom-with-topology.yaml elasticsearch.kubedb.com/custom-elasticsearch created ``` diff --git a/docs/guides/elasticsearch/custom-config/without-topology.md b/docs/guides/elasticsearch/custom-config/without-topology.md index ec111132e..ff726dcc5 100644 --- a/docs/guides/elasticsearch/custom-config/without-topology.md +++ b/docs/guides/elasticsearch/custom-config/without-topology.md @@ -111,7 +111,7 @@ metadata: Now, create an Elasticsearch crd without topology, ```console -$ kubectl apply -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/elasticsearch/custom-config/es-custom.yaml +$ kubectl apply -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/elasticsearch/custom-config/es-custom.yaml elasticsearch.kubedb.com/custom-elasticsearch created ``` diff --git a/docs/guides/elasticsearch/initialization/snapshot_source.md b/docs/guides/elasticsearch/initialization/snapshot_source.md index d98e11a95..8e9ef9d59 100644 --- a/docs/guides/elasticsearch/initialization/snapshot_source.md +++ b/docs/guides/elasticsearch/initialization/snapshot_source.md @@ -44,7 +44,7 @@ Follow these steps to prepare this tutorial - Create Elasticsearch object `infant-elasticsearch`, if not exists. ```console - $ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/elasticsearch/quickstart/infant-elasticsearch.yaml + $ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/elasticsearch/quickstart/infant-elasticsearch.yaml elasticsearch "infant-elasticsearch" created ``` @@ -124,7 +124,7 @@ instant-snapshot es/infant-elasticsearch Succeeded 2m Now, create the Elasticsearch object. ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/elasticsearch/initialization/recovered-es.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/elasticsearch/initialization/recovered-es.yaml elasticsearch "recovered-es" created ``` diff --git a/docs/guides/elasticsearch/kibana/connect-kibana.md b/docs/guides/elasticsearch/kibana/connect-kibana.md index 38d9eb1a2..520272c68 100644 --- a/docs/guides/elasticsearch/kibana/connect-kibana.md +++ b/docs/guides/elasticsearch/kibana/connect-kibana.md @@ -255,7 +255,7 @@ metadata: Now, create Elasticsearch crd specifying `spec.databaseSecret` and `spec.configSource` field. ```console -$ kubectl apply -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/elasticsearch/kibana/es-kibana-demo.yaml +$ kubectl apply -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/elasticsearch/kibana/es-kibana-demo.yaml elasticsearch.kubedb.com/es-kibana-demo created ``` @@ -366,7 +366,7 @@ configmap/kibana-config created Finally, deploy Kibana deployment, ```console -$ kubectl apply -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/elasticsearch/kibana/kibana-deployment.yaml +$ kubectl apply -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/elasticsearch/kibana/kibana-deployment.yaml deployment.apps/kibana created ``` diff --git a/docs/guides/elasticsearch/monitoring/using-builtin-prometheus.md b/docs/guides/elasticsearch/monitoring/using-builtin-prometheus.md index 8dba14805..1219fbf1e 100644 --- a/docs/guides/elasticsearch/monitoring/using-builtin-prometheus.md +++ b/docs/guides/elasticsearch/monitoring/using-builtin-prometheus.md @@ -66,7 +66,7 @@ Here, Run following command to create example above. ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/elasticsearch/monitoring/builtin-prom-es.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/elasticsearch/monitoring/builtin-prom-es.yaml elasticsearch "builtin-prom-es" created ``` @@ -179,7 +179,7 @@ data: Create above ConfigMap ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/monitoring/builtin-prometheus/demo-1.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/monitoring/builtin-prometheus/demo-1.yaml configmap "prometheus-server-conf" created ``` @@ -226,7 +226,7 @@ spec: Run the following command to deploy prometheus-server ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/monitoring/builtin-prometheus/demo-2.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/monitoring/builtin-prometheus/demo-2.yaml clusterrole "prometheus-server" created serviceaccount "prometheus-server" created clusterrolebinding "prometheus-server" created diff --git a/docs/guides/elasticsearch/monitoring/using-coreos-prometheus-operator.md b/docs/guides/elasticsearch/monitoring/using-coreos-prometheus-operator.md index 65b25764b..a2ec5a46b 100644 --- a/docs/guides/elasticsearch/monitoring/using-coreos-prometheus-operator.md +++ b/docs/guides/elasticsearch/monitoring/using-coreos-prometheus-operator.md @@ -41,7 +41,7 @@ This tutorial assumes that you are familiar with Elasticsearch concept. Run the following command to deploy CoreOS-Prometheus operator. ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/monitoring/coreos-operator/demo-0.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/monitoring/coreos-operator/demo-0.yaml clusterrole "prometheus-operator" created serviceaccount "prometheus-operator" created clusterrolebinding "prometheus-operator" created @@ -69,7 +69,7 @@ servicemonitors.monitoring.coreos.com 3m Once the Prometheus CRDs are registered, run the following command to create a Prometheus. ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/monitoring/coreos-operator/demo-1.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/monitoring/coreos-operator/demo-1.yaml clusterrole "prometheus" created serviceaccount "prometheus" created clusterrolebinding "prometheus" created @@ -146,7 +146,7 @@ Here, Now create this Elasticsearch object with monitoring spec ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/elasticsearch/monitoring/coreos-prom-es.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/elasticsearch/monitoring/coreos-prom-es.yaml elasticsearch "coreos-prom-es" created ``` diff --git a/docs/guides/elasticsearch/private-registry/using-private-registry.md b/docs/guides/elasticsearch/private-registry/using-private-registry.md index 27ef55326..8c4498272 100644 --- a/docs/guides/elasticsearch/private-registry/using-private-registry.md +++ b/docs/guides/elasticsearch/private-registry/using-private-registry.md @@ -47,7 +47,7 @@ For Elasticsearch, push the following images to your private registry. ```console $ export DOCKER_REGISTRY= -$ docker pull kubedb/operator:0.8.0 ; docker tag kubedb/operator:0.8.0 $DOCKER_REGISTRY/operator:0.8.0 ; docker push $DOCKER_REGISTRY/operator:0.8.0 +$ docker pull kubedb/operator:0.9.0-beta.0 ; docker tag kubedb/operator:0.9.0-beta.0 $DOCKER_REGISTRY/operator:0.9.0-beta.0 ; docker push $DOCKER_REGISTRY/operator:0.9.0-beta.0 $ docker pull kubedb/elasticsearch:5.6 ; docker tag kubedb/elasticsearch:5.6 $DOCKER_REGISTRY/elasticsearch:5.6 ; docker push $DOCKER_REGISTRY/elasticsearch:5.6 $ docker pull kubedb/elasticsearch-tools:5.6 ; docker tag kubedb/elasticsearch-tools:5.6 $DOCKER_REGISTRY/elasticsearch-tools:5.6 ; docker push $DOCKER_REGISTRY/elasticsearch-tools:5.6 ``` @@ -105,7 +105,7 @@ spec: Now run the command to deploy this Elasticsearch object: ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/elasticsearch/private-registry/private-registry.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/elasticsearch/private-registry/private-registry.yaml elasticsearch "pvt-reg-elasticsearch" created ``` diff --git a/docs/guides/elasticsearch/quickstart/quickstart.md b/docs/guides/elasticsearch/quickstart/quickstart.md index 9856ec174..fb2ffba68 100644 --- a/docs/guides/elasticsearch/quickstart/quickstart.md +++ b/docs/guides/elasticsearch/quickstart/quickstart.md @@ -73,7 +73,7 @@ Here, Create example above with following command ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/elasticsearch/quickstart/quick-elasticsearch.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/elasticsearch/quickstart/quick-elasticsearch.yaml elasticsearch "quick-elasticsearch" created ``` @@ -432,7 +432,7 @@ In this tutorial, the DormantDatabase `quick-elasticsearch` can be resumed by cr The below command will resume the DormantDatabase `quick-elasticsearch` ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/elasticsearch/quickstart/quick-elasticsearch.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/elasticsearch/quickstart/quick-elasticsearch.yaml elasticsearch "quick-elasticsearch" created ``` diff --git a/docs/guides/elasticsearch/search-guard/certificate.md b/docs/guides/elasticsearch/search-guard/certificate.md index b677fd481..0d944fdad 100644 --- a/docs/guides/elasticsearch/search-guard/certificate.md +++ b/docs/guides/elasticsearch/search-guard/certificate.md @@ -77,7 +77,7 @@ You need to follow these steps 1. Get root certificate configuration file ```console - $ wget https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/elasticsearch/search-guard/openssl-config/openssl-ca.ini + $ wget https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/elasticsearch/search-guard/openssl-config/openssl-ca.ini ``` ```ini @@ -144,7 +144,7 @@ You need to follow these steps to generate three keystore. To sign certificate, we need another configuration file. ```console -$ wget https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/elasticsearch/search-guard/openssl-config/openssl-sign.ini +$ wget https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/elasticsearch/search-guard/openssl-config/openssl-sign.ini ``` ```ini @@ -226,7 +226,7 @@ Here, Now run following commands ```console -wget https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/elasticsearch/search-guard/openssl-config/openssl-node.ini +wget https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/elasticsearch/search-guard/openssl-config/openssl-node.ini openssl req -config openssl-node.ini -newkey rsa:4096 -sha256 -nodes -out node-csr.pem -keyout node-key.pem openssl ca -config openssl-sign.ini -batch -policy signing_policy -extensions signing_req -out node.pem -infiles node-csr.pem openssl pkcs12 -export -certfile root.pem -inkey node-key.pem -in node.pem -password "pass:$KEY_PASS" -out node.pkcs12 @@ -267,7 +267,7 @@ Here, Now run following commands ```console -wget https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/elasticsearch/search-guard/openssl-config/openssl-client.ini +wget https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/elasticsearch/search-guard/openssl-config/openssl-client.ini openssl req -config openssl-client.ini -newkey rsa:4096 -sha256 -nodes -out client-csr.pem -keyout client-key.pem openssl ca -config openssl-sign.ini -batch -policy signing_policy -extensions signing_req -out client.pem -infiles client-csr.pem openssl pkcs12 -export -certfile root.pem -inkey client-key.pem -in client.pem -password "pass:$KEY_PASS" -out client.pkcs12 @@ -307,7 +307,7 @@ Here, Now run following commands ```console -wget https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/elasticsearch/search-guard/openssl-config/openssl-sgadmin.ini +wget https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/elasticsearch/search-guard/openssl-config/openssl-sgadmin.ini openssl req -config openssl-sgadmin.ini -newkey rsa:4096 -sha256 -nodes -out sgadmin-csr.pem -keyout sgadmin-key.pem openssl ca -config openssl-sign.ini -batch -policy signing_policy -extensions signing_req -out sgadmin.pem -infiles sgadmin-csr.pem openssl pkcs12 -export -certfile root.pem -inkey sgadmin-key.pem -in sgadmin.pem -password "pass:$KEY_PASS" -out sgadmin.pkcs12 @@ -367,7 +367,7 @@ Here, Create example above with following command ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/elasticsearch/search-guard/sg-elasticsearch.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/elasticsearch/search-guard/sg-elasticsearch.yaml elasticsearch "sg-elasticsearch" created ``` diff --git a/docs/guides/elasticsearch/search-guard/configuration.md b/docs/guides/elasticsearch/search-guard/configuration.md index 68efed789..2e59bda85 100644 --- a/docs/guides/elasticsearch/search-guard/configuration.md +++ b/docs/guides/elasticsearch/search-guard/configuration.md @@ -100,7 +100,7 @@ searchguard: ``` ```console -$ wget https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/elasticsearch/search-guard/sg-config/sg_config.yml +$ wget https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/elasticsearch/search-guard/sg-config/sg_config.yml ``` ### sg_internal_users.yml @@ -149,7 +149,7 @@ readall: Run following command to write user information in `sg_internal_users.yml` file with password. ```console -curl https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/elasticsearch/search-guard/sg-config/sg_internal_users.yml | envsubst > sg_internal_users.yml +curl https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/elasticsearch/search-guard/sg-config/sg_internal_users.yml | envsubst > sg_internal_users.yml ``` > Note: Random password is set if KubeDB creates Secret for Users. @@ -173,7 +173,7 @@ See details about [action groups](http://docs.search-guard.com/v5/action-groups) Run following command to get action groups we will use in this tutorial ```console -$ wget https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/elasticsearch/search-guard/sg-config/sg_action_groups.yml +$ wget https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/elasticsearch/search-guard/sg-config/sg_action_groups.yml ``` ```yml @@ -255,7 +255,7 @@ sg_readall: ``` ```console -$ wget https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/elasticsearch/search-guard/sg-config/sg_roles.yml +$ wget https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/elasticsearch/search-guard/sg-config/sg_roles.yml ``` ### sg_roles_mapping.yml @@ -293,7 +293,7 @@ See details about [backend roles mapping](http://docs.search-guard.com/v5/mappin Get roles mapping by running ```console -$ wget https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/elasticsearch/search-guard/sg-config/sg_roles_mapping.yml +$ wget https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/elasticsearch/search-guard/sg-config/sg_roles_mapping.yml ``` ```yml @@ -375,7 +375,7 @@ Here, Create example above with following command ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/elasticsearch/search-guard/config-elasticsearch.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/elasticsearch/search-guard/config-elasticsearch.yaml elasticsearch "config-elasticsearch" created ``` diff --git a/docs/guides/elasticsearch/search-guard/use_certificate.md b/docs/guides/elasticsearch/search-guard/use_certificate.md index e227cf292..fc6dafcb0 100644 --- a/docs/guides/elasticsearch/search-guard/use_certificate.md +++ b/docs/guides/elasticsearch/search-guard/use_certificate.md @@ -52,7 +52,7 @@ spec: If Elasticsearch object `ssl-elasticsearch` doesn't exists, create it first. ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/elasticsearch/search-guard/ssl-elasticsearch.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/elasticsearch/search-guard/ssl-elasticsearch.yaml elasticsearch "ssl-elasticsearch" created ``` diff --git a/docs/guides/elasticsearch/snapshot/instant_backup.md b/docs/guides/elasticsearch/snapshot/instant_backup.md index 610d0740e..474daffc2 100644 --- a/docs/guides/elasticsearch/snapshot/instant_backup.md +++ b/docs/guides/elasticsearch/snapshot/instant_backup.md @@ -49,7 +49,7 @@ spec: If Elasticsearch object `infant-elasticsearch` doesn't exists, create it first. ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/elasticsearch/quickstart/infant-elasticsearch.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/elasticsearch/quickstart/infant-elasticsearch.yaml elasticsearch "infant-elasticsearch" created ``` @@ -195,7 +195,7 @@ To lean how to configure other storage destinations for snapshot data, please vi Now, create the Snapshot object. ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/elasticsearch/snapshot/instant-snapshot.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/elasticsearch/snapshot/instant-snapshot.yaml snapshot "instant-snapshot" created ``` diff --git a/docs/guides/elasticsearch/snapshot/scheduled_backup.md b/docs/guides/elasticsearch/snapshot/scheduled_backup.md index c974168c2..e749ed970 100644 --- a/docs/guides/elasticsearch/snapshot/scheduled_backup.md +++ b/docs/guides/elasticsearch/snapshot/scheduled_backup.md @@ -91,7 +91,7 @@ Here, > Note: Secret object must be in the same namespace as Elasticsearch, `scheduled-es`, in this case. ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/elasticsearch/snapshot/scheduled-es.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/elasticsearch/snapshot/scheduled-es.yaml elasticsearch "scheduled-es" created ``` diff --git a/docs/guides/elasticsearch/x-pack/x-pack-monitoring.md b/docs/guides/elasticsearch/x-pack/x-pack-monitoring.md index 63d11fe07..3b3957e27 100644 --- a/docs/guides/elasticsearch/x-pack/x-pack-monitoring.md +++ b/docs/guides/elasticsearch/x-pack/x-pack-monitoring.md @@ -284,7 +284,7 @@ metadata: Now, create Elasticsearch crd specifying `spec.databaseSecret` and `spec.configSource` field. ```console -$ kubectl apply -f kubectl apply -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/elasticsearch/x-pack/es-mon-demo.yaml +$ kubectl apply -f kubectl apply -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/elasticsearch/x-pack/es-mon-demo.yaml elasticsearch.kubedb.com/es-mon-demo created ``` @@ -399,7 +399,7 @@ configmap/kibana-config created Finally, deploy Kibana deployment, ```console -$ kubectl apply -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/elasticsearch/kibana/kibana-deployment.yaml +$ kubectl apply -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/elasticsearch/kibana/kibana-deployment.yaml deployment.apps/kibana created ``` diff --git a/docs/guides/memcached/README.md b/docs/guides/memcached/README.md index 63479cbf8..ee0f0b464 100644 --- a/docs/guides/memcached/README.md +++ b/docs/guides/memcached/README.md @@ -46,6 +46,7 @@ aliases: | 0.8.0-beta.2 | ✓ | | 0.8.0-rc.0 | ✓ | | 0.8.0 | ✓ | +| 0.9.0-beta.0 | ✓ |
diff --git a/docs/guides/memcached/custom-config/using-custom-config.md b/docs/guides/memcached/custom-config/using-custom-config.md index 825f532f7..bfa97686e 100644 --- a/docs/guides/memcached/custom-config/using-custom-config.md +++ b/docs/guides/memcached/custom-config/using-custom-config.md @@ -111,7 +111,7 @@ metadata: Now, create Memcached crd specifying `spec.configSource` field. ```console -$ kubectl apply -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/memcached/custom-config/mc-custom.yaml +$ kubectl apply -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/memcached/custom-config/mc-custom.yaml memcached.kubedb.com/custom-memcached created ``` diff --git a/docs/guides/memcached/monitoring/using-builtin-prometheus.md b/docs/guides/memcached/monitoring/using-builtin-prometheus.md index ae3768b1f..861f52356 100644 --- a/docs/guides/memcached/monitoring/using-builtin-prometheus.md +++ b/docs/guides/memcached/monitoring/using-builtin-prometheus.md @@ -64,7 +64,7 @@ spec: ``` ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/memcached/monitoring/builtin-prometheus/demo-1.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/memcached/monitoring/builtin-prometheus/demo-1.yaml memcached "memcd-mon-prometheus" created ``` @@ -225,7 +225,7 @@ data: ``` ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/monitoring/builtin-prometheus/demo-1.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/monitoring/builtin-prometheus/demo-1.yaml configmap "prometheus-server-conf" created ``` @@ -272,7 +272,7 @@ spec: Run the following command to deploy prometheus-server ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/monitoring/builtin-prometheus/demo-2.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/monitoring/builtin-prometheus/demo-2.yaml clusterrole "prometheus-server" created serviceaccount "prometheus-server" created clusterrolebinding "prometheus-server" created diff --git a/docs/guides/memcached/monitoring/using-coreos-prometheus-operator.md b/docs/guides/memcached/monitoring/using-coreos-prometheus-operator.md index ae15876e6..ad8dedf4d 100644 --- a/docs/guides/memcached/monitoring/using-coreos-prometheus-operator.md +++ b/docs/guides/memcached/monitoring/using-coreos-prometheus-operator.md @@ -30,7 +30,7 @@ Note that the yaml files that are used in this tutorial, stored in [docs/example Run the following command to deploy CoreOS-Prometheus operator. ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/monitoring/coreos-operator/demo-0.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/monitoring/coreos-operator/demo-0.yaml namespace "demo" created clusterrole "prometheus-operator" created serviceaccount "prometheus-operator" created @@ -51,7 +51,7 @@ servicemonitors.monitoring.coreos.com 11m Once the Prometheus operator CRDs are registered, run the following command to create a Prometheus. ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/monitoring/coreos-operator/demo-1.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/monitoring/coreos-operator/demo-1.yaml clusterrole "prometheus" created serviceaccount "prometheus" created clusterrolebinding "prometheus" created @@ -151,7 +151,7 @@ __Known Limitations:__ If the database password is updated, exporter must be res Run the following command to deploy the above `Memcached` CRD object. ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/memcached/monitoring/coreos-operator/demo-1.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/memcached/monitoring/coreos-operator/demo-1.yaml memcached "memcd-mon-coreos" created ``` diff --git a/docs/guides/memcached/private-registry/using-private-registry.md b/docs/guides/memcached/private-registry/using-private-registry.md index bc12e7e11..4544cd3b5 100644 --- a/docs/guides/memcached/private-registry/using-private-registry.md +++ b/docs/guides/memcached/private-registry/using-private-registry.md @@ -30,7 +30,7 @@ You have to push the required images from KubeDB's [Docker hub account](https:// ```console $ export DOCKER_REGISTRY= -$ docker pull kubedb/operator:0.8.0 ; docker tag kubedb/operator:0.8.0 $DOCKER_REGISTRY/operator:0.8.0 ; docker push $DOCKER_REGISTRY/operator:0.8.0 +$ docker pull kubedb/operator:0.9.0-beta.0 ; docker tag kubedb/operator:0.9.0-beta.0 $DOCKER_REGISTRY/operator:0.9.0-beta.0 ; docker push $DOCKER_REGISTRY/operator:0.9.0-beta.0 $ docker pull kubedb/memcached:1.5.4 ; docker tag kubedb/memcached:1.5.4 $DOCKER_REGISTRY/memcached:1.5.4 ; docker push $DOCKER_REGISTRY/memcached:1.5.4 ``` @@ -103,7 +103,7 @@ spec: Now run the command to deploy this `Memcached` object: ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/memcached/private-registry/demo-2.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/memcached/private-registry/demo-2.yaml memcached "memcached-pvt-reg" created ``` diff --git a/docs/guides/memcached/quickstart/quickstart.md b/docs/guides/memcached/quickstart/quickstart.md index 6ba54b038..f2c2fca8d 100644 --- a/docs/guides/memcached/quickstart/quickstart.md +++ b/docs/guides/memcached/quickstart/quickstart.md @@ -65,7 +65,7 @@ spec: ``` ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/memcached/quickstart/demo-1.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/memcached/quickstart/demo-1.yaml memcached "memcd-quickstart" created ``` @@ -271,7 +271,7 @@ To resume the database from the dormant state, create same `Memcached` object wi The below command resumes the dormant database `memcd-quickstart`. ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/memcached/quickstart/demo-1.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/memcached/quickstart/demo-1.yaml memcached "memcd-quickstart" created ``` diff --git a/docs/guides/mongodb/README.md b/docs/guides/mongodb/README.md index 159c49d3c..2826a5abb 100644 --- a/docs/guides/mongodb/README.md +++ b/docs/guides/mongodb/README.md @@ -46,6 +46,7 @@ aliases: | 0.8.0-beta.2 | ✓ | ✓ | | 0.8.0-rc.0 | ✓ | ✓ | | 0.8.0 | ✓ | ✓ | +| 0.9.0-beta.0 | ✓ | ✓ | ## User Guide diff --git a/docs/guides/mongodb/clustering/replicaset.md b/docs/guides/mongodb/clustering/replicaset.md index 5d4496323..99f31aba5 100644 --- a/docs/guides/mongodb/clustering/replicaset.md +++ b/docs/guides/mongodb/clustering/replicaset.md @@ -66,7 +66,7 @@ spec: ``` ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/mongodb/clustering/demo-1.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/mongodb/clustering/demo-1.yaml mongodb.kubedb.com "mgo-replicaset" created ``` @@ -411,7 +411,7 @@ In this tutorial, the dormant database can be resumed by creating original Mongo The below command will resume the DormantDatabase `mgo-replicaset`. ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/mongodb/clustering/demo-1.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/mongodb/clustering/demo-1.yaml mongodb "mgo-replicaset" created ``` diff --git a/docs/guides/mongodb/initialization/using-script.md b/docs/guides/mongodb/initialization/using-script.md index 3220141bf..92c77ec75 100644 --- a/docs/guides/mongodb/initialization/using-script.md +++ b/docs/guides/mongodb/initialization/using-script.md @@ -69,7 +69,7 @@ spec: ``` ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/mongodb/Initialization/demo-1.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/mongodb/Initialization/demo-1.yaml mongodb "mgo-init-script" created ``` diff --git a/docs/guides/mongodb/initialization/using-snapshot.md b/docs/guides/mongodb/initialization/using-snapshot.md index ffa234d34..8fa59520e 100644 --- a/docs/guides/mongodb/initialization/using-snapshot.md +++ b/docs/guides/mongodb/initialization/using-snapshot.md @@ -51,7 +51,7 @@ spec: ``` ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/mongodb/Initialization/demo-2.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/mongodb/Initialization/demo-2.yaml mongodb "mgo-init-snapshot" created ``` diff --git a/docs/guides/mongodb/monitoring/using-builtin-prometheus.md b/docs/guides/mongodb/monitoring/using-builtin-prometheus.md index cecdd522a..3c9772cca 100644 --- a/docs/guides/mongodb/monitoring/using-builtin-prometheus.md +++ b/docs/guides/mongodb/monitoring/using-builtin-prometheus.md @@ -62,7 +62,7 @@ spec: ``` ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/mongodb/monitoring/builtin-prometheus/demo-1.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/mongodb/monitoring/builtin-prometheus/demo-1.yaml mongodb "mgo-mon-prometheus" created ``` @@ -241,7 +241,7 @@ data: ``` ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/monitoring/builtin-prometheus/demo-1.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/monitoring/builtin-prometheus/demo-1.yaml configmap "prometheus-server-conf" created ``` @@ -288,7 +288,7 @@ spec: Run the following command to deploy prometheus-server ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/monitoring/builtin-prometheus/demo-2.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/monitoring/builtin-prometheus/demo-2.yaml clusterrole "prometheus-server" created serviceaccount "prometheus-server" created clusterrolebinding "prometheus-server" created diff --git a/docs/guides/mongodb/monitoring/using-coreos-prometheus-operator.md b/docs/guides/mongodb/monitoring/using-coreos-prometheus-operator.md index 01089786c..b9aab1655 100644 --- a/docs/guides/mongodb/monitoring/using-coreos-prometheus-operator.md +++ b/docs/guides/mongodb/monitoring/using-coreos-prometheus-operator.md @@ -31,7 +31,7 @@ Note that the yaml files that are used in this tutorial, stored in [docs/example Run the following command to deploy CoreOS-Prometheus operator. ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/monitoring/coreos-operator/demo-0.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/monitoring/coreos-operator/demo-0.yaml namespace "demo" created clusterrole "prometheus-operator" created serviceaccount "prometheus-operator" created @@ -53,7 +53,7 @@ servicemonitors.monitoring.coreos.com 11m Once the Prometheus operator CRDs are registered, run the following command to create a Prometheus. ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/monitoring/coreos-operator/demo-1.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/monitoring/coreos-operator/demo-1.yaml clusterrole "prometheus" created serviceaccount "prometheus" created clusterrolebinding "prometheus" created @@ -151,7 +151,7 @@ __Known Limitations:__ If the database password is updated, exporter must be res Run the following command to deploy the above `MongoDB` CRD object. ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/mongodb/monitoring/coreos-operator/demo-1.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/mongodb/monitoring/coreos-operator/demo-1.yaml mongodb "mgo-mon-coreos" created ``` diff --git a/docs/guides/mongodb/private-registry/using-private-registry.md b/docs/guides/mongodb/private-registry/using-private-registry.md index cc29d7832..1225011df 100644 --- a/docs/guides/mongodb/private-registry/using-private-registry.md +++ b/docs/guides/mongodb/private-registry/using-private-registry.md @@ -31,7 +31,7 @@ You have to push the required images from KubeDB's [Docker hub account](https:// ```console $ export DOCKER_REGISTRY= -$ docker pull kubedb/operator:0.8.0 ; docker tag kubedb/operator:0.8.0 $DOCKER_REGISTRY/operator:0.8.0 ; docker push $DOCKER_REGISTRY/operator:0.8.0 +$ docker pull kubedb/operator:0.9.0-beta.0 ; docker tag kubedb/operator:0.9.0-beta.0 $DOCKER_REGISTRY/operator:0.9.0-beta.0 ; docker push $DOCKER_REGISTRY/operator:0.9.0-beta.0 $ docker pull kubedb/mongo:3.4 ; docker tag kubedb/mongo:3.4 $DOCKER_REGISTRY/mongo:3.4 ; docker push $DOCKER_REGISTRY/mongo:3.4 $ docker pull kubedb/mongo:3.6 ; docker tag kubedb/mongo:3.6 $DOCKER_REGISTRY/mongo:3.6 ; docker push $DOCKER_REGISTRY/mongo:3.6 $ docker pull kubedb/mongo-tools:3.4 ; docker tag kubedb/mongo-tools:3.4 $DOCKER_REGISTRY/mongo-tools:3.4 ; docker push $DOCKER_REGISTRY/mongo-tools:3.4 @@ -106,7 +106,7 @@ spec: Now run the command to deploy this `MongoDB` object: ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/mongodb/private-registry/demo-2.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/mongodb/private-registry/demo-2.yaml mongodb "mgo-pvt-reg" created ``` diff --git a/docs/guides/mongodb/quickstart/quickstart.md b/docs/guides/mongodb/quickstart/quickstart.md index e3e249459..c5a594454 100644 --- a/docs/guides/mongodb/quickstart/quickstart.md +++ b/docs/guides/mongodb/quickstart/quickstart.md @@ -66,7 +66,7 @@ spec: ``` ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/mongodb/quickstart/demo-1.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/mongodb/quickstart/demo-1.yaml mongodb "mgo-quickstart" created ``` @@ -312,7 +312,7 @@ In this tutorial, the dormant database can be resumed by creating original Mongo The below command will resume the DormantDatabase `mgo-quickstart`. ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/mongodb/quickstart/demo-1.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/mongodb/quickstart/demo-1.yaml mongodb "mgo-quickstart" created ``` diff --git a/docs/guides/mongodb/snapshot/backup-and-restore.md b/docs/guides/mongodb/snapshot/backup-and-restore.md index a9ea14b57..0f92ff478 100644 --- a/docs/guides/mongodb/snapshot/backup-and-restore.md +++ b/docs/guides/mongodb/snapshot/backup-and-restore.md @@ -35,7 +35,7 @@ demo Active 1m kube-public Active 1h kube-system Active 1h -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/mongodb/snapshot/demo-1.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/mongodb/snapshot/demo-1.yaml mongodb "mgo-infant" created ``` @@ -96,7 +96,7 @@ spec: ``` ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/mongodb/snapshot/demo-2.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/mongodb/snapshot/demo-2.yaml snapshot "snapshot-infant" created $ kubedb get snap -n demo @@ -222,7 +222,7 @@ spec: ``` ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/mongodb/snapshot/demo-3.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/mongodb/snapshot/demo-3.yaml mongodb "mgo-recovered" created ``` diff --git a/docs/guides/mongodb/snapshot/scheduled-backup.md b/docs/guides/mongodb/snapshot/scheduled-backup.md index 65c8e3a01..9a774e12f 100644 --- a/docs/guides/mongodb/snapshot/scheduled-backup.md +++ b/docs/guides/mongodb/snapshot/scheduled-backup.md @@ -105,7 +105,7 @@ spec: ``` ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/mongodb/snapshot/demo-4.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/mongodb/snapshot/demo-4.yaml mongodb "mgo-scheduled" created ``` diff --git a/docs/guides/mysql/README.md b/docs/guides/mysql/README.md index 06765eb79..84dd1da85 100644 --- a/docs/guides/mysql/README.md +++ b/docs/guides/mysql/README.md @@ -46,6 +46,7 @@ aliases: | 0.8.0-beta.2 | ✓ | ✗ | | 0.8.0-rc.0 | ✓ | ✓ | | 0.8.0 | ✓ | ✓ | +| 0.9.0-beta.0 | ✓ | ✓ | ## User Guide diff --git a/docs/guides/mysql/custom-config/using-custom-config.md b/docs/guides/mysql/custom-config/using-custom-config.md index 8a8f2b782..40732fbab 100644 --- a/docs/guides/mysql/custom-config/using-custom-config.md +++ b/docs/guides/mysql/custom-config/using-custom-config.md @@ -84,7 +84,7 @@ metadata: Now, create MySQL crd specifying `spec.configSource` field. ```console -$ kubectl apply -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/mysql/custom-config//mysql-custom.yaml +$ kubectl apply -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/mysql/custom-config//mysql-custom.yaml mysql.kubedb.com "custom-mysql" created ``` @@ -146,7 +146,7 @@ Now, we will check if the database has started with the custom configuration we First, deploy [phpMyAdmin](https://hub.docker.com/r/phpmyadmin/phpmyadmin/) to connect with the MySQL database we have just created. ```console - $ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/mysql/quickstart/demo-1.yaml + $ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/mysql/quickstart/demo-1.yaml deployment.extensions "myadmin" created service "myadmin" created ``` diff --git a/docs/guides/mysql/initialization/using-script.md b/docs/guides/mysql/initialization/using-script.md index e1c6e0c39..d732b44b0 100644 --- a/docs/guides/mysql/initialization/using-script.md +++ b/docs/guides/mysql/initialization/using-script.md @@ -30,7 +30,7 @@ To keep things isolated, this tutorial uses a separate namespace called `demo` t $ kubectl create ns demo namespace "demo" created -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/mysql/quickstart/demo-1.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/mysql/quickstart/demo-1.yaml deployment "myadmin" created service "myadmin" created @@ -86,7 +86,7 @@ spec: ``` ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/mysql/Initialization/demo-1.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/mysql/Initialization/demo-1.yaml mysql "mysql-init-script" created ``` diff --git a/docs/guides/mysql/initialization/using-snapshot.md b/docs/guides/mysql/initialization/using-snapshot.md index 6f63fc9fa..f0e789ba9 100644 --- a/docs/guides/mysql/initialization/using-snapshot.md +++ b/docs/guides/mysql/initialization/using-snapshot.md @@ -51,7 +51,7 @@ spec: ``` ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/mysql/Initialization/demo-2.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/mysql/Initialization/demo-2.yaml mysql "mysql-init-snapshot" created ``` diff --git a/docs/guides/mysql/monitoring/using-builtin-prometheus.md b/docs/guides/mysql/monitoring/using-builtin-prometheus.md index 7c9c6fba9..6b137a7af 100644 --- a/docs/guides/mysql/monitoring/using-builtin-prometheus.md +++ b/docs/guides/mysql/monitoring/using-builtin-prometheus.md @@ -62,7 +62,7 @@ spec: ``` ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/mysql/monitoring/builtin-prometheus/demo-1.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/mysql/monitoring/builtin-prometheus/demo-1.yaml mysql "mysql-mon-prometheus" created ``` @@ -237,7 +237,7 @@ data: ``` ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/monitoring/builtin-prometheus/demo-1.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/monitoring/builtin-prometheus/demo-1.yaml configmap "prometheus-server-conf" created ``` @@ -284,7 +284,7 @@ spec: Run the following command to deploy prometheus-server ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/monitoring/builtin-prometheus/demo-2.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/monitoring/builtin-prometheus/demo-2.yaml clusterrole "prometheus-server" created serviceaccount "prometheus-server" created clusterrolebinding "prometheus-server" created diff --git a/docs/guides/mysql/monitoring/using-coreos-prometheus-operator.md b/docs/guides/mysql/monitoring/using-coreos-prometheus-operator.md index 556340215..812902e52 100644 --- a/docs/guides/mysql/monitoring/using-coreos-prometheus-operator.md +++ b/docs/guides/mysql/monitoring/using-coreos-prometheus-operator.md @@ -31,7 +31,7 @@ Note that the yaml files that are used in this tutorial, stored in [docs/example Run the following command to deploy CoreOS-Prometheus operator. ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/monitoring/coreos-operator/demo-0.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/monitoring/coreos-operator/demo-0.yaml namespace "demo" created clusterrole "prometheus-operator" created serviceaccount "prometheus-operator" created @@ -53,7 +53,7 @@ servicemonitors.monitoring.coreos.com 11m Once the Prometheus operator CRDs are registered, run the following command to create a Prometheus. ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/monitoring/coreos-operator/demo-1.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/monitoring/coreos-operator/demo-1.yaml clusterrole "prometheus" created serviceaccount "prometheus" created clusterrolebinding "prometheus" created @@ -154,7 +154,7 @@ __Known Limitations:__ If the database password is updated, exporter must be res Run the following command to deploy the above `MySQL` CRD object. ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/mysql/monitoring/coreos-operator/demo-1.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/mysql/monitoring/coreos-operator/demo-1.yaml mysql "mysql-mon-coreos" created ``` diff --git a/docs/guides/mysql/private-registry/using-private-registry.md b/docs/guides/mysql/private-registry/using-private-registry.md index ae1315697..35b65ff62 100644 --- a/docs/guides/mysql/private-registry/using-private-registry.md +++ b/docs/guides/mysql/private-registry/using-private-registry.md @@ -30,7 +30,7 @@ You have to push the required images from KubeDB's [Docker hub account](https:// ```console $ export DOCKER_REGISTRY= -$ docker pull kubedb/operator:0.8.0 ; docker tag kubedb/operator:0.8.0 $DOCKER_REGISTRY/operator:0.8.0 ; docker push $DOCKER_REGISTRY/operator:0.8.0 +$ docker pull kubedb/operator:0.9.0-beta.0 ; docker tag kubedb/operator:0.9.0-beta.0 $DOCKER_REGISTRY/operator:0.9.0-beta.0 ; docker push $DOCKER_REGISTRY/operator:0.9.0-beta.0 $ docker pull kubedb/mysql:8.0 ; docker tag kubedb/mysql:8.0 $DOCKER_REGISTRY/mysql:8.0 ; docker push $DOCKER_REGISTRY/mysql:8.0 $ docker pull kubedb/mysql-tools:8.0 ; docker tag kubedb/mysql-tools:8.0 $DOCKER_REGISTRY/mysql-tools:8.0 ; docker push $DOCKER_REGISTRY/mysql-tools:8.0 ``` @@ -103,7 +103,7 @@ spec: Now run the command to deploy this `MySQL` object: ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/mysql/private-registry/demo-2.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/mysql/private-registry/demo-2.yaml mysql "mysql-pvt-reg" created ``` diff --git a/docs/guides/mysql/quickstart/quickstart.md b/docs/guides/mysql/quickstart/quickstart.md index fd19cbd2c..843c94063 100644 --- a/docs/guides/mysql/quickstart/quickstart.md +++ b/docs/guides/mysql/quickstart/quickstart.md @@ -33,7 +33,7 @@ To keep things isolated, this tutorial uses a separate namespace called `demo` t $ kubectl create ns demo namespace "demo" created -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/mysql/quickstart/demo-1.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/mysql/quickstart/demo-1.yaml deployment "myadmin" created service "myadmin" created @@ -83,7 +83,7 @@ spec: ``` ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/mysql/quickstart/demo-2.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/mysql/quickstart/demo-2.yaml mysql "mysql-quickstart" created ``` @@ -291,7 +291,7 @@ In this tutorial, the dormant database can be resumed by creating original `MySQ The below command will resume the DormantDatabase `mysql-quickstart` that was created before. ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/mysql/quickstart/demo-2.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/mysql/quickstart/demo-2.yaml mysql "mysql-quickstart" created ``` diff --git a/docs/guides/mysql/snapshot/backup-and-restore.md b/docs/guides/mysql/snapshot/backup-and-restore.md index 6b1508c7b..f4d0c7c35 100644 --- a/docs/guides/mysql/snapshot/backup-and-restore.md +++ b/docs/guides/mysql/snapshot/backup-and-restore.md @@ -34,7 +34,7 @@ demo Active 1m kube-public Active 1h kube-system Active 1h -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/mysql/snapshot/demo-1.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/mysql/snapshot/demo-1.yaml mysql "mysql-infant" created ``` @@ -95,7 +95,7 @@ spec: ``` ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/mysql/snapshot/demo-2.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/mysql/snapshot/demo-2.yaml snapshot "snap-mysql-infant" created $ kubedb get snap -n demo @@ -221,7 +221,7 @@ spec: ``` ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/mysql/snapshot/demo-3.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/mysql/snapshot/demo-3.yaml mysql "mysql-recovered" created ``` diff --git a/docs/guides/mysql/snapshot/scheduled-backup.md b/docs/guides/mysql/snapshot/scheduled-backup.md index 877208400..859d3b984 100644 --- a/docs/guides/mysql/snapshot/scheduled-backup.md +++ b/docs/guides/mysql/snapshot/scheduled-backup.md @@ -104,7 +104,7 @@ spec: ``` ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/mysql/snapshot/demo-4.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/mysql/snapshot/demo-4.yaml mysql "mysql-scheduled" created ``` diff --git a/docs/guides/postgres/README.md b/docs/guides/postgres/README.md index bb9bf80b5..e87c96712 100644 --- a/docs/guides/postgres/README.md +++ b/docs/guides/postgres/README.md @@ -53,6 +53,7 @@ aliases: | 0.8.0-beta.2 | ✗ | ✓ | ✓ | | 0.8.0-rc.0 | ✗ | ✓ | ✓ | | 0.8.0 | ✗ | ✓ | ✓ | +| 0.9.0-beta.0 | ✗ | ✓ | ✓ |
diff --git a/docs/guides/postgres/clustering/streaming_replication.md b/docs/guides/postgres/clustering/streaming_replication.md index a77255edb..ec30f87c1 100644 --- a/docs/guides/postgres/clustering/streaming_replication.md +++ b/docs/guides/postgres/clustering/streaming_replication.md @@ -101,7 +101,7 @@ Here, Now create this Postgres object with Streaming Replication support ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/postgres/clustering/ha-postgres.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/postgres/clustering/ha-postgres.yaml postgres "ha-postgres" created ``` @@ -262,7 +262,7 @@ Here, Now create this Postgres object ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/postgres/clustering/hot-postgres.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/postgres/clustering/hot-postgres.yaml postgres "hot-postgres" created ``` diff --git a/docs/guides/postgres/custom-config/using-custom-config.md b/docs/guides/postgres/custom-config/using-custom-config.md index 516cc45d3..45956861f 100644 --- a/docs/guides/postgres/custom-config/using-custom-config.md +++ b/docs/guides/postgres/custom-config/using-custom-config.md @@ -82,7 +82,7 @@ metadata: Now, create Postgres crd specifying `spec.configSource` field. ```console -$ kubectl apply -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/postgres/custom-config/pg-custom-config.yaml +$ kubectl apply -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/postgres/custom-config/pg-custom-config.yaml postgres.kubedb.com "custom-postgres" created ``` diff --git a/docs/guides/postgres/custom-versions/setup.md b/docs/guides/postgres/custom-versions/setup.md index f8fcf8c92..169654503 100644 --- a/docs/guides/postgres/custom-versions/setup.md +++ b/docs/guides/postgres/custom-versions/setup.md @@ -66,7 +66,7 @@ spec: db: image: "myco/postgres:timescale-0.9.1" exporter: - image: "kubedb/operator:0.8.0" + image: "kubedb/operator:0.9.0-beta.0" tools: image: "kubedb/postgres-tools:10.2" ``` diff --git a/docs/guides/postgres/initialization/script_source.md b/docs/guides/postgres/initialization/script_source.md index dc9b3923c..0a8825496 100644 --- a/docs/guides/postgres/initialization/script_source.md +++ b/docs/guides/postgres/initialization/script_source.md @@ -77,7 +77,7 @@ In this tutorial, `data.sql` script from the git repository `https://github.com/ > Note: PostgreSQL supports initialization with `.sh`, `.sql` and `.sql.gz` files. ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/postgres/initialization/script-postgres.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/postgres/initialization/script-postgres.yaml postgres "script-postgres" created ``` diff --git a/docs/guides/postgres/initialization/snapshot_source.md b/docs/guides/postgres/initialization/snapshot_source.md index 9d5d68b22..43252c39e 100644 --- a/docs/guides/postgres/initialization/snapshot_source.md +++ b/docs/guides/postgres/initialization/snapshot_source.md @@ -44,7 +44,7 @@ Follow these steps to prepare this tutorial - Create Postgres object `script-postgres`, if not exists. ```console - $ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/postgres/initialization/script-postgres.yaml + $ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/postgres/initialization/script-postgres.yaml postgres "script-postgres" created ``` @@ -123,7 +123,7 @@ instant-snapshot pg/script-postgres Succeeded 12m Now, create the Postgres object. ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/postgres/initialization/recovered-postgres.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/postgres/initialization/recovered-postgres.yaml postgres "recovered-postgres" created ``` diff --git a/docs/guides/postgres/initialization/wal_source.md b/docs/guides/postgres/initialization/wal_source.md index 67da2cc71..379098f26 100644 --- a/docs/guides/postgres/initialization/wal_source.md +++ b/docs/guides/postgres/initialization/wal_source.md @@ -94,7 +94,7 @@ Here, `{namespace}` & `{postgres-name}` indicates Postgres object whose WAL arch Now create this Postgres ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/postgres/initialization/replay-postgres.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/postgres/initialization/replay-postgres.yaml postgres "replay-postgres" created ``` diff --git a/docs/guides/postgres/monitoring/using-builtin-prometheus.md b/docs/guides/postgres/monitoring/using-builtin-prometheus.md index d902539be..d153c875a 100644 --- a/docs/guides/postgres/monitoring/using-builtin-prometheus.md +++ b/docs/guides/postgres/monitoring/using-builtin-prometheus.md @@ -68,7 +68,7 @@ Here, Run following command to create example above. ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/postgres/monitoring/builtin-prom-postgres.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/postgres/monitoring/builtin-prom-postgres.yaml postgres "builtin-prom-postgres" created ``` @@ -169,7 +169,7 @@ data: Create above ConfigMap ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/monitoring/builtin-prometheus/demo-1.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/monitoring/builtin-prometheus/demo-1.yaml configmap "prometheus-server-conf" created ``` @@ -216,7 +216,7 @@ spec: Run the following command to deploy prometheus-server ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/monitoring/builtin-prometheus/demo-2.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/monitoring/builtin-prometheus/demo-2.yaml clusterrole "prometheus-server" created serviceaccount "prometheus-server" created clusterrolebinding "prometheus-server" created diff --git a/docs/guides/postgres/monitoring/using-coreos-prometheus-operator.md b/docs/guides/postgres/monitoring/using-coreos-prometheus-operator.md index 7e26034fe..1060cda5f 100644 --- a/docs/guides/postgres/monitoring/using-coreos-prometheus-operator.md +++ b/docs/guides/postgres/monitoring/using-coreos-prometheus-operator.md @@ -42,7 +42,7 @@ This tutorial assumes that you are familiar with PostgreSQL concept. Run the following command to deploy CoreOS-Prometheus operator. ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/monitoring/coreos-operator/demo-0.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/monitoring/coreos-operator/demo-0.yaml clusterrole "prometheus-operator" created serviceaccount "prometheus-operator" created clusterrolebinding "prometheus-operator" created @@ -70,7 +70,7 @@ servicemonitors.monitoring.coreos.com 11m Once the Prometheus operator CRDs are registered, run the following command to create a Prometheus. ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/monitoring/coreos-operator/demo-1.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/monitoring/coreos-operator/demo-1.yaml clusterrole "prometheus" created serviceaccount "prometheus" created clusterrolebinding "prometheus" created @@ -143,7 +143,7 @@ Here, Now create PostgreSQL with monitoring spec ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/postgres/monitoring/coreos-prom-postgres.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/postgres/monitoring/coreos-prom-postgres.yaml postgres "coreos-prom-postgres" created ``` diff --git a/docs/guides/postgres/private-registry/using-private-registry.md b/docs/guides/postgres/private-registry/using-private-registry.md index 9d8ac3a9a..029eb4734 100644 --- a/docs/guides/postgres/private-registry/using-private-registry.md +++ b/docs/guides/postgres/private-registry/using-private-registry.md @@ -49,7 +49,7 @@ For Postgres, push the following images to your private registry. ```console $ export DOCKER_REGISTRY= -$ docker pull kubedb/operator:0.8.0 ; docker tag kubedb/operator:0.8.0 $DOCKER_REGISTRY/operator:0.8.0 ; docker push $DOCKER_REGISTRY/operator:0.8.0 +$ docker pull kubedb/operator:0.9.0-beta.0 ; docker tag kubedb/operator:0.9.0-beta.0 $DOCKER_REGISTRY/operator:0.9.0-beta.0 ; docker push $DOCKER_REGISTRY/operator:0.9.0-beta.0 $ docker pull kubedb/postgres:9.6 ; docker tag kubedb/postgres:9.6 $DOCKER_REGISTRY/postgres:9.6 ; docker push $DOCKER_REGISTRY/postgres:9.6 $ docker pull kubedb/postgres-tools:9.6 ; docker tag kubedb/postgres-tools:9.6 $DOCKER_REGISTRY/postgres-tools:9.6 ; docker push $DOCKER_REGISTRY/postgres-tools:9.6 ``` @@ -108,7 +108,7 @@ spec: Now run the command to create this Postgres object: ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/postgres/private-registry/pvt-reg-postgres.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/postgres/private-registry/pvt-reg-postgres.yaml postgres "pvt-reg-postgres" created ``` diff --git a/docs/guides/postgres/quickstart/quickstart.md b/docs/guides/postgres/quickstart/quickstart.md index 6d938b1be..d3926f51a 100644 --- a/docs/guides/postgres/quickstart/quickstart.md +++ b/docs/guides/postgres/quickstart/quickstart.md @@ -42,7 +42,7 @@ This tutorial will also use a pgAdmin to connect and test PostgreSQL database, o Run the following command to prepare your cluster for this tutorial ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/postgres/quickstart/pgadmin.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/postgres/quickstart/pgadmin.yaml deployment "pgadmin" created service "pgadmin" created @@ -97,7 +97,7 @@ Here, - `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. You can specify any StorageClass available in your cluster with appropriate resource requests. Since release 0.8.0, a storage spec is required for MySQL. ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/postgres/quickstart/quick-postgres.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/postgres/quickstart/quick-postgres.yaml postgres "quick-postgres" created ``` @@ -331,7 +331,7 @@ In this tutorial, the DormantDatabase `quick-postgres` can be resumed by creatin The below command will resume the DormantDatabase `quick-postgres` ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/postgres/quickstart/quick-postgres.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/postgres/quickstart/quick-postgres.yaml postgres "quick-postgres" created ``` diff --git a/docs/guides/postgres/quickstart/rbac.md b/docs/guides/postgres/quickstart/rbac.md index 2f4988a49..6ec9d77b7 100644 --- a/docs/guides/postgres/quickstart/rbac.md +++ b/docs/guides/postgres/quickstart/rbac.md @@ -71,7 +71,7 @@ spec: Create above Postgres object with following command ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/postgres/quickstart/quick-postgres.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/postgres/quickstart/quick-postgres.yaml postgres "quick-postgres" created ``` diff --git a/docs/guides/postgres/snapshot/continuous_archiving.md b/docs/guides/postgres/snapshot/continuous_archiving.md index 4fbd95521..39c2d3a80 100644 --- a/docs/guides/postgres/snapshot/continuous_archiving.md +++ b/docs/guides/postgres/snapshot/continuous_archiving.md @@ -146,7 +146,7 @@ To configure this backend, following parameters are available: Now create this Postgres object with Continuous Archiving support. ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/postgres/snapshot/wal-postgres.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/postgres/snapshot/wal-postgres.yaml postgres "wal-postgres" created ``` diff --git a/docs/guides/postgres/snapshot/instant_backup.md b/docs/guides/postgres/snapshot/instant_backup.md index a69e0599a..74fd4237c 100644 --- a/docs/guides/postgres/snapshot/instant_backup.md +++ b/docs/guides/postgres/snapshot/instant_backup.md @@ -62,7 +62,7 @@ spec: If Postgres object `script-postgres` doesn't exists, create it first. ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/postgres/initialization/script-postgres.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/postgres/initialization/script-postgres.yaml postgres "script-postgres" created ``` @@ -164,7 +164,7 @@ To lean how to configure other storage destinations for snapshot data, please vi Now, create the Snapshot object. ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/postgres/snapshot/instant-snapshot.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/postgres/snapshot/instant-snapshot.yaml snapshot "instant-snapshot" created ``` diff --git a/docs/guides/postgres/snapshot/scheduled_backup.md b/docs/guides/postgres/snapshot/scheduled_backup.md index 94c14de0d..631695b56 100644 --- a/docs/guides/postgres/snapshot/scheduled_backup.md +++ b/docs/guides/postgres/snapshot/scheduled_backup.md @@ -93,7 +93,7 @@ Here, > Note: Secret object must be in the same namespace as Postgres, `scheduled-pg`, in this case. ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/postgres/snapshot/scheduled-pg.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/postgres/snapshot/scheduled-pg.yaml postgres "scheduled-pg" created ``` diff --git a/docs/guides/redis/README.md b/docs/guides/redis/README.md index 8c8a2a171..d504ec7e3 100644 --- a/docs/guides/redis/README.md +++ b/docs/guides/redis/README.md @@ -32,12 +32,13 @@ aliases: ## Supported Redis Versions -| KubeDB Version | Redis:4 | -|:--------------:|:--------:| -| 0.1.0 - 0.7.0 | ✗ | -| 0.8.0-beta.2 | ✓ | -| 0.8.0-rc.0 | ✓ | -| 0.8.0 | ✓ | +| KubeDB Version | Redis:4.0.6 | +|:--------------:|:------------:| +| 0.1.0 - 0.7.0 | ✗ | +| 0.8.0-beta.2 | ✓ | +| 0.8.0-rc.0 | ✓ | +| 0.8.0 | ✓ | +| 0.8.0-beta.2 | ✓ |
diff --git a/docs/guides/redis/custom-config/using-custom-config.md b/docs/guides/redis/custom-config/using-custom-config.md index 1279c2525..c8f4a082d 100644 --- a/docs/guides/redis/custom-config/using-custom-config.md +++ b/docs/guides/redis/custom-config/using-custom-config.md @@ -81,7 +81,7 @@ metadata: Now, create Redis crd specifying `spec.configSource` field. ```console -$ kubectl apply -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/redis/custom-config/redis-custom.yaml +$ kubectl apply -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/redis/custom-config/redis-custom.yaml redis.kubedb.com "custom-redis" created ``` diff --git a/docs/guides/redis/monitoring/using-builtin-prometheus.md b/docs/guides/redis/monitoring/using-builtin-prometheus.md index 7f31b0990..14923f874 100644 --- a/docs/guides/redis/monitoring/using-builtin-prometheus.md +++ b/docs/guides/redis/monitoring/using-builtin-prometheus.md @@ -62,7 +62,7 @@ spec: ``` ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/redis/monitoring/builtin-prometheus/demo-1.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/redis/monitoring/builtin-prometheus/demo-1.yaml redis "redis-mon-prometheus" created ``` @@ -227,7 +227,7 @@ data: ``` ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/monitoring/builtin-prometheus/demo-1.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/monitoring/builtin-prometheus/demo-1.yaml configmap "prometheus-server-conf" created ``` @@ -274,7 +274,7 @@ spec: Run the following command to deploy prometheus-server ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/monitoring/builtin-prometheus/demo-2.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/monitoring/builtin-prometheus/demo-2.yaml clusterrole "prometheus-server" created serviceaccount "prometheus-server" created clusterrolebinding "prometheus-server" created diff --git a/docs/guides/redis/monitoring/using-coreos-prometheus-operator.md b/docs/guides/redis/monitoring/using-coreos-prometheus-operator.md index 3d87493c2..976ea44cc 100644 --- a/docs/guides/redis/monitoring/using-coreos-prometheus-operator.md +++ b/docs/guides/redis/monitoring/using-coreos-prometheus-operator.md @@ -30,7 +30,7 @@ Note that the yaml files that are used in this tutorial, stored in [docs/example Run the following command to deploy CoreOS-Prometheus operator. ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/monitoring/coreos-operator/demo-0.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/monitoring/coreos-operator/demo-0.yaml namespace "demo" created clusterrole "prometheus-operator" created serviceaccount "prometheus-operator" created @@ -52,7 +52,7 @@ servicemonitors.monitoring.coreos.com 11m Once the Prometheus operator CRDs are registered, run the following command to create a Prometheus. ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/monitoring/coreos-operator/demo-1.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/monitoring/coreos-operator/demo-1.yaml clusterrole "prometheus" created serviceaccount "prometheus" created clusterrolebinding "prometheus" created @@ -153,7 +153,7 @@ __Known Limitations:__ If the database password is updated, exporter must be res Run the following command to deploy the above `Redis` CRD object. ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/redis/monitoring/coreos-operator/demo-1.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/redis/monitoring/coreos-operator/demo-1.yaml redis "redis-mon-coreos" created ``` diff --git a/docs/guides/redis/private-registry/using-private-registry.md b/docs/guides/redis/private-registry/using-private-registry.md index 5464a2200..ca39492de 100644 --- a/docs/guides/redis/private-registry/using-private-registry.md +++ b/docs/guides/redis/private-registry/using-private-registry.md @@ -30,7 +30,7 @@ You have to push the required images from KubeDB's [Docker hub account](https:// ```console $ export DOCKER_REGISTRY= -$ docker pull kubedb/operator:0.8.0 ; docker tag kubedb/operator:0.8.0 $DOCKER_REGISTRY/operator:0.8.0 ; docker push $DOCKER_REGISTRY/operator:0.8.0 +$ docker pull kubedb/operator:0.9.0-beta.0 ; docker tag kubedb/operator:0.9.0-beta.0 $DOCKER_REGISTRY/operator:0.9.0-beta.0 ; docker push $DOCKER_REGISTRY/operator:0.9.0-beta.0 $ docker pull kubedb/redis:4 ; docker tag kubedb/redis:4 $DOCKER_REGISTRY/redis:4 ; docker push $DOCKER_REGISTRY/redis:4 ``` @@ -102,7 +102,7 @@ spec: Now run the command to deploy this `Redis` object: ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/redis/private-registry/demo-2.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/redis/private-registry/demo-2.yaml redis "redis-pvt-reg" created ``` diff --git a/docs/guides/redis/quickstart/quickstart.md b/docs/guides/redis/quickstart/quickstart.md index ab2c19921..db8bba9d9 100644 --- a/docs/guides/redis/quickstart/quickstart.md +++ b/docs/guides/redis/quickstart/quickstart.md @@ -64,7 +64,7 @@ spec: ``` ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/redis/quickstart/demo-1.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/redis/quickstart/demo-1.yaml redis "redis-quickstart" created ``` @@ -267,7 +267,7 @@ In this tutorial, the dormant database can be resumed by creating original `Redi The below command will resume the DormantDatabase `redis-quickstart`. ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0/docs/examples/redis/quickstart/demo-1.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/redis/quickstart/demo-1.yaml redis "redis-quickstart" created ``` diff --git a/docs/reference/_index.md b/docs/reference/_index.md index a2467d63c..12895016d 100644 --- a/docs/reference/_index.md +++ b/docs/reference/_index.md @@ -2,9 +2,9 @@ title: Reference description: KubeDB CLI Reference menu: - docs_0.8.0: + docs_0.9.0-beta.0: identifier: reference name: Reference weight: 1000 -menu_name: docs_0.8.0 +menu_name: docs_0.9.0-beta.0 --- diff --git a/docs/reference/kubedb.md b/docs/reference/kubedb.md index 62e4c71ef..41b9bc22d 100644 --- a/docs/reference/kubedb.md +++ b/docs/reference/kubedb.md @@ -1,16 +1,16 @@ --- title: Kubedb menu: - docs_0.8.0: + docs_0.9.0-beta.0: identifier: kubedb name: Kubedb parent: reference weight: 0 -menu_name: docs_0.8.0 +menu_name: docs_0.9.0-beta.0 section_menu_id: reference aliases: - - /docs/0.8.0/reference/ + - /docs/0.9.0-beta.0/reference/ --- ## kubedb diff --git a/docs/reference/kubedb_create.md b/docs/reference/kubedb_create.md index 4aec68c4c..d003d34a7 100644 --- a/docs/reference/kubedb_create.md +++ b/docs/reference/kubedb_create.md @@ -1,11 +1,11 @@ --- title: Kubedb Create menu: - docs_0.8.0: + docs_0.9.0-beta.0: identifier: kubedb-create name: Kubedb Create parent: reference -menu_name: docs_0.8.0 +menu_name: docs_0.9.0-beta.0 section_menu_id: reference --- ## kubedb create diff --git a/docs/reference/kubedb_delete.md b/docs/reference/kubedb_delete.md index bbc1a8f51..6cb808d67 100644 --- a/docs/reference/kubedb_delete.md +++ b/docs/reference/kubedb_delete.md @@ -1,11 +1,11 @@ --- title: Kubedb Delete menu: - docs_0.8.0: + docs_0.9.0-beta.0: identifier: kubedb-delete name: Kubedb Delete parent: reference -menu_name: docs_0.8.0 +menu_name: docs_0.9.0-beta.0 section_menu_id: reference --- ## kubedb delete diff --git a/docs/reference/kubedb_describe.md b/docs/reference/kubedb_describe.md index 3822f0b1a..6208eacf3 100644 --- a/docs/reference/kubedb_describe.md +++ b/docs/reference/kubedb_describe.md @@ -1,11 +1,11 @@ --- title: Kubedb Describe menu: - docs_0.8.0: + docs_0.9.0-beta.0: identifier: kubedb-describe name: Kubedb Describe parent: reference -menu_name: docs_0.8.0 +menu_name: docs_0.9.0-beta.0 section_menu_id: reference --- ## kubedb describe diff --git a/docs/reference/kubedb_edit.md b/docs/reference/kubedb_edit.md index 87f9567ff..317f8c49e 100644 --- a/docs/reference/kubedb_edit.md +++ b/docs/reference/kubedb_edit.md @@ -1,11 +1,11 @@ --- title: Kubedb Edit menu: - docs_0.8.0: + docs_0.9.0-beta.0: identifier: kubedb-edit name: Kubedb Edit parent: reference -menu_name: docs_0.8.0 +menu_name: docs_0.9.0-beta.0 section_menu_id: reference --- ## kubedb edit @@ -35,16 +35,18 @@ kubedb edit (RESOURCE/NAME | -f FILENAME) ### Options ``` - -f, --filename strings Filename, directory, or URL to files to use to edit the resource - -h, --help help for edit - --include-uninitialized If true, the kubectl command applies to uninitialized objects. If explicitly set to false, this flag overrides other flags that make the kubectl commands apply to uninitialized objects, e.g., "--all". Objects with empty metadata.initializers are regarded as initialized. - -o, --output string Output format. One of: json|yaml|wide|name|custom-columns=...|custom-columns-file=...|go-template=...|go-template-file=...|jsonpath=...|jsonpath-file=... See custom columns [http://kubernetes.io/docs/user-guide/kubectl-overview/#custom-columns], golang template [http://golang.org/pkg/text/template/#pkg-overview] and jsonpath template [http://kubernetes.io/docs/user-guide/jsonpath]. - --output-patch Output the patch if the resource is edited. - --record Record current kubectl command in the resource annotation. If set to false, do not record the command. If set to true, record the command. If not set, default to updating the existing annotation value only if one already exists. - -R, --recursive Process the directory used in -f, --filename recursively. Useful when you want to manage related manifests organized within the same directory. - --save-config If true, the configuration of current object will be saved in its annotation. Otherwise, the annotation will be unchanged. This flag is useful when you want to perform kubectl apply on this object in the future. - --validate If true, use a schema to validate the input before sending it (default true) - --windows-line-endings Defaults to the line ending native to your platform. + --allow-missing-template-keys If true, ignore any errors in templates when a field or map key is missing in the template. Only applies to golang and jsonpath output formats. (default true) + -f, --filename strings Filename, directory, or URL to files to use to edit the resource + -h, --help help for edit + --include-uninitialized If true, the kubectl command applies to uninitialized objects. If explicitly set to false, this flag overrides other flags that make the kubectl commands apply to uninitialized objects, e.g., "--all". Objects with empty metadata.initializers are regarded as initialized. + -o, --output string Output format. One of: json|yaml|name|template|go-template|go-template-file|templatefile|jsonpath|jsonpath-file. + --output-patch Output the patch if the resource is edited. + --record Record current kubectl command in the resource annotation. If set to false, do not record the command. If set to true, record the command. If not set, default to updating the existing annotation value only if one already exists. + -R, --recursive Process the directory used in -f, --filename recursively. Useful when you want to manage related manifests organized within the same directory. + --save-config If true, the configuration of current object will be saved in its annotation. Otherwise, the annotation will be unchanged. This flag is useful when you want to perform kubectl apply on this object in the future. + --template string Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates [http://golang.org/pkg/text/template/#pkg-overview]. + --validate If true, use a schema to validate the input before sending it (default true) + --windows-line-endings Defaults to the line ending native to your platform. ``` ### Options inherited from parent commands diff --git a/docs/reference/kubedb_get.md b/docs/reference/kubedb_get.md index b19dcc0fb..27d64133f 100644 --- a/docs/reference/kubedb_get.md +++ b/docs/reference/kubedb_get.md @@ -1,11 +1,11 @@ --- title: Kubedb Get menu: - docs_0.8.0: + docs_0.9.0-beta.0: identifier: kubedb-get name: Kubedb Get parent: reference -menu_name: docs_0.8.0 +menu_name: docs_0.9.0-beta.0 section_menu_id: reference --- ## kubedb get diff --git a/docs/reference/kubedb_version.md b/docs/reference/kubedb_version.md index 71f4dd6d9..d57962489 100644 --- a/docs/reference/kubedb_version.md +++ b/docs/reference/kubedb_version.md @@ -1,11 +1,11 @@ --- title: Kubedb Version menu: - docs_0.8.0: + docs_0.9.0-beta.0: identifier: kubedb-version name: Kubedb Version parent: reference -menu_name: docs_0.8.0 +menu_name: docs_0.9.0-beta.0 section_menu_id: reference --- ## kubedb version diff --git a/docs/setup/install.md b/docs/setup/install.md index fd01cda89..fa909c055 100644 --- a/docs/setup/install.md +++ b/docs/setup/install.md @@ -37,7 +37,7 @@ To use `kubedb`, you will need to install KubeDB [operator](https://github.com/k To install KubeDB in your Kubernetes cluster, run the following command: ```console -$ curl -fsSL https://raw.githubusercontent.com/kubedb/cli/0.8.0/hack/deploy/kubedb.sh | bash +$ curl -fsSL https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/hack/deploy/kubedb.sh | bash ``` After successful installation, you should have a `kubedb-operator-***` pod running in the `kube-system` namespace. @@ -49,10 +49,10 @@ kubedb-operator-65d97f8cf9-8c9tj 2/2 Running 0 1m #### Customizing Installer -The installer script and associated yaml files can be found in the [/hack/deploy](https://github.com/kubedb/cli/tree/0.8.0/hack/deploy) folder. You can see the full list of flags available to installer using `-h` flag. +The installer script and associated yaml files can be found in the [/hack/deploy](https://github.com/kubedb/cli/tree/0.9.0-beta.0/hack/deploy) folder. You can see the full list of flags available to installer using `-h` flag. ```console -$ curl -fsSL https://raw.githubusercontent.com/kubedb/cli/0.8.0/hack/deploy/kubedb.sh | bash -s -- -h +$ curl -fsSL https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/hack/deploy/kubedb.sh | bash -s -- -h kubedb.sh - install kubedb operator kubedb.sh [options] @@ -76,7 +76,7 @@ options: If you would like to run KubeDB operator pod in `master` instances, pass the `--run-on-master` flag: ```console -$ curl -fsSL https://raw.githubusercontent.com/kubedb/cli/0.8.0/hack/deploy/kubedb.sh \ +$ curl -fsSL https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/hack/deploy/kubedb.sh \ | bash -s -- --run-on-master [--rbac] ``` @@ -84,7 +84,7 @@ KubeDB operator will be installed in a `kube-system` namespace by default. If yo ```console $ kubectl create namespace kubedb -$ curl -fsSL https://raw.githubusercontent.com/kubedb/cli/0.8.0/hack/deploy/kubedb.sh \ +$ curl -fsSL https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/hack/deploy/kubedb.sh \ | bash -s -- --namespace=kubedb [--run-on-master] [--rbac] ``` @@ -94,14 +94,14 @@ To pass the address of your private registry and optionally a image pull secret ```console $ kubectl create namespace kubedb -$ curl -fsSL https://raw.githubusercontent.com/kubedb/cli/0.8.0/hack/deploy/kubedb.sh \ +$ curl -fsSL https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/hack/deploy/kubedb.sh \ | bash -s -- --docker-registry=MY_REGISTRY [--image-pull-secret=SECRET_NAME] [--rbac] ``` KubeDB implements [validating and mutating admission webhooks](https://kubernetes.io/docs/admin/admission-controllers/#validatingadmissionwebhook-alpha-in-18-beta-in-19) for KubeDB CRDs. This is enabled by default for Kubernetes 1.9.0 or later releases. To disable this feature, pass the `--enable-validating-webhook=false` and `--enable-mutating-webhook=false` flag respectively. ```console -$ curl -fsSL https://raw.githubusercontent.com/kubedb/cli/0.8.0/hack/deploy/kubedb.sh \ +$ curl -fsSL https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/hack/deploy/kubedb.sh \ | bash -s -- --enable-validating-webhook=false --enable-mutating-webhook=false [--rbac] ``` @@ -110,7 +110,7 @@ KubeDB 0.9.0 or later releases can use status sub resource for CustomResourceDef KubeDB 0.9.0 or later installs a catalog of database versions. To disable this pass the `--install-catalog=none` flag. ```console -$ curl -fsSL https://raw.githubusercontent.com/kubedb/cli/0.8.0/hack/deploy/kubedb.sh \ +$ curl -fsSL https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/hack/deploy/kubedb.sh \ | bash -s -- --install-catalog=none [--rbac] ``` @@ -126,17 +126,17 @@ $ helm repo add appscode https://charts.appscode.com/stable/ $ helm repo update $ helm search appscode/kubedb NAME CHART VERSION APP VERSION DESCRIPTION -appscode/kubedb 0.8.0 0.8.0 KubeDB by AppsCode - Production ready databases... +appscode/kubedb 0.9.0-beta.0 0.9.0-beta.0 KubeDB by AppsCode - Production ready databases... # Kubernetes 1.9.x - 1.10.x -$ helm install appscode/kubedb --name kubedb-operator --version 0.8.0 \ +$ helm install appscode/kubedb --name kubedb-operator --version 0.9.0-beta.0 \ --namespace kube-system \ --set apiserver.ca="$(onessl get kube-ca)" \ --set apiserver.enableValidatingWebhook=true \ --set apiserver.enableMutatingWebhook=true # Kubernetes 1.11.0 or later -$ helm install appscode/kubedb --name kubedb-operator --version 0.8.0 \ +$ helm install appscode/kubedb --name kubedb-operator --version 0.9.0-beta.0 \ --namespace kube-system \ --set apiserver.ca="$(onessl get kube-ca)" \ --set apiserver.enableValidatingWebhook=true \ @@ -206,12 +206,12 @@ KubeDB provides a CLI to work with database objects. Download pre-built binaries ```console # Linux amd 64-bit -wget -O kubedb https://github.com/kubedb/cli/releases/download/0.8.0/kubedb-linux-amd64 \ +wget -O kubedb https://github.com/kubedb/cli/releases/download/0.9.0-beta.0/kubedb-linux-amd64 \ && chmod +x kubedb \ && sudo mv kubedb /usr/local/bin/ # Mac 64-bit -wget -O kubedb https://github.com/kubedb/cli/releases/download/0.8.0/kubedb-darwin-amd64 \ +wget -O kubedb https://github.com/kubedb/cli/releases/download/0.9.0-beta.0/kubedb-darwin-amd64 \ && chmod +x kubedb \ && sudo mv kubedb /usr/local/bin/ ``` diff --git a/docs/setup/uninstall.md b/docs/setup/uninstall.md index 46edf44f2..f8ce015a1 100644 --- a/docs/setup/uninstall.md +++ b/docs/setup/uninstall.md @@ -17,7 +17,7 @@ section_menu_id: setup To uninstall KubeDB operator, run the following command: ```console -$ curl -fsSL https://raw.githubusercontent.com/kubedb/cli/0.8.0/hack/deploy/kubedb.sh \ +$ curl -fsSL https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/hack/deploy/kubedb.sh \ | bash -s -- --uninstall [--namespace=NAMESPACE] + kubectl delete deployment -l app=kubedb -n kube-system diff --git a/glide.yaml b/glide.yaml index 2cd3d21ac..ba6811084 100644 --- a/glide.yaml +++ b/glide.yaml @@ -10,6 +10,8 @@ import: version: 0.9.0-beta.0 - package: github.com/kubedb/elasticsearch version: 0.9.0-beta.0 +- package: github.com/kubedb/etcd + version: 0.1.0-beta.0 - package: github.com/kubedb/postgres version: 0.9.0-beta.0 - package: github.com/kubedb/mysql diff --git a/hack/deploy/kubedb.sh b/hack/deploy/kubedb.sh index c29da23e6..e230de1c5 100755 --- a/hack/deploy/kubedb.sh +++ b/hack/deploy/kubedb.sh @@ -117,7 +117,7 @@ export KUBEDB_ENABLE_VALIDATING_WEBHOOK=false export KUBEDB_ENABLE_MUTATING_WEBHOOK=false export KUBEDB_CATALOG=${KUBEDB_CATALOG:-all} export KUBEDB_DOCKER_REGISTRY=kubedb -export KUBEDB_OPERATOR_TAG=0.8.0 +export KUBEDB_OPERATOR_TAG=0.9.0-beta.0 export KUBEDB_OPERATOR_NAME=operator export KUBEDB_IMAGE_PULL_SECRET= export KUBEDB_IMAGE_PULL_POLICY=IfNotPresent @@ -127,7 +127,7 @@ export KUBEDB_PURGE=0 export KUBEDB_ENABLE_STATUS_SUBRESOURCE=false export APPSCODE_ENV=${APPSCODE_ENV:-prod} -export SCRIPT_LOCATION="curl -fsSL https://raw.githubusercontent.com/kubedb/cli/0.8.0/" +export SCRIPT_LOCATION="curl -fsSL https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/" if [ "$APPSCODE_ENV" = "dev" ]; then detect_tag export SCRIPT_LOCATION="cat " diff --git a/hack/gendocs/main.go b/hack/gendocs/main.go index ac5777c35..ca95e5025 100644 --- a/hack/gendocs/main.go +++ b/hack/gendocs/main.go @@ -16,7 +16,7 @@ import ( ) const ( - version = "0.8.0" + version = "0.9.0-beta.0" ) var (