diff --git a/CHANGELOG.md b/CHANGELOG.md index 98f3b87e3..518b1cb4f 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,35 @@ # Change Log +## [Unreleased](https://github.com/kubedb/cli/tree/HEAD) + +[Full Changelog](https://github.com/kubedb/cli/compare/0.9.0-beta.1...HEAD) + +**Merged pull requests:** + +- Cleanup postgres and elasticsearch docs [\#336](https://github.com/kubedb/cli/pull/336) ([tamalsaha](https://github.com/tamalsaha)) +- Update chart and installer for webhook xray [\#335](https://github.com/kubedb/cli/pull/335) ([tamalsaha](https://github.com/tamalsaha)) +- Update kubernetes client libraries to 1.12.0 [\#334](https://github.com/kubedb/cli/pull/334) ([tamalsaha](https://github.com/tamalsaha)) +- Update dependencies to kubernetes 1.12.0 [\#333](https://github.com/kubedb/cli/pull/333) ([tamalsaha](https://github.com/tamalsaha)) +- Fix addition expression on installer script [\#332](https://github.com/kubedb/cli/pull/332) ([the-redback](https://github.com/the-redback)) +- Updated Snapshot concept for 0.9.0 [\#331](https://github.com/kubedb/cli/pull/331) ([the-redback](https://github.com/the-redback)) +- Updated Memcached docs for 0.9.0 [\#330](https://github.com/kubedb/cli/pull/330) ([the-redback](https://github.com/the-redback)) +- Add appdatalog to forced dep list [\#329](https://github.com/kubedb/cli/pull/329) ([tamalsaha](https://github.com/tamalsaha)) +- Add Support for Elasticsearch 6.4 [\#328](https://github.com/kubedb/cli/pull/328) ([hossainemruz](https://github.com/hossainemruz)) +- Add RBAC permission for appcatalog [\#327](https://github.com/kubedb/cli/pull/327) ([tamalsaha](https://github.com/tamalsaha)) +- Add validation webhook for Namespace deletion [\#326](https://github.com/kubedb/cli/pull/326) ([tamalsaha](https://github.com/tamalsaha)) +- Support LogLevel in chart [\#325](https://github.com/kubedb/cli/pull/325) ([tamalsaha](https://github.com/tamalsaha)) +- Added missing chart of mysql:8-v1 catalog [\#324](https://github.com/kubedb/cli/pull/324) ([the-redback](https://github.com/the-redback)) +- Update dep list [\#323](https://github.com/kubedb/cli/pull/323) ([tamalsaha](https://github.com/tamalsaha)) +- Fix small typo in docs/README.md [\#322](https://github.com/kubedb/cli/pull/322) ([CemalUnal](https://github.com/CemalUnal)) +- Updated Redis doc for 0.9.0 [\#321](https://github.com/kubedb/cli/pull/321) ([the-redback](https://github.com/the-redback)) +- Format user roles [\#320](https://github.com/kubedb/cli/pull/320) ([tamalsaha](https://github.com/tamalsaha)) +- Always use json syntax for verbs in installers [\#319](https://github.com/kubedb/cli/pull/319) ([tamalsaha](https://github.com/tamalsaha)) +- Start next dev cycle [\#317](https://github.com/kubedb/cli/pull/317) ([tamalsaha](https://github.com/tamalsaha)) +- Updated MySQL doc for 0.9.0 [\#310](https://github.com/kubedb/cli/pull/310) ([the-redback](https://github.com/the-redback)) +- MongoDB docs updated for 0.9.0 [\#304](https://github.com/kubedb/cli/pull/304) ([the-redback](https://github.com/the-redback)) +- Update docs for release 0.9.0 \(Elasticsearch\) [\#303](https://github.com/kubedb/cli/pull/303) ([hossainemruz](https://github.com/hossainemruz)) +- Update docs for release 0.9.0 \(Postgres\) [\#280](https://github.com/kubedb/cli/pull/280) ([hossainemruz](https://github.com/hossainemruz)) + ## [0.9.0-beta.1](https://github.com/kubedb/cli/tree/0.9.0-beta.1) (2018-09-30) [Full Changelog](https://github.com/kubedb/cli/compare/0.9.0-beta.0...0.9.0-beta.1) diff --git a/README.md b/README.md index 99a1e0055..208b89dca 100644 --- a/README.md +++ b/README.md @@ -37,7 +37,7 @@ Please pick a version of KubeDB that matches your Kubernetes installation. | KubeDB Version | Docs | Kubernetes Version | |------------------------------------------------------------------------------------|---------------------------------------------------------------------|--------------------| -| [0.9.0-beta.1](https://github.com/kubedb/cli/releases/tag/0.9.0-beta.1) (uses CRD) | [User Guide](https://github.com/kubedb/cli/tree/0.9.0-beta.1/docs) | 1.9.x + (for qa) | +| [0.9.0-rc.0](https://github.com/kubedb/cli/releases/tag/0.9.0-rc.0) (uses CRD) | [User Guide](https://github.com/kubedb/cli/tree/0.9.0-rc.0/docs) | 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 | diff --git a/chart/kubedb-catalog/Chart.yaml b/chart/kubedb-catalog/Chart.yaml index 20a3212f3..1982b0135 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.9.0-beta.1 -appVersion: 0.9.0-beta.1 +version: 0.9.0-rc.0 +appVersion: 0.9.0-rc.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 3838a492e..8e7f09fb2 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.9.0-beta.1 -appVersion: 0.9.0-beta.1 +version: 0.9.0-rc.0 +appVersion: 0.9.0-rc.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 d9f2e47ae..b23f5f4e5 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.9.0-beta.1` | +| `kubedb.tag` | Kubedb operator container image tag | `0.9.0-rc.0` | | `cleaner.registry` | Docker registry used to pull Webhook cleaner image | `appscode` | | `cleaner.repository` | Webhook cleaner container image | `kubectl` | | `cleaner.tag` | Webhook cleaner container image tag | `v1.11` | diff --git a/chart/kubedb/values.yaml b/chart/kubedb/values.yaml index 17614a00a..1ed3267e3 100644 --- a/chart/kubedb/values.yaml +++ b/chart/kubedb/values.yaml @@ -7,7 +7,7 @@ replicaCount: 1 kubedb: registry: kubedb repository: operator - tag: 0.9.0-beta.1 + tag: 0.9.0-rc.0 cleaner: registry: appscode repository: kubectl diff --git a/docs/CONTRIBUTING.md b/docs/CONTRIBUTING.md index b52156c16..814d478d1 100644 --- a/docs/CONTRIBUTING.md +++ b/docs/CONTRIBUTING.md @@ -2,16 +2,16 @@ title: Contributing | KubeDB description: Contributing menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: contributing-cli name: Contributing parent: welcome weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: welcome -url: /docs/0.8.0/welcome/contributing/ +url: /docs/0.9.0-rc.0/welcome/contributing/ aliases: - - /docs/0.8.0/CONTRIBUTING/ + - /docs/0.9.0-rc.0/CONTRIBUTING/ --- # Contribution Guidelines diff --git a/docs/README.md b/docs/README.md index 858062921..ffeb5be61 100644 --- a/docs/README.md +++ b/docs/README.md @@ -2,17 +2,17 @@ title: Welcome | KubeDB description: Welcome to KubeDB menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: readme-cli name: Readme parent: welcome weight: -1 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: welcome -url: /docs/0.8.0/welcome/ +url: /docs/0.9.0-rc.0/welcome/ aliases: - - /docs/0.8.0/ - - /docs/0.8.0/README/ + - /docs/0.9.0-rc.0/ + - /docs/0.9.0-rc.0/README/ --- # Welcome diff --git a/docs/_index.md b/docs/_index.md index c26a296d3..e93a38783 100644 --- a/docs/_index.md +++ b/docs/_index.md @@ -1,9 +1,9 @@ --- title: KubeDB menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: welcome name: Welcome weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/concepts/README.md b/docs/concepts/README.md index 02172c85f..a758adfa4 100644 --- a/docs/concepts/README.md +++ b/docs/concepts/README.md @@ -1,16 +1,16 @@ --- title: Concepts | KubeDB menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: concepts-readme name: Readme parent: concepts weight: -1 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: concepts -url: /docs/0.8.0/concepts/ +url: /docs/0.9.0-rc.0/concepts/ aliases: - - /docs/0.8.0/concepts/README/ + - /docs/0.9.0-rc.0/concepts/README/ --- # Concepts diff --git a/docs/concepts/_index.md b/docs/concepts/_index.md index 7f903793c..12e085870 100644 --- a/docs/concepts/_index.md +++ b/docs/concepts/_index.md @@ -2,9 +2,9 @@ title: Concepts description: Concepts menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: concepts name: Concepts weight: 20 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/concepts/catalog/_index.md b/docs/concepts/catalog/_index.md index cad8dc295..c00fdda69 100644 --- a/docs/concepts/catalog/_index.md +++ b/docs/concepts/catalog/_index.md @@ -2,10 +2,10 @@ title: KubeDB Catalog | KubeDB description: Database Version CRD menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: catalog parent: concepts name: Catalog weight: 20 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/concepts/catalog/elasticsearch.md b/docs/concepts/catalog/elasticsearch.md index a1aaea0c2..32774eb23 100644 --- a/docs/concepts/catalog/elasticsearch.md +++ b/docs/concepts/catalog/elasticsearch.md @@ -1,12 +1,12 @@ --- title: ElasticsearchVersion menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: elasticsearh-version name: ElasticsearchVersion parent: catalog weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: concepts --- @@ -57,7 +57,7 @@ We modify original Elasticsearch docker image to support additional features lik ### spec.deprecated -`spec.deprecated` is an optional field that specifies whether the docker images specified here is supported by the current KubeDB operator. For example, we have modified `kubedb/elasticsearch:6.2.4` docker image to support custom configuration and re-tagged as `kubedb/elasticsearch:6.2.4-v1`. Now, KubeDB `0.9.0` supports providing custom configuration which required `kubedb/elasticsearch:6.2.4-v1` docker image. So, we have marked `kubedb/elasticsearch:6.2.4` as deprecated in KubeDB `0.9.0`. +`spec.deprecated` is an optional field that specifies whether the docker images specified here is supported by the current KubeDB operator. For example, we have modified `kubedb/elasticsearch:6.2.4` docker image to support custom configuration and re-tagged as `kubedb/elasticsearch:6.2.4-v1`. Now, KubeDB `0.9.0-rc.0` supports providing custom configuration which required `kubedb/elasticsearch:6.2.4-v1` docker image. So, we have marked `kubedb/elasticsearch:6.2.4` as deprecated in KubeDB `0.9.0-rc.0`. The default value of this field is `false`. If `spec.depcrecated` is set `true`, KubeDB operator will not create the database and other respective resources for this version. diff --git a/docs/concepts/catalog/memcached.md b/docs/concepts/catalog/memcached.md index a2114ba8f..180bf11da 100644 --- a/docs/concepts/catalog/memcached.md +++ b/docs/concepts/catalog/memcached.md @@ -1,12 +1,12 @@ --- title: MemcachedVersion menu: - docs_0.9.0-beta.1: + docs_0.9.0-rc.0: identifier: memcached-version name: MemcachedVersion parent: catalog weight: 30 -menu_name: docs_0.9.0-beta.1 +menu_name: docs_0.9.0-rc.0 section_menu_id: concepts --- @@ -47,7 +47,7 @@ We follow this convention for naming MemcachedVersion crd: - Name format: `{Original Memcached image version}-{modification tag}` -We modify original Memcached docker image to support additional features. An image with higher modification tag will have more feature than the images with lower modification tag. Hence, it is recommended to use MemcachedVersion crd with highest modification tag to enjoy latest features. +We modify original Memcached docker image to support additional features. An image with higher modification tag will have more feature than the images with lower modification tag. Hence, it is recommended to use MemcachedVersion crd with highest modification tag to take advantage of the latest features. ### spec.version @@ -55,7 +55,7 @@ We modify original Memcached docker image to support additional features. An ima ### spec.deprecated -`spec.deprecated` is an optional field that specifies whether the docker images specified here is supported by the current KubeDB operator. For example, we have modified `kubedb/memcached:1.5.4` docker image to support custom configuration and re-tagged as `kubedb/memcached:1.5.4-v1`. Now, KubeDB `0.9.0` supports providing custom configuration which required `kubedb/memcached:1.5.4-v1` docker image. So, we have marked `kubedb/memcached:1.5.4` as deprecated for KubeDB `0.9.0`. +`spec.deprecated` is an optional field that specifies whether the docker images specified here is supported by the current KubeDB operator. For example, we have modified `kubedb/memcached:1.5.4` docker image to support custom configuration and re-tagged as `kubedb/memcached:1.5.4-v1`. Now, KubeDB `0.9.0-rc.0` supports providing custom configuration which required `kubedb/memcached:1.5.4-v1` docker image. So, we have marked `kubedb/memcached:1.5.4` as deprecated for KubeDB `0.9.0-rc.0`. The default value of this field is `false`. If `spec.depcrecated` is set `true`, KubeDB operator will not create the database and other respective resources for this version. diff --git a/docs/concepts/catalog/mongodb.md b/docs/concepts/catalog/mongodb.md index 283bc533e..53651abb2 100644 --- a/docs/concepts/catalog/mongodb.md +++ b/docs/concepts/catalog/mongodb.md @@ -1,12 +1,12 @@ --- title: MongoDBVersion menu: - docs_0.8.0: + docs_0.9.0-rc.0: identifier: mongodb-version name: MongoDBVersion parent: catalog weight: 30 -menu_name: docs_0.8.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: concepts --- @@ -50,7 +50,7 @@ We follow this convention for naming MongoDBVersion crd: - Name format: `{Original PosgreSQL image verion}-{modification tag}` -We modify original MongoDB docker image to support MongoDB clustering and re-tag the image with v1,v2 etc. modification tag. An image with higher modification tag will have more feature than the images with lower modification tag. Hence, it is recommended to use MongoDBVersion crd with highest modification tag to enjoy the latest features. +We modify original MongoDB docker image to support MongoDB clustering and re-tag the image with v1, v2 etc. modification tag. An image with higher modification tag will have more feature than the images with lower modification tag. Hence, it is recommended to use MongoDBVersion crd with highest modification tag to enjoy the latest features. ### spec.version @@ -58,7 +58,7 @@ We modify original MongoDB docker image to support MongoDB clustering and re-tag ### spec.deprecated -`spec.deprecated` is an optional field that specifies whether the docker images specified here is supported by the current KubeDB operator. For example, we have modified `kubedb/mongo:3.6` docker image to support MongoDB clustering and re-tagged as `kubedb/mongo:3.6-v1`. So, we have marked `kubedb/mongo:3.6` as deprecated for KubeDB `0.9.0`. +`spec.deprecated` is an optional field that specifies whether the docker images specified here is supported by the current KubeDB operator. For example, we have modified `kubedb/mongo:3.6` docker image to support MongoDB clustering and re-tagged as `kubedb/mongo:3.6-v1`. So, we have marked `kubedb/mongo:3.6` as deprecated for KubeDB `0.9.0-rc.0`. The default value of this field is `false`. If `spec.depcrecated` is set to `true`, KubeDB operator will skip processing this CRD object and will add a event to the CRD object specifying that the DB version is deprecated. diff --git a/docs/concepts/catalog/mysql.md b/docs/concepts/catalog/mysql.md index 3af04156d..27c4d62d0 100644 --- a/docs/concepts/catalog/mysql.md +++ b/docs/concepts/catalog/mysql.md @@ -1,12 +1,12 @@ --- title: MySQLVersion menu: - docs_0.9.0-beta.1: + docs_0.9.0-rc.0: identifier: mysql-version name: MySQLVersion parent: catalog weight: 30 -menu_name: docs_0.9.0-beta.1 +menu_name: docs_0.9.0-rc.0 section_menu_id: concepts --- @@ -49,7 +49,7 @@ We follow this convention for naming MySQLVersion crd: - Name format: `{Original MySQL image version}-{modification tag}` -We modify original MySQL docker image to support additional features. An image with higher modification tag will have more feature than the images with lower modification tag. Hence, it is recommended to use MySQLVersion crd with highest modification tag to enjoy latest features. +We modify original MySQL docker image to support additional features. An image with higher modification tag will have more feature than the images with lower modification tag. Hence, it is recommended to use MySQLVersion crd with highest modification tag to take advantage of the latest features. ### spec.version @@ -57,7 +57,7 @@ We modify original MySQL docker image to support additional features. An image w ### spec.deprecated -`spec.deprecated` is an optional field that specifies whether the docker images specified here is supported by the current KubeDB operator. For example, we have modified `kubedb/mysql:8.0` docker image to support custom configuration and re-tagged as `kubedb/mysql:8.0-v1`. Now, KubeDB `0.9.0` supports providing custom configuration which required `kubedb/mysql:8.0-v1` docker image. So, we have marked `kubedb/mysql:8.0` as deprecated for KubeDB `0.9.0`. +`spec.deprecated` is an optional field that specifies whether the docker images specified here is supported by the current KubeDB operator. For example, we have modified `kubedb/mysql:8.0` docker image to support custom configuration and re-tagged as `kubedb/mysql:8.0-v1`. Now, KubeDB `0.9.0-rc.0` supports providing custom configuration which required `kubedb/mysql:8.0-v1` docker image. So, we have marked `kubedb/mysql:8.0` as deprecated for KubeDB `0.9.0-rc.0`. The default value of this field is `false`. If `spec.depcrecated` is set `true`, KubeDB operator will not create the database and other respective resources for this version. diff --git a/docs/concepts/catalog/postgres.md b/docs/concepts/catalog/postgres.md index d69f8fce2..399fe5864 100644 --- a/docs/concepts/catalog/postgres.md +++ b/docs/concepts/catalog/postgres.md @@ -1,12 +1,12 @@ --- title: PostgresVersion menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: postgres-version name: PostgresVersion parent: catalog weight: 30 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: concepts --- @@ -57,7 +57,7 @@ We modify original PostgreSQL docker image to support additional features like W ### spec.deprecated -`spec.deprecated` is an optional field that specifies whether the docker images specified here is supported by the current KubeDB operator. For example, we have modified `kubedb/postgres:10.2` docker image to support custom configuration and re-tagged as `kubedb/postgres:10.2-v1`. Now, KubeDB `0.9.0` supports providing custom configuration which required `kubedb/postgres:10.2-v1` docker image. So, we have marked `kubedb/postgres:10.2` as deprecated in KubeDB `0.9.0`. +`spec.deprecated` is an optional field that specifies whether the docker images specified here is supported by the current KubeDB operator. For example, we have modified `kubedb/postgres:10.2` docker image to support custom configuration and re-tagged as `kubedb/postgres:10.2-v1`. Now, KubeDB `0.9.0-rc.0` supports providing custom configuration which required `kubedb/postgres:10.2-v1` docker image. So, we have marked `kubedb/postgres:10.2` as deprecated in KubeDB `0.9.0-rc.0`. The default value of this field is `false`. If `spec.depcrecated` is set `true`, KubeDB operator will not create the database and other respective resources for this version. diff --git a/docs/concepts/catalog/redis.md b/docs/concepts/catalog/redis.md index 485b824da..1bf3e3c8f 100644 --- a/docs/concepts/catalog/redis.md +++ b/docs/concepts/catalog/redis.md @@ -1,12 +1,12 @@ --- title: RedisVersion menu: - docs_0.8.0: + docs_0.9.0-rc.0: identifier: redis-version name: RedisVersion parent: catalog weight: 30 -menu_name: docs_0.8.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: concepts --- @@ -47,7 +47,7 @@ We follow this convention for naming RedisVersion crd: - Name format: `{Original PosgreSQL image verion}-{modification tag}` -We modify original Redis docker image to support Redis clustering and re-tag the image with v1,v2 etc. modification tag. An image with higher modification tag will have more feature than the images with lower modification tag. Hence, it is recommended to use RedisVersion crd with highest modification tag to enjoy the latest features. +We modify original Redis docker image to support Redis clustering and re-tag the image with v1, v2 etc. modification tag. An image with higher modification tag will have more feature than the images with lower modification tag. Hence, it is recommended to use RedisVersion crd with highest modification tag to enjoy the latest features. ### spec.version diff --git a/docs/concepts/databases/_index.md b/docs/concepts/databases/_index.md index 398205537..8652444a3 100644 --- a/docs/concepts/databases/_index.md +++ b/docs/concepts/databases/_index.md @@ -2,10 +2,10 @@ title: Supported Databases | KubeDB description: Supported Databases menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: databases parent: concepts name: Supported Databases weight: 15 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/concepts/databases/elasticsearch.md b/docs/concepts/databases/elasticsearch.md index 58ab2b967..9eb567258 100644 --- a/docs/concepts/databases/elasticsearch.md +++ b/docs/concepts/databases/elasticsearch.md @@ -1,12 +1,12 @@ --- title: Elasticsearch menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: elasticsearch-db name: Elasticsearch parent: databases weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: concepts --- diff --git a/docs/concepts/databases/memcached.md b/docs/concepts/databases/memcached.md index 19f8b60e9..5273a29d7 100644 --- a/docs/concepts/databases/memcached.md +++ b/docs/concepts/databases/memcached.md @@ -1,12 +1,12 @@ --- title: Memcached menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: memcached-db name: Memcached parent: databases weight: 15 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: concepts --- @@ -202,7 +202,7 @@ Following table show what KubeDB does when you delete Memcached crd for differen | Behaviour | DoNotTerminate | Pause | Delete | WipeOut | | ----------------------------------- | :------------: | :------: | :------: | :------: | -| 1. Nullify Delete operation | ✓ | ✗ | ✗ | ✗ | +| 1. Block Delete operation | ✓ | ✗ | ✗ | ✗ | | 2. Create Dormant Database | ✗ | ✓ | ✗ | ✗ | | 3. Delete StatefulSet | ✗ | ✓ | ✓ | ✓ | | 4. Delete Services | ✗ | ✓ | ✓ | ✓ | diff --git a/docs/concepts/databases/mongodb.md b/docs/concepts/databases/mongodb.md index 44c4d6be0..011d4d248 100644 --- a/docs/concepts/databases/mongodb.md +++ b/docs/concepts/databases/mongodb.md @@ -1,12 +1,12 @@ --- title: MongoDB menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: mongodb-db name: MongoDB parent: databases weight: 20 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: concepts --- @@ -157,7 +157,7 @@ type: Opaque ### spec.storage -Since 0.9.0, If you set `spec.storageType:` to `Durable`, then `spec.storage` is a required field that specifies the StorageClass of PVCs dynamically allocated to store data for the 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 0.9.0-rc.0, If you set `spec.storageType:` to `Durable`, then `spec.storage` is a required field that specifies the StorageClass of PVCs dynamically allocated to store data for the 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.storage.storageClassName` is the name of the StorageClass used to provision PVCs. PVCs don’t necessarily have to request a class. A PVC with its storageClassName set equal to "" is always interpreted to be requesting a PV with no class, so it can only be bound to PVs with no class (no annotation or one set equal to ""). A PVC with no storageClassName is not quite the same and is treated differently by the cluster depending on whether the DefaultStorageClass admission plugin is turned on. - `spec.storage.accessModes` uses the same conventions as Kubernetes PVCs when requesting storage with specific access modes. @@ -381,7 +381,7 @@ Following table show what KubeDB does when you delete MongoDB crd for different | Behaviour | DoNotTerminate | Pause | Delete | WipeOut | | ----------------------------------- | :------------: | :------: | :------: | :------: | -| 1. Nullify Delete operation | ✓ | ✗ | ✗ | ✗ | +| 1. Block Delete operation | ✓ | ✗ | ✗ | ✗ | | 2. Create Dormant Database | ✗ | ✓ | ✗ | ✗ | | 3. Delete StatefulSet | ✗ | ✓ | ✓ | ✓ | | 4. Delete Services | ✗ | ✓ | ✓ | ✓ | diff --git a/docs/concepts/databases/mysql.md b/docs/concepts/databases/mysql.md index 906ebe736..00933081d 100644 --- a/docs/concepts/databases/mysql.md +++ b/docs/concepts/databases/mysql.md @@ -1,12 +1,12 @@ --- title: MySQL menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: mysql-db name: MySQL parent: databases weight: 25 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: concepts --- @@ -140,7 +140,7 @@ type: Opaque ### spec.storage -Since 0.9.0, If you set `spec.storageType:` to `Durable`, then `spec.storage` is a required field that specifies the StorageClass of PVCs dynamically allocated to store data for the 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 0.9.0-rc.0, If you set `spec.storageType:` to `Durable`, then `spec.storage` is a required field that specifies the StorageClass of PVCs dynamically allocated to store data for the 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.storage.storageClassName` is the name of the StorageClass used to provision PVCs. PVCs don’t necessarily have to request a class. A PVC with its storageClassName set equal to "" is always interpreted to be requesting a PV with no class, so it can only be bound to PVs with no class (no annotation or one set equal to ""). A PVC with no storageClassName is not quite the same and is treated differently by the cluster depending on whether the DefaultStorageClass admission plugin is turned on. - `spec.storage.accessModes` uses the same conventions as Kubernetes PVCs when requesting storage with specific access modes. @@ -360,7 +360,7 @@ Following table show what KubeDB does when you delete MySQL crd for different te | Behaviour | DoNotTerminate | Pause | Delete | WipeOut | | ----------------------------------- | :------------: | :------: | :------: | :------: | -| 1. Nullify Delete operation | ✓ | ✗ | ✗ | ✗ | +| 1. Block Delete operation | ✓ | ✗ | ✗ | ✗ | | 2. Create Dormant Database | ✗ | ✓ | ✗ | ✗ | | 3. Delete StatefulSet | ✗ | ✓ | ✓ | ✓ | | 4. Delete Services | ✗ | ✓ | ✓ | ✓ | diff --git a/docs/concepts/databases/postgres.md b/docs/concepts/databases/postgres.md index 953b7ab58..19d91e591 100644 --- a/docs/concepts/databases/postgres.md +++ b/docs/concepts/databases/postgres.md @@ -1,12 +1,12 @@ --- title: Postgres menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: postgres-db name: Postgres parent: databases weight: 30 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: concepts --- diff --git a/docs/concepts/databases/redis.md b/docs/concepts/databases/redis.md index e0d265e50..b921ba2de 100644 --- a/docs/concepts/databases/redis.md +++ b/docs/concepts/databases/redis.md @@ -1,12 +1,12 @@ --- title: Redis menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: redis-db name: Redis parent: databases weight: 35 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: concepts --- @@ -93,7 +93,7 @@ spec: ### spec.storage -Since 0.9.0, If you set `spec.storageType:` to `Durable`, then `spec.storage` is a required field that specifies the StorageClass of PVCs dynamically allocated to store data for the 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 0.9.0-rc.0, If you set `spec.storageType:` to `Durable`, then `spec.storage` is a required field that specifies the StorageClass of PVCs dynamically allocated to store data for the 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.storage.storageClassName` is the name of the StorageClass used to provision PVCs. PVCs don’t necessarily have to request a class. A PVC with its storageClassName set equal to "" is always interpreted to be requesting a PV with no class, so it can only be bound to PVs with no class (no annotation or one set equal to ""). A PVC with no storageClassName is not quite the same and is treated differently by the cluster depending on whether the DefaultStorageClass admission plugin is turned on. - `spec.storage.accessModes` uses the same conventions as Kubernetes PVCs when requesting storage with specific access modes. diff --git a/docs/concepts/snapshot.md b/docs/concepts/snapshot.md index b421d515a..57d92a848 100644 --- a/docs/concepts/snapshot.md +++ b/docs/concepts/snapshot.md @@ -1,12 +1,12 @@ --- title: Snapshot menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: snapshot-concepts name: Snapshot parent: concepts weight: 35 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: concepts --- diff --git a/docs/concepts/what-is-kubedb/_index.md b/docs/concepts/what-is-kubedb/_index.md index 8d652accd..c4682212f 100644 --- a/docs/concepts/what-is-kubedb/_index.md +++ b/docs/concepts/what-is-kubedb/_index.md @@ -2,10 +2,10 @@ title: What is KubeDB description: What is KubeDB menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: what-is-kubedb parent: concepts name: What is KubeDB weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/concepts/what-is-kubedb/overview.md b/docs/concepts/what-is-kubedb/overview.md index 5d124f471..0bbb961a6 100644 --- a/docs/concepts/what-is-kubedb/overview.md +++ b/docs/concepts/what-is-kubedb/overview.md @@ -2,12 +2,12 @@ title: KubeDB Overview description: KubeDB Overview menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: overview-concepts name: Overview parent: what-is-kubedb weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: concepts --- diff --git a/docs/examples/postgres/custom-version/postgresversion.yaml b/docs/examples/postgres/custom-version/postgresversion.yaml index 71b30e2e0..7abaf566f 100644 --- a/docs/examples/postgres/custom-version/postgresversion.yaml +++ b/docs/examples/postgres/custom-version/postgresversion.yaml @@ -7,6 +7,6 @@ spec: db: image: "myco/postgres:timescale-0.9.1" exporter: - image: "kubedb/operator:0.9.0-beta.0" + image: "kubedb/operator:0.9.0-rc.0" tools: image: "kubedb/postgres-tools:10.2-v1" diff --git a/docs/guides/README.md b/docs/guides/README.md index f7b0415d7..fe920cf6c 100644 --- a/docs/guides/README.md +++ b/docs/guides/README.md @@ -1,16 +1,16 @@ --- title: Guides | KubeDB menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: guides-readme name: Readme parent: guides weight: -1 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides -url: /docs/0.8.0/guides/ +url: /docs/0.9.0-rc.0/guides/ aliases: - - /docs/0.8.0/guides/README/ + - /docs/0.9.0-rc.0/guides/README/ --- # Guides diff --git a/docs/guides/_index.md b/docs/guides/_index.md index 7c0e6d646..051b85f6c 100644 --- a/docs/guides/_index.md +++ b/docs/guides/_index.md @@ -1,10 +1,10 @@ --- title: Guides | KubeDB menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: guides name: Guides weight: 40 pre: dropdown -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/elasticsearch/README.md b/docs/guides/elasticsearch/README.md index eaafa0018..4b29bf319 100644 --- a/docs/guides/elasticsearch/README.md +++ b/docs/guides/elasticsearch/README.md @@ -1,16 +1,16 @@ --- title: Elasticsearch menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: es-readme-elasticsearch name: Elasticsearch parent: es-elasticsearch-guides weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides -url: /docs/0.8.0/guides/elasticsearch/ +url: /docs/0.9.0-rc.0/guides/elasticsearch/ aliases: - - /docs/0.8.0/guides/elasticsearch/README/ + - /docs/0.9.0-rc.0/guides/elasticsearch/README/ --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -49,28 +49,29 @@ aliases: | -------------- | :---------------: | :---------------: | :---------------: | :---------------: | :---------------: | | 0.1.0 - 0.7.0 | ✓ | ✗ | ✗ | ✗ | ✗ | | 0.8.0 | ✗ | ✓ | ✓ | ✗ | ✗ | -| 0.9.0-beta.1 | ✗ | ✓ | ✓ | ✓ | ✓ | +| 0.9.0-rc.0 | ✗ | ✓ | ✓ | ✓ | ✓ | ## Supported ElasticsearchVersion CRD Here, ✓ means supported and ✗ means deprecated. -| ElasticsearchVersion | KubeDB: 0.9.0-beta.1 | -| -------------------- | :------------------: | -| 5.6 | ✗ | -| 5.6-v1 | ✓ | -| 5.6.4 | ✗ | -| 5.6.4-v1 | ✓ | -| 6.2 | ✗ | -| 6.2-v1 | ✓ | -| 6.2.4 | ✗ | -| 6.2.4-v1 | ✓ | -| 6.3 | ✗ | -| 6.3-v1 | ✓ | -| 6.3.0 | ✗ | -| 6.3.0-v1 | ✓ | -| 6.4-v1 | ✗ | -| 6.4.0-v1 | ✗ | +| NAME | VERSION | KubeDB: 0.9.0-rc.0 | +|----------|---------|--------------------| +| 5.6 | 5.6 | ✗ | +| 5.6-v1 | 5.6 | ✓ | +| 5.6.4 | 5.6.4 | ✗ | +| 5.6.4-v1 | 5.6.4 | ✓ | +| 6.2 | 6.2 | ✗ | +| 6.2-v1 | 6.2 | ✓ | +| 6.2.4 | 6.2.4 | ✗ | +| 6.2.4-v1 | 6.2.4 | ✓ | +| 6.3 | 6.3 | ✗ | +| 6.3-v1 | 6.3 | ✓ | +| 6.3.0 | 6.3.0 | ✗ | +| 6.3.0-v1 | 6.3.0 | ✓ | +| 6.4 | 6.4 | ✓ | +| 6.4.0 | 6.4.0 | ✓ | + ## External tools dependency diff --git a/docs/guides/elasticsearch/_index.md b/docs/guides/elasticsearch/_index.md index 974af0b8e..71ead0962 100644 --- a/docs/guides/elasticsearch/_index.md +++ b/docs/guides/elasticsearch/_index.md @@ -1,10 +1,10 @@ --- title: Elasticsearch menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: es-elasticsearch-guides name: Elasticsearch parent: guides weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/elasticsearch/cli/_index.md b/docs/guides/elasticsearch/cli/_index.md index 8bf641d0d..82859a544 100755 --- a/docs/guides/elasticsearch/cli/_index.md +++ b/docs/guides/elasticsearch/cli/_index.md @@ -1,10 +1,10 @@ --- title: CLI | KubeDB menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: es-cli-elasticsearch name: CLI parent: es-elasticsearch-guides weight: 65 -menu_name: docs_0.8.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/elasticsearch/cli/cli.md b/docs/guides/elasticsearch/cli/cli.md index 44d938b79..6db6b3cbe 100644 --- a/docs/guides/elasticsearch/cli/cli.md +++ b/docs/guides/elasticsearch/cli/cli.md @@ -1,12 +1,12 @@ --- title: CLI | KubeDB menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: es-cli-cli name: Quickstart parent: es-cli-elasticsearch weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- diff --git a/docs/guides/elasticsearch/clustering/_index.md b/docs/guides/elasticsearch/clustering/_index.md index e8bf1bb8a..151acc88e 100755 --- a/docs/guides/elasticsearch/clustering/_index.md +++ b/docs/guides/elasticsearch/clustering/_index.md @@ -1,10 +1,10 @@ --- title: Elasticsearch Clustering menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: es-clustering-elasticsearch name: Clustering parent: es-elasticsearch-guides weight: 20 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/elasticsearch/clustering/topology.md b/docs/guides/elasticsearch/clustering/topology.md index 63ad94915..90f2b0d4d 100644 --- a/docs/guides/elasticsearch/clustering/topology.md +++ b/docs/guides/elasticsearch/clustering/topology.md @@ -1,12 +1,12 @@ --- title: Elasticsearch Cluster Topology menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: es-topology-clustering name: Topology parent: es-clustering-elasticsearch weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -32,7 +32,7 @@ NAME STATUS AGE demo Active 5s ``` -> Note: Yaml files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/cli/tree/master/docs/examples/elasticsearch) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: Yaml files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/cli/tree/master/docs/examples/elasticsearch) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). ## Create multi-node Elasticsearch @@ -68,7 +68,7 @@ Here, Create example above with following command ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/elasticsearch/clustering/multi-node-es.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/elasticsearch/clustering/multi-node-es.yaml elasticsearch.kubedb.com/multi-node-es created ``` @@ -237,7 +237,7 @@ Here, Let's create this Elasticsearch object ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/elasticsearch/clustering/topology-es.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/elasticsearch/clustering/topology-es.yaml elasticsearch.kubedb.com/topology-es created ``` diff --git a/docs/guides/elasticsearch/custom-config/_index.md b/docs/guides/elasticsearch/custom-config/_index.md index f943eddaf..706ece995 100755 --- a/docs/guides/elasticsearch/custom-config/_index.md +++ b/docs/guides/elasticsearch/custom-config/_index.md @@ -1,10 +1,10 @@ --- title: Run Elasticsearch with Custom Configuration menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: es-custom-config name: Custom Configuration parent: es-elasticsearch-guides weight: 40 -menu_name: docs_0.8.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/elasticsearch/custom-config/overview.md b/docs/guides/elasticsearch/custom-config/overview.md index 11d907ffc..aa898d6f1 100644 --- a/docs/guides/elasticsearch/custom-config/overview.md +++ b/docs/guides/elasticsearch/custom-config/overview.md @@ -1,12 +1,12 @@ --- title: Run Elasticsearch with Custom Configuration menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: es-custom-config-overview name: Overview parent: es-custom-config weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- > New to KubeDB? Please start [here](/docs/concepts/README.md). diff --git a/docs/guides/elasticsearch/custom-config/with-topology.md b/docs/guides/elasticsearch/custom-config/with-topology.md index d29102926..9a2520df9 100644 --- a/docs/guides/elasticsearch/custom-config/with-topology.md +++ b/docs/guides/elasticsearch/custom-config/with-topology.md @@ -1,12 +1,12 @@ --- title: Using Custom Configuration in Elasticsearch with Topology menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: es-custom-config-with-topology name: With Topology parent: es-custom-config weight: 20 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -34,7 +34,7 @@ NAME STATUS AGE demo Active 5s ``` -> Note: Yaml files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/cli/tree/master/docs/examples/elasticsearch) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: Yaml files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/cli/tree/master/docs/examples/elasticsearch) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). ## Use Custom Configuration @@ -120,7 +120,7 @@ metadata: Now, create an Elasticsearch crd with topology specified, ```console -$ kubectl apply -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/elasticsearch/custom-config/es-custom-with-topology.yaml +$ kubectl apply -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.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 c729a9891..db3486310 100644 --- a/docs/guides/elasticsearch/custom-config/without-topology.md +++ b/docs/guides/elasticsearch/custom-config/without-topology.md @@ -1,12 +1,12 @@ --- title: Using Custom Configuration in Elasticsearch without Topology menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: es-custom-config-without-topology name: Without Topology parent: es-custom-config weight: 30 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -34,7 +34,7 @@ NAME STATUS AGE demo Active 5s ``` -> Note: Yaml files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/cli/tree/master/docs/examples/elasticsearch) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: Yaml files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/cli/tree/master/docs/examples/elasticsearch) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). ## Use Custom Configuration @@ -111,7 +111,7 @@ metadata: Now, create an Elasticsearch crd without topology, ```console -$ kubectl apply -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/elasticsearch/custom-config/es-custom.yaml +$ kubectl apply -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/elasticsearch/custom-config/es-custom.yaml elasticsearch.kubedb.com/custom-elasticsearch created ``` diff --git a/docs/guides/elasticsearch/initialization/_index.md b/docs/guides/elasticsearch/initialization/_index.md index efa10c1d6..21651a74c 100755 --- a/docs/guides/elasticsearch/initialization/_index.md +++ b/docs/guides/elasticsearch/initialization/_index.md @@ -1,10 +1,10 @@ --- title: Elasticsearch Initialization menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: es-initialization-elasticsearch name: Initialization parent: es-elasticsearch-guides weight: 30 -menu_name: docs_0.8.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/elasticsearch/initialization/snapshot_source.md b/docs/guides/elasticsearch/initialization/snapshot_source.md index add63ff3b..d028581c2 100644 --- a/docs/guides/elasticsearch/initialization/snapshot_source.md +++ b/docs/guides/elasticsearch/initialization/snapshot_source.md @@ -1,12 +1,12 @@ --- title: Initialize Elasticsearch from Snapshot menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: es-snapshot-source-initialization name: Using Snapshot parent: es-initialization-elasticsearch weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- @@ -33,7 +33,7 @@ NAME STATUS AGE demo Active 5s ``` -> Note: Yaml files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/cli/tree/master/docs/examples/elasticsearch) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: Yaml files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/cli/tree/master/docs/examples/elasticsearch) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). ## Prepare Snapshot @@ -92,7 +92,7 @@ instant-snapshot infant-elasticsearch Succeeded 51m Now, create the Elasticsearch object. ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/elasticsearch/initialization/recovered-es.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/elasticsearch/initialization/recovered-es.yaml elasticsearch.kubedb.com/recovered-es created ``` diff --git a/docs/guides/elasticsearch/kibana/_index.md b/docs/guides/elasticsearch/kibana/_index.md index 082ba2494..9b48f0bdf 100644 --- a/docs/guides/elasticsearch/kibana/_index.md +++ b/docs/guides/elasticsearch/kibana/_index.md @@ -1,10 +1,10 @@ --- title: Use Kibana with KubeDB Elasticsearch menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: es-kibana name: Kibana parent: es-elasticsearch-guides weight: 55 -menu_name: docs_0.8.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/elasticsearch/kibana/connect-kibana.md b/docs/guides/elasticsearch/kibana/connect-kibana.md index 1165f176b..e79f1a296 100644 --- a/docs/guides/elasticsearch/kibana/connect-kibana.md +++ b/docs/guides/elasticsearch/kibana/connect-kibana.md @@ -1,12 +1,12 @@ --- title: Using Kibana with KubeDB Elasticsearch menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: es-kibana-connect name: Use Kibana parent: es-kibana weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -36,7 +36,7 @@ NAME STATUS AGE demo Active 5s ``` -> Note: Yaml files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/cli/tree/master/docs/examples/elasticsearch) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: Yaml files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/cli/tree/master/docs/examples/elasticsearch) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). ## Overview @@ -257,7 +257,7 @@ metadata: Now, create Elasticsearch crd specifying `spec.databaseSecret` and `spec.configSource` field. ```console -$ kubectl apply -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/elasticsearch/kibana/es-kibana-demo.yaml +$ kubectl apply -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.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.9.0-beta.1/docs/examples/elasticsearch/kibana/kibana-deployment.yaml +$ kubectl apply -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/elasticsearch/kibana/kibana-deployment.yaml deployment.apps/kibana created ``` diff --git a/docs/guides/elasticsearch/monitoring/_index.md b/docs/guides/elasticsearch/monitoring/_index.md index 6cc7cf5fd..84149fef5 100755 --- a/docs/guides/elasticsearch/monitoring/_index.md +++ b/docs/guides/elasticsearch/monitoring/_index.md @@ -1,10 +1,10 @@ --- title: Elasticsearch Monitoring menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: es-monitoring-elasticsearch name: Monitoring parent: es-elasticsearch-guides weight: 45 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/elasticsearch/monitoring/using-builtin-prometheus.md b/docs/guides/elasticsearch/monitoring/using-builtin-prometheus.md index af40127c6..8c588a833 100644 --- a/docs/guides/elasticsearch/monitoring/using-builtin-prometheus.md +++ b/docs/guides/elasticsearch/monitoring/using-builtin-prometheus.md @@ -1,12 +1,12 @@ --- title: Monitor Elasticsearch using Builtin Prometheus Discovery menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: es-using-builtin-prometheus-monitoring name: Builtin Prometheus Discovery parent: es-monitoring-elasticsearch weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -32,7 +32,7 @@ NAME STATUS AGE demo Active 5s ``` -> Note: Yaml files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/cli/tree/master/docs/examples/elasticsearch) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: Yaml files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/cli/tree/master/docs/examples/elasticsearch) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). This tutorial assumes that you are familiar with Elasticsearch concept. @@ -66,7 +66,7 @@ Here, Run following command to create example above. ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/elasticsearch/monitoring/builtin-prom-es.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/elasticsearch/monitoring/builtin-prom-es.yaml elasticsearch.kubedb.com/builtin-prom-es created ``` @@ -178,7 +178,7 @@ data: Create above ConfigMap ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/monitoring/builtin-prometheus/demo-1.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/monitoring/builtin-prometheus/demo-1.yaml configmap/prometheus-server-conf created ``` @@ -225,7 +225,7 @@ spec: Run the following command to deploy prometheus-server ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/monitoring/builtin-prometheus/demo-2.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/monitoring/builtin-prometheus/demo-2.yaml clusterrole.rbac.authorization.k8s.io/prometheus-server created serviceaccount/prometheus-server created clusterrolebinding.rbac.authorization.k8s.io/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 399828afc..0f9f32ec4 100644 --- a/docs/guides/elasticsearch/monitoring/using-coreos-prometheus-operator.md +++ b/docs/guides/elasticsearch/monitoring/using-coreos-prometheus-operator.md @@ -1,12 +1,12 @@ --- title: Monitoring Elasticsearch using Coreos Prometheus Operator menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: es-using-coreos-prometheus-operator-monitoring name: Coreos Prometheus Operator parent: es-monitoring-elasticsearch weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -32,7 +32,7 @@ NAME STATUS AGE demo Active 5s ``` -> Note: Yaml files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/cli/tree/master/docs/examples/elasticsearch) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: Yaml files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/cli/tree/master/docs/examples/elasticsearch) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). This tutorial assumes that you are familiar with Elasticsearch concept. @@ -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.9.0-beta.1/docs/examples/monitoring/coreos-operator/demo-0.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/monitoring/coreos-operator/demo-0.yaml namespace/demo configured clusterrole.rbac.authorization.k8s.io/prometheus-operator created serviceaccount/prometheus-operator created @@ -72,7 +72,7 @@ servicemonitors.monitoring.coreos.com 2018-10-08T12:53:47Z 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.9.0-beta.1/docs/examples/monitoring/coreos-operator/demo-1.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/monitoring/coreos-operator/demo-1.yaml clusterrole.rbac.authorization.k8s.io/prometheus created serviceaccount/prometheus created clusterrolebinding.rbac.authorization.k8s.io/prometheus created @@ -155,7 +155,7 @@ Here, Now create this Elasticsearch object with monitoring spec ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/elasticsearch/monitoring/coreos-prom-es.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/elasticsearch/monitoring/coreos-prom-es.yaml elasticsearch.kubedb.com/coreos-prom-es created ``` diff --git a/docs/guides/elasticsearch/private-registry/_index.md b/docs/guides/elasticsearch/private-registry/_index.md index 68a189121..0cda64ac2 100755 --- a/docs/guides/elasticsearch/private-registry/_index.md +++ b/docs/guides/elasticsearch/private-registry/_index.md @@ -1,10 +1,10 @@ --- title: Run Elasticsearch from Private Registry menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: es-private-registry-elasticsearch name: Private Registry parent: es-elasticsearch-guides weight: 35 -menu_name: docs_0.8.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/elasticsearch/private-registry/using-private-registry.md b/docs/guides/elasticsearch/private-registry/using-private-registry.md index da5d1366e..1aa55c81e 100644 --- a/docs/guides/elasticsearch/private-registry/using-private-registry.md +++ b/docs/guides/elasticsearch/private-registry/using-private-registry.md @@ -1,12 +1,12 @@ --- title: Run Elasticsearch using Private Registry menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: es-using-private-registry-private-registry name: Quickstart parent: es-private-registry-elasticsearch weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -30,7 +30,7 @@ NAME STATUS AGE demo Active 5s ``` -> Note: Yaml files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/cli/tree/master/docs/examples/elasticsearch) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: Yaml files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/cli/tree/master/docs/examples/elasticsearch) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). ## Prepare Private Docker Registry @@ -48,7 +48,7 @@ For Elasticsearch, push the following images to your private registry. ```console $ export DOCKER_REGISTRY= -$ docker pull kubedb/operator:0.9.0-beta.1 ; docker tag kubedb/operator:0.9.0-beta.1 $DOCKER_REGISTRY/operator:0.9.0-beta.1 ; docker push $DOCKER_REGISTRY/operator:0.9.0-beta.1 +$ docker pull kubedb/operator:0.9.0-rc.0 ; docker tag kubedb/operator:0.9.0-rc.0 $DOCKER_REGISTRY/operator:0.9.0-rc.0 ; docker push $DOCKER_REGISTRY/operator:0.9.0-rc.0 $ docker pull kubedb/elasticsearch:6.3-v1 ; docker tag kubedb/elasticsearch:6.3-v1 $DOCKER_REGISTRY/elasticsearch:6.3-v1 ; docker push $DOCKER_REGISTRY/elasticsearch:6.3-v1 $ docker pull kubedb/elasticsearch-tools:6.3-v1 ; docker tag kubedb/elasticsearch-tools:6.3-v1 $DOCKER_REGISTRY/elasticsearch-tools:6.3-v1 ; docker push $DOCKER_REGISTRY/elasticsearch-tools:6.3-v1 $ docker pull kubedb/elasticsearch_exporter:1.0.2 ; docker tag kubedb/elasticsearch_exporter:1.0.2 $DOCKER_REGISTRY/elasticsearch_exporter:1.0.2 ; docker push $DOCKER_REGISTRY/elasticsearch_exporter:1.0.2 @@ -138,7 +138,7 @@ spec: Now run the command to deploy this Elasticsearch object: ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/elasticsearch/private-registry/private-registry.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/elasticsearch/private-registry/private-registry.yaml elasticsearch.kubedb.com/pvt-reg-elasticsearch created ``` diff --git a/docs/guides/elasticsearch/quickstart/_index.md b/docs/guides/elasticsearch/quickstart/_index.md index 1376ee5ef..31b851bd6 100755 --- a/docs/guides/elasticsearch/quickstart/_index.md +++ b/docs/guides/elasticsearch/quickstart/_index.md @@ -1,10 +1,10 @@ --- title: Elasticsearch Quickstart menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: es-quickstart-elasticsearch name: Quickstart parent: es-elasticsearch-guides weight: 15 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/elasticsearch/quickstart/quickstart.md b/docs/guides/elasticsearch/quickstart/quickstart.md index f7f119305..6fbf1aed0 100644 --- a/docs/guides/elasticsearch/quickstart/quickstart.md +++ b/docs/guides/elasticsearch/quickstart/quickstart.md @@ -1,12 +1,12 @@ --- title: Elasticsearch Quickstart menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: es-quickstart-quickstart name: Overview parent: es-quickstart-elasticsearch weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -36,7 +36,7 @@ NAME STATUS AGE demo Active 5s ``` -> Note: Yaml files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/cli/tree/master/docs/examples/elasticsearch) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: Yaml files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/cli/tree/master/docs/examples/elasticsearch) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). >We have designed this tutorial to demonstrate a production setup of KubeDB managed Elasticsearch. If you just want to try out KubeDB, you can bypass some of the safety features following the tips [here](/docs/guides/elasticsearch/quickstart/quickstart.md#tips-for-testing). @@ -76,7 +76,7 @@ NAME VERSION DB_IMAGE DEPRECATED AGE Notice the `DEPRECATED` column. Here, `true` means that this ElasticsearchVersion is deprecated for current KubeDB version. KubeDB will not work for deprecated ElasticsearchVersion. -In this tutorial, we will use `6.3-v1` ElasticsearchVersion crd to create Elasticsearch database. To know more about what is `ElasticsearchVersion` crd and why there is `6.3` and `6.3-v1` variation, please visit [here](/docs/concepts/catalog/elasticsearch.md). You can also see supported ElasticsearchVersion in KubeDB 0.9.0-beta.0 from [here](/docs/guides/elasticsearch/README.md#supported-elasticsearchversion-crd). +In this tutorial, we will use `6.3-v1` ElasticsearchVersion crd to create Elasticsearch database. To know more about what is `ElasticsearchVersion` crd and why there is `6.3` and `6.3-v1` variation, please visit [here](/docs/concepts/catalog/elasticsearch.md). You can also see supported ElasticsearchVersion in KubeDB 0.9.0-rc.0 from [here](/docs/guides/elasticsearch/README.md#supported-elasticsearchversion-crd). ## Create an Elasticsearch database @@ -115,7 +115,7 @@ Here, Let's create Elasticsearch crd that is shown above with following command ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/elasticsearch/quickstart/quick-elasticsearch.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/elasticsearch/quickstart/quick-elasticsearch.yaml elasticsearch.kubedb.com/quick-elasticsearch created ``` @@ -526,7 +526,7 @@ In this tutorial, the DormantDatabase `quick-elasticsearch` can be resumed by cr The below command will resume the DormantDatabase `quick-elasticsearch` ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/elasticsearch/quickstart/quick-elasticsearch.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/elasticsearch/quickstart/quick-elasticsearch.yaml elasticsearch.kubedb.com/quick-elasticsearch created ``` diff --git a/docs/guides/elasticsearch/search-guard/_index.md b/docs/guides/elasticsearch/search-guard/_index.md index feaeab403..b2e7c87ee 100755 --- a/docs/guides/elasticsearch/search-guard/_index.md +++ b/docs/guides/elasticsearch/search-guard/_index.md @@ -1,10 +1,10 @@ --- title: Using Search Guard with Elasticsearch menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: es-search-guard-elasticsearch name: Search Guard parent: es-elasticsearch-guides weight: 50 -menu_name: docs_0.8.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/elasticsearch/search-guard/configuration.md b/docs/guides/elasticsearch/search-guard/configuration.md index f042cc2ea..e52d16d92 100644 --- a/docs/guides/elasticsearch/search-guard/configuration.md +++ b/docs/guides/elasticsearch/search-guard/configuration.md @@ -1,12 +1,12 @@ --- title: Search Guard Configuration menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: es-configuration-search-guard name: Configuration parent: es-search-guard-elasticsearch weight: 15 -menu_name: docs_0.8.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -51,7 +51,7 @@ mkdir -p /tmp/kubedb/sg cd /tmp/kubedb/sg ``` -> Note: Yaml files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/cli/tree/master/docs/examples/elasticsearch) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: Yaml files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/cli/tree/master/docs/examples/elasticsearch) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). ## Create Configuration @@ -99,7 +99,7 @@ searchguard: ``` ```console -$ wget https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/elasticsearch/search-guard/sg-config/sg_config.yml +$ wget https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/elasticsearch/search-guard/sg-config/sg_config.yml ``` ### sg_internal_users.yml @@ -148,7 +148,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.9.0-beta.1/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-rc.0/docs/examples/elasticsearch/search-guard/sg-config/sg_internal_users.yml | envsubst > sg_internal_users.yml ``` > Note: If user does not provide `spec.databaseSecret`, KubeDB will generate random password for both admin and readall user. @@ -172,7 +172,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.9.0-beta.1/docs/examples/elasticsearch/search-guard/sg-config/sg_action_groups.yml +$ wget https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/elasticsearch/search-guard/sg-config/sg_action_groups.yml ``` ```yml @@ -254,7 +254,7 @@ sg_readall: ``` ```console -$ wget https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/elasticsearch/search-guard/sg-config/sg_roles.yml +$ wget https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/elasticsearch/search-guard/sg-config/sg_roles.yml ``` ### sg_roles_mapping.yml @@ -291,7 +291,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.9.0-beta.1/docs/examples/elasticsearch/search-guard/sg-config/sg_roles_mapping.yml +$ wget https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/elasticsearch/search-guard/sg-config/sg_roles_mapping.yml ``` ```yml @@ -380,7 +380,7 @@ Here, Create example above with following command ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/elasticsearch/search-guard/config-elasticsearch.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/elasticsearch/search-guard/config-elasticsearch.yaml elasticsearch.kubedb.com/config-elasticsearch created ``` diff --git a/docs/guides/elasticsearch/search-guard/disable-searchguard.md b/docs/guides/elasticsearch/search-guard/disable-searchguard.md index 3876eec90..17fd8d80e 100644 --- a/docs/guides/elasticsearch/search-guard/disable-searchguard.md +++ b/docs/guides/elasticsearch/search-guard/disable-searchguard.md @@ -1,12 +1,12 @@ --- title: Disable Search Guard menu: - docs_0.9.0-beta.1: + docs_0.9.0-rc.0: identifier: es-disable-search-guard name: Disable Search Guard parent: es-search-guard-elasticsearch weight: 30 -menu_name: docs_0.9.0-beta.1 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- @@ -35,7 +35,7 @@ NAME STATUS AGE demo Active 5s ``` -> Note: Yaml files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/cli/tree/master/docs/examples/elasticsearch) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: Yaml files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/cli/tree/master/docs/examples/elasticsearch) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). ## Create Elasticsearch @@ -62,7 +62,7 @@ spec: Let's create the Elasticsearch object we have shown above, ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/elasticsearch/search-guard/es-sg-disabled.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/elasticsearch/search-guard/es-sg-disabled.yaml elasticsearch.kubedb.com/es-sg-disabled created ``` diff --git a/docs/guides/elasticsearch/search-guard/issue-certificate.md b/docs/guides/elasticsearch/search-guard/issue-certificate.md index b51ee09bd..77ef588bc 100644 --- a/docs/guides/elasticsearch/search-guard/issue-certificate.md +++ b/docs/guides/elasticsearch/search-guard/issue-certificate.md @@ -1,12 +1,12 @@ --- title: Search Guard Certificate menu: - docs_0.8.0: + docs_0.9.0-rc.0: identifier: es-issue-certificate-search-guard name: Issue Certificate parent: es-search-guard-elasticsearch weight: 25 -menu_name: docs_0.8.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -70,7 +70,7 @@ mkdir -p /tmp/kubedb/certs cd /tmp/kubedb/certs ``` -> Note: Yaml files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/cli/tree/master/docs/examples/elasticsearch) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: Yaml files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/cli/tree/master/docs/examples/elasticsearch) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). ## Generate truststore @@ -81,7 +81,7 @@ You need to follow these steps 1. Get root certificate configuration file ```console - $ wget https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/elasticsearch/search-guard/openssl-config/openssl-ca.ini + $ wget https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/elasticsearch/search-guard/openssl-config/openssl-ca.ini ``` ```ini @@ -148,7 +148,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.9.0-beta.1/docs/examples/elasticsearch/search-guard/openssl-config/openssl-sign.ini +$ wget https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/elasticsearch/search-guard/openssl-config/openssl-sign.ini ``` ```ini @@ -230,7 +230,7 @@ Here, Now run following commands ```console -$ wget https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/elasticsearch/search-guard/openssl-config/openssl-node.ini +$ wget https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.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 @@ -271,7 +271,7 @@ Here, Now run following commands ```console -$ wget https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/elasticsearch/search-guard/openssl-config/openssl-client.ini +$ wget https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.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 @@ -311,7 +311,7 @@ Here, Now run following commands ```console -$ wget https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/elasticsearch/search-guard/openssl-config/openssl-sgadmin.ini +$ wget https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.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 @@ -372,7 +372,7 @@ Here, Create example above with following command ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/elasticsearch/search-guard/sg-elasticsearch.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/elasticsearch/search-guard/sg-elasticsearch.yaml elasticsearch.kubedb.com/sg-elasticsearch created ``` diff --git a/docs/guides/elasticsearch/search-guard/overview.md b/docs/guides/elasticsearch/search-guard/overview.md index 43c377c15..57f211daf 100644 --- a/docs/guides/elasticsearch/search-guard/overview.md +++ b/docs/guides/elasticsearch/search-guard/overview.md @@ -1,12 +1,12 @@ --- title: Search Guard menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: es-search-guard-search-guard name: Overview parent: es-search-guard-elasticsearch weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- diff --git a/docs/guides/elasticsearch/search-guard/use-tls.md b/docs/guides/elasticsearch/search-guard/use-tls.md index 7dec1cf10..c25b34bdf 100644 --- a/docs/guides/elasticsearch/search-guard/use-tls.md +++ b/docs/guides/elasticsearch/search-guard/use-tls.md @@ -1,12 +1,12 @@ --- title: Run TLS Secured Elasticsearch menu: - docs_0.8.0: + docs_0.9.0-rc.0: identifier: es-use-tls-search-guard name: Use TLS parent: es-search-guard-elasticsearch weight: 20 -menu_name: docs_0.8.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -34,7 +34,7 @@ NAME STATUS AGE demo Active 5s ``` -> Note: Yaml files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/cli/tree/master/docs/examples/elasticsearch) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: Yaml files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/cli/tree/master/docs/examples/elasticsearch) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). ## Create Elasticsearch @@ -63,7 +63,7 @@ spec: Let's create the Elasticsearch object we have shown above, ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/elasticsearch/search-guard/ssl-elasticsearch.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/elasticsearch/search-guard/ssl-elasticsearch.yaml elasticsearch.kubedb.com/ssl-elasticsearch created ``` diff --git a/docs/guides/elasticsearch/snapshot/_index.md b/docs/guides/elasticsearch/snapshot/_index.md index 284e1181f..042d5a494 100755 --- a/docs/guides/elasticsearch/snapshot/_index.md +++ b/docs/guides/elasticsearch/snapshot/_index.md @@ -1,10 +1,10 @@ --- title: Elasticsearch Snapshotting menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: es-snapshot-elasticsearch name: Snapshotting parent: es-elasticsearch-guides weight: 25 -menu_name: docs_0.8.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/elasticsearch/snapshot/instant_backup.md b/docs/guides/elasticsearch/snapshot/instant_backup.md index bd79b64a5..74fdb85de 100644 --- a/docs/guides/elasticsearch/snapshot/instant_backup.md +++ b/docs/guides/elasticsearch/snapshot/instant_backup.md @@ -1,12 +1,12 @@ --- title: Instant Backup of Elasticsearch menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: es-instant-backup-snapshot name: Instant Backup parent: es-snapshot-elasticsearch weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -32,14 +32,14 @@ NAME STATUS AGE demo Active 5s ``` -> Note: Yaml files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/cli/tree/master/docs/examples/elasticsearch) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: Yaml files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/cli/tree/master/docs/examples/elasticsearch) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). ## Prepare Database We need an Elasticsearch object in `Running` phase to perform backup operation. If you do not already have an Elasticsearch instance running, create one first. ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/elasticsearch/quickstart/infant-elasticsearch.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/elasticsearch/quickstart/infant-elasticsearch.yaml elasticsearch "infant-elasticsearch" created ``` @@ -189,7 +189,7 @@ To learn how to configure other storage destinations for snapshot data, please v Now, create the Snapshot object. ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/elasticsearch/snapshot/instant-snapshot.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/elasticsearch/snapshot/instant-snapshot.yaml snapshot.kubedb.com/instant-snapshot created ``` diff --git a/docs/guides/elasticsearch/snapshot/scheduled_backup.md b/docs/guides/elasticsearch/snapshot/scheduled_backup.md index 34ed9c9f5..315dc58b3 100644 --- a/docs/guides/elasticsearch/snapshot/scheduled_backup.md +++ b/docs/guides/elasticsearch/snapshot/scheduled_backup.md @@ -1,12 +1,12 @@ --- title: Scheduled Backup of Elasticsearch menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: es-scheduled-backup-snapshot name: Scheduled Backup parent: es-snapshot-elasticsearch weight: 15 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- > Don't know how backup works? Check [tutorial](/docs/guides/elasticsearch/snapshot/instant_backup.md) on Instant Backup. @@ -32,7 +32,7 @@ NAME STATUS AGE demo Active 5s ``` -> Note: Yaml files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/cli/tree/master/docs/examples/elasticsearch) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: Yaml files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/cli/tree/master/docs/examples/elasticsearch) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). ## Create Elasticsearch with BackupSchedule @@ -90,7 +90,7 @@ Here, > Note: Secret object must be in the same namespace as Elasticsearch, `scheduled-es`, in this case. ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/elasticsearch/snapshot/scheduled-es.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/elasticsearch/snapshot/scheduled-es.yaml elasticsearch.kubedb.com/scheduled-es created ``` diff --git a/docs/guides/elasticsearch/x-pack/_index.md b/docs/guides/elasticsearch/x-pack/_index.md index 62524fd65..82538ac46 100644 --- a/docs/guides/elasticsearch/x-pack/_index.md +++ b/docs/guides/elasticsearch/x-pack/_index.md @@ -1,10 +1,10 @@ --- title: Use X-Pack with KubeDB Elasticsearch menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: es-x-pack name: X-Pack parent: es-elasticsearch-guides weight: 60 -menu_name: docs_0.8.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/elasticsearch/x-pack/x-pack-monitoring.md b/docs/guides/elasticsearch/x-pack/x-pack-monitoring.md index 31d9ea0db..f5a46aad1 100644 --- a/docs/guides/elasticsearch/x-pack/x-pack-monitoring.md +++ b/docs/guides/elasticsearch/x-pack/x-pack-monitoring.md @@ -1,12 +1,12 @@ --- title: X-Pack Monitoring of Elasticsearch Cluster in KubeDB menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: es-x-pack-monitoring name: Monitoring parent: es-x-pack weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -34,7 +34,7 @@ NAME STATUS AGE demo Active 5s ``` -> Note: Yaml files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/cli/tree/master/docs/examples/elasticsearch) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: Yaml files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/cli/tree/master/docs/examples/elasticsearch) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). ## Overview @@ -286,7 +286,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.9.0-beta.1/docs/examples/elasticsearch/x-pack/es-mon-demo.yaml +$ kubectl apply -f kubectl apply -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.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.9.0-beta.1/docs/examples/elasticsearch/kibana/kibana-deployment.yaml +$ kubectl apply -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.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 e1cde85c4..16ef5d333 100644 --- a/docs/guides/memcached/README.md +++ b/docs/guides/memcached/README.md @@ -1,16 +1,16 @@ --- title: Memcached menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: mc-readme-memcached name: Memcached parent: mc-memcached-guides weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides -url: /docs/0.8.0/guides/memcached/ +url: /docs/0.9.0-rc.0/guides/memcached/ aliases: - - /docs/0.8.0/guides/memcached/README/ + - /docs/0.9.0-rc.0/guides/memcached/README/ --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -42,13 +42,22 @@ aliases: ## Supported Memcached Versions -| KubeDB Version | Memcached:1.5.4, 1.4 | 1.5.4-v1, 1.5-v1 | -| :------------: | :------------------: | :--------------: | -| 0.1.0 - 0.7.0 | ✗ | ✓ | -| 0.8.0 | ✓ | ✓ | -| 0.9.0-beta.1 | ✗ | ✗ | +| KubeDB Version | Memcached:1.5.4 | +|:--------------:|:---------------:| +| 0.1.0 - 0.7.0 | ✗ | +| 0.8.0 | ✓ | +| 0.9.0-rc.0 | ✓ | -
+## Supported MemcachedVersion CRD + +Here, ✓ means supported and ✗ means deprecated. + +| NAME | VERSION | KubeDB: 0.9.0-rc.0 | +|----------|---------|--------------------| +| 1.5 | 1.5 | ✗ | +| 1.5-v1 | 1.5 | ✓ | +| 1.5.4 | 1.5.4 | ✗ | +| 1.5.4-v1 | 1.5.4 | ✓ | ## User Guide diff --git a/docs/guides/memcached/_index.md b/docs/guides/memcached/_index.md index d1d9a44f3..95c4a005c 100644 --- a/docs/guides/memcached/_index.md +++ b/docs/guides/memcached/_index.md @@ -1,10 +1,10 @@ --- title: Memcached menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: mc-memcached-guides name: Memcached parent: guides weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/memcached/cli/_index.md b/docs/guides/memcached/cli/_index.md index 2befd3ef2..1b3e70f0d 100755 --- a/docs/guides/memcached/cli/_index.md +++ b/docs/guides/memcached/cli/_index.md @@ -1,10 +1,10 @@ --- title: CLI | KubeDB menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: mc-cli-memcached name: Cli parent: mc-memcached-guides weight: 45 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/memcached/cli/cli.md b/docs/guides/memcached/cli/cli.md index c9d367fc6..d2b531e28 100644 --- a/docs/guides/memcached/cli/cli.md +++ b/docs/guides/memcached/cli/cli.md @@ -1,12 +1,12 @@ --- title: CLI | KubeDB menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: mc-cli-cli name: Quickstart parent: mc-cli-memcached weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- diff --git a/docs/guides/memcached/custom-config/_index.md b/docs/guides/memcached/custom-config/_index.md index 6648d1b85..e78d67619 100755 --- a/docs/guides/memcached/custom-config/_index.md +++ b/docs/guides/memcached/custom-config/_index.md @@ -1,10 +1,10 @@ --- title: Run Memcached with Custom Configuration menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: mc-custom-config name: Custom Configuration parent: mc-memcached-guides weight: 50 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/memcached/custom-config/using-custom-config.md b/docs/guides/memcached/custom-config/using-custom-config.md index 638341b22..9005897a5 100644 --- a/docs/guides/memcached/custom-config/using-custom-config.md +++ b/docs/guides/memcached/custom-config/using-custom-config.md @@ -1,12 +1,12 @@ --- title: Run Memcached with Custom Configuration menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: mc-custom-config-quickstart name: Quickstart parent: mc-custom-config weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -32,7 +32,7 @@ KubeDB supports providing custom configuration for Memcached. This tutorial will demo Active 5s ``` -> Note: Yaml files used in this tutorial are stored in [docs/examples/memcached](https://github.com/kubedb/cli/tree/master/docs/examples/memcached) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: Yaml files used in this tutorial are stored in [docs/examples/memcached](https://github.com/kubedb/cli/tree/master/docs/examples/memcached) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). ## Overview @@ -119,7 +119,7 @@ metadata: Now, create Memcached crd specifying `spec.configSource` field. ```console -$ kubectl apply -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/memcached/custom-config/mc-custom.yaml +$ kubectl apply -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/memcached/custom-config/mc-custom.yaml memcached.kubedb.com/custom-memcached created ``` diff --git a/docs/guides/memcached/monitoring/_index.md b/docs/guides/memcached/monitoring/_index.md index 89aa2d479..1ae7030e4 100755 --- a/docs/guides/memcached/monitoring/_index.md +++ b/docs/guides/memcached/monitoring/_index.md @@ -1,10 +1,10 @@ --- title: Monitoring Memcached menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: mc-monitoring-memcached name: Monitoring parent: mc-memcached-guides weight: 25 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/memcached/monitoring/using-builtin-prometheus.md b/docs/guides/memcached/monitoring/using-builtin-prometheus.md index 1a9141409..705782ec5 100644 --- a/docs/guides/memcached/monitoring/using-builtin-prometheus.md +++ b/docs/guides/memcached/monitoring/using-builtin-prometheus.md @@ -1,12 +1,12 @@ --- title: Monitor Memcached using Builtin Prometheus Discovery menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: mc-using-builtin-prometheus-monitoring name: Builtin Prometheus Discovery parent: mc-monitoring-memcached weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- @@ -62,7 +62,7 @@ spec: ``` ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/memcached/monitoring/builtin-prometheus/demo-1.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/memcached/monitoring/builtin-prometheus/demo-1.yaml memcached.kubedb.com/memcd-mon-prometheus created ``` @@ -251,7 +251,7 @@ data: Create above ConfigMap ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/monitoring/builtin-prometheus/demo-1.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/monitoring/builtin-prometheus/demo-1.yaml configmap/prometheus-server-conf created ``` @@ -298,7 +298,7 @@ spec: Run the following command to deploy prometheus-server ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/monitoring/builtin-prometheus/demo-2.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/monitoring/builtin-prometheus/demo-2.yaml clusterrole.rbac.authorization.k8s.io/prometheus-server created serviceaccount/prometheus-server created clusterrolebinding.rbac.authorization.k8s.io/prometheus-server created @@ -356,7 +356,7 @@ kubectl delete -n demo mc/memcd-mon-prometheus kubectl patch -n demo drmn/memcd-mon-prometheus -p '{"spec":{"wipeOut":true}}' --type="merge" kubectl delete -n demo drmn/memcd-mon-prometheus -kubectl delete -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/monitoring/builtin-prometheus/demo-2.yaml +kubectl delete -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/monitoring/builtin-prometheus/demo-2.yaml kubectl delete ns demo ``` diff --git a/docs/guides/memcached/monitoring/using-coreos-prometheus-operator.md b/docs/guides/memcached/monitoring/using-coreos-prometheus-operator.md index 21661f74f..01b6e920d 100644 --- a/docs/guides/memcached/monitoring/using-coreos-prometheus-operator.md +++ b/docs/guides/memcached/monitoring/using-coreos-prometheus-operator.md @@ -1,12 +1,12 @@ --- title: Monitor Memcached using Coreos Prometheus Operator menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: mc-using-coreos-prometheus-operator-monitoring name: Coreos Prometheus Operator parent: mc-monitoring-memcached weight: 15 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -28,7 +28,7 @@ This tutorial will show you how to monitor KubeDB databases using Prometheus via Run the following command to deploy CoreOS-Prometheus operator. ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/monitoring/coreos-operator/demo-0.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/monitoring/coreos-operator/demo-0.yaml namespace/demo created clusterrole.rbac.authorization.k8s.io/prometheus-operator created serviceaccount/prometheus-operator created @@ -57,7 +57,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.9.0-beta.1/docs/examples/monitoring/coreos-operator/demo-1.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/monitoring/coreos-operator/demo-1.yaml clusterrole.rbac.authorization.k8s.io/prometheus created serviceaccount/prometheus created clusterrolebinding.rbac.authorization.k8s.io/prometheus created @@ -160,7 +160,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.9.0-beta.1/docs/examples/memcached/monitoring/coreos-operator/demo-1.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/memcached/monitoring/coreos-operator/demo-1.yaml memcached.kubedb.com/memcd-mon-coreos created ``` @@ -286,8 +286,8 @@ kubectl delete -n demo mc/memcd-mon-coreos kubectl patch -n demo drmn/memcd-mon-coreos -p '{"spec":{"wipeOut":true}}' --type="merge" kubectl delete -n demo drmn/memcd-mon-coreos -kubectl delete -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/monitoring/coreos-operator/demo-1.yaml -kubectl delete -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/monitoring/coreos-operator/demo-0.yaml +kubectl delete -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/monitoring/coreos-operator/demo-1.yaml +kubectl delete -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/monitoring/coreos-operator/demo-0.yaml kubectl delete ns demo ``` diff --git a/docs/guides/memcached/private-registry/_index.md b/docs/guides/memcached/private-registry/_index.md index 774d46d47..2fe1cee47 100755 --- a/docs/guides/memcached/private-registry/_index.md +++ b/docs/guides/memcached/private-registry/_index.md @@ -1,10 +1,10 @@ --- title: Run Memcached using Private Registry menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: mc-private-registry-memcached name: Private Registry parent: mc-memcached-guides weight: 20 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/memcached/private-registry/using-private-registry.md b/docs/guides/memcached/private-registry/using-private-registry.md index fc995f994..98629b168 100644 --- a/docs/guides/memcached/private-registry/using-private-registry.md +++ b/docs/guides/memcached/private-registry/using-private-registry.md @@ -1,12 +1,12 @@ --- title: Run Memcached using Private Registry menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: mc-using-private-registry-private-registry name: Quickstart parent: mc-private-registry-memcached weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- @@ -121,7 +121,7 @@ spec: Now run the command to deploy this `Memcached` object: ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/memcached/private-registry/demo-2.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/memcached/private-registry/demo-2.yaml memcached.kubedb.com/memcd-pvt-reg created ``` diff --git a/docs/guides/memcached/quickstart/_index.md b/docs/guides/memcached/quickstart/_index.md index 2d680c9ad..298313c17 100755 --- a/docs/guides/memcached/quickstart/_index.md +++ b/docs/guides/memcached/quickstart/_index.md @@ -1,10 +1,10 @@ --- title: Memcached Quickstart menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: mc-quickstart-memcached name: Quickstart parent: mc-memcached-guides weight: 15 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/memcached/quickstart/quickstart.md b/docs/guides/memcached/quickstart/quickstart.md index f4bd7f000..190b7b217 100644 --- a/docs/guides/memcached/quickstart/quickstart.md +++ b/docs/guides/memcached/quickstart/quickstart.md @@ -1,12 +1,12 @@ --- title: Memcached Quickstart menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: mc-quickstart-quickstart name: Overview parent: mc-quickstart-memcached weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -19,7 +19,7 @@ This tutorial will show you how to use KubeDB to run a Memcached database.   lifecycle

-> Note: The yaml files used in this tutorial are stored in [docs/examples/memcached](https://github.com/kubedb/cli/tree/master/docs/examples/memcached) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: The yaml files used in this tutorial are stored in [docs/examples/memcached](https://github.com/kubedb/cli/tree/master/docs/examples/memcached) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). ## Before You Begin @@ -77,7 +77,7 @@ spec: ``` ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/memcached/quickstart/demo-1.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/memcached/quickstart/demo-1.yaml memcached.kubedb.com/memcd-quickstart created ``` @@ -312,7 +312,7 @@ In this tutorial, the dormant database can be resumed by creating `Memcached` da The below command resumes the dormant database `memcd-quickstart`. ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/memcached/quickstart/demo-1.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/memcached/quickstart/demo-1.yaml memcached.kubedb.com/memcd-quickstart created ``` diff --git a/docs/guides/mongodb/README.md b/docs/guides/mongodb/README.md index c30c9471c..fd8efd549 100644 --- a/docs/guides/mongodb/README.md +++ b/docs/guides/mongodb/README.md @@ -1,16 +1,16 @@ --- title: MongoDB menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: mg-readme-mongodb name: MongoDB parent: mg-mongodb-guides weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides -url: /docs/0.8.0/guides/mongodb/ +url: /docs/0.9.0-rc.0/guides/mongodb/ aliases: - - /docs/0.8.0/guides/mongodb/README/ + - /docs/0.9.0-rc.0/guides/mongodb/README/ --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -43,13 +43,22 @@ aliases: ## Supported MongoDB Versions -| KubeDB Version | Mongo 3.4 | 3.6 | 3.4-v1 | 3.6-v1 | -| :------------: | :-------: | :------: | :------: | :------: | -| 0.1.0 - 0.7.0 | ✗ | ✗ | ✗ | ✗ | -| 0.8.0 | ✓ | ✓ | ✗ | ✗ | -| 0.9.0-beta.1 | ✗ | ✗ | ✓ | ✓ | +| KubeDB Version | Mongo:3.4 | Mongo:3.6 | +|:--------------:|:---------:|:---------:| +| 0.1.0 - 0.7.0 | ✗ | ✗ | +| 0.8.0 | ✓ | ✓ | +| 0.9.0-rc.0 | ✓ | ✓ | -
+## Supported MongoDBVersion CRD + +Here, ✓ means supported and ✗ means deprecated. + +| NAME | VERSION | KubeDB: 0.9.0-rc.0 | +|----------|---------|--------------------| +| 3.4 | 3.4 | ✗ | +| 3.4-v1 | 3.4 | ✓ | +| 3.6 | 3.6 | ✗ | +| 3.6-v1 | 3.6 | ✓ | ## External tools dependency diff --git a/docs/guides/mongodb/_index.md b/docs/guides/mongodb/_index.md index 86adebbd9..278917817 100644 --- a/docs/guides/mongodb/_index.md +++ b/docs/guides/mongodb/_index.md @@ -1,10 +1,10 @@ --- title: MongoDB menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: mg-mongodb-guides name: MongoDB parent: guides weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/mongodb/cli/_index.md b/docs/guides/mongodb/cli/_index.md index 58c339db6..a5141e25b 100755 --- a/docs/guides/mongodb/cli/_index.md +++ b/docs/guides/mongodb/cli/_index.md @@ -1,10 +1,10 @@ --- title: CLI | KubeDB menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: mg-cli-mongodb name: Cli parent: mg-mongodb-guides weight: 45 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/mongodb/cli/cli.md b/docs/guides/mongodb/cli/cli.md index e47b5a77c..e8c71677f 100644 --- a/docs/guides/mongodb/cli/cli.md +++ b/docs/guides/mongodb/cli/cli.md @@ -1,12 +1,12 @@ --- title: CLI | KubeDB menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: mg-cli-cli name: Quickstart parent: mg-cli-mongodb weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- diff --git a/docs/guides/mongodb/clustering/_index.md b/docs/guides/mongodb/clustering/_index.md index 9444ec5d2..c24100ce7 100755 --- a/docs/guides/mongodb/clustering/_index.md +++ b/docs/guides/mongodb/clustering/_index.md @@ -1,10 +1,10 @@ --- title: MongoDB Clustering menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: mg-clustering-mongodb name: Clustering parent: mg-mongodb-guides weight: 17 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/mongodb/clustering/replicaset.md b/docs/guides/mongodb/clustering/replicaset.md index 39cbcb4c5..bbabc5b9c 100644 --- a/docs/guides/mongodb/clustering/replicaset.md +++ b/docs/guides/mongodb/clustering/replicaset.md @@ -1,12 +1,12 @@ --- title: MongoDB ReplicaSet Guide menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: mg-clustering-replicaset name: ReplicaSet Guide parent: mg-clustering-mongodb weight: 15 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- @@ -37,7 +37,7 @@ Before proceeding: demo Active 10s ``` -> Note: The yaml files used in this tutorial are stored in [docs/examples/mongodb](https://github.com/kubedb/cli/tree/master/docs/examples/mongodb) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: The yaml files used in this tutorial are stored in [docs/examples/mongodb](https://github.com/kubedb/cli/tree/master/docs/examples/mongodb) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). ## Deploy MongoDB ReplicaSet @@ -66,7 +66,7 @@ spec: ``` ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/mongodb/clustering/demo-1.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/mongodb/clustering/demo-1.yaml mongodb.kubedb.com/mgo-replicaset created ``` @@ -76,7 +76,7 @@ Here, - `name` denotes the name of mongodb replicaset. - `KeyFileSecret` (optional) is a secret name that contains keyfile (a random string)against `key.txt` key. Each mongod instances in the replica set uses the contents of the keyfile as the shared password for authenticating other members in the deployment. Only mongod instances with the correct keyfile can join the replica set. _User can provide the `KeyFileSecret` by creating a secret with key `key.txt`. See [here](https://docs.mongodb.com/manual/tutorial/enforce-keyfile-access-control-in-existing-replica-set/#create-a-keyfile) to create the string for `KeyFileSecret`._ If `KeyFileSecret` is not given, KubeDB operator will generate a `KeyFileSecret` itself. - `spec.replicas` denotes the number of members in `rs0` mongodb replicaset. -- `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. Since release 0.8.0, a storage spec is required for MongoDB. +- `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. KubeDB operator watches for `MongoDB` objects using Kubernetes api. When a `MongoDB` object is created, KubeDB operator will create a new StatefulSet and a ClusterIP Service with the matching MongoDB object name. KubeDB operator will also create a governing service for StatefulSets with the name `-gvr`. No MongoDB specific RBAC permission is required in [RBAC enabled clusters](/docs/setup/install.md#using-yaml). @@ -451,7 +451,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.9.0-beta.1/docs/examples/mongodb/clustering/demo-1.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/mongodb/clustering/demo-1.yaml mongodb.kubedb.com/mgo-replicaset created ``` diff --git a/docs/guides/mongodb/clustering/replication_concept.md b/docs/guides/mongodb/clustering/replication_concept.md index 044f054d7..4445a8560 100644 --- a/docs/guides/mongodb/clustering/replication_concept.md +++ b/docs/guides/mongodb/clustering/replication_concept.md @@ -1,12 +1,12 @@ --- title: MongoDB ReplicaSet Concept menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: mg-clustering-replicaset-concept name: ReplicaSet Concept parent: mg-clustering-mongodb weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- diff --git a/docs/guides/mongodb/configuration/_index.md b/docs/guides/mongodb/configuration/_index.md index fdde590b2..3a0e18082 100755 --- a/docs/guides/mongodb/configuration/_index.md +++ b/docs/guides/mongodb/configuration/_index.md @@ -1,10 +1,10 @@ --- title: Run mongodb with Custom Configuration menu: - docs_0.8.0: + docs_0.9.0-rc.0: identifier: mg-configuration name: Custom Configuration parent: mg-mongodb-guides weight: 27 -menu_name: docs_0.8.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/mongodb/configuration/using-CRD-configuration.md b/docs/guides/mongodb/configuration/using-CRD-configuration.md index 1cd32e08d..fde8ed10c 100644 --- a/docs/guides/mongodb/configuration/using-CRD-configuration.md +++ b/docs/guides/mongodb/configuration/using-CRD-configuration.md @@ -1,20 +1,20 @@ --- title: Run MongoDB with Custom Configuration menu: - docs_0.8.0: + docs_0.9.0-rc.0: identifier: mg-crd-configuration name: Using CRD Config parent: mg-configuration weight: 15 -menu_name: docs_0.8.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- > New to KubeDB? Please start [here](/docs/concepts/README.md). -# Configuration Using CRD +# Run MongoDB with Custom Configuration -KubeDB supports providing variation configuration for MongoDB through [PodTemplate](/docs/concepts/databases/mongodb.md#specpodtemplate). This tutorial will show you how to use KubeDB to run a MongoDB database with custom configuration using PodTemplate. +KubeDB supports providing custom configuration for MongoDB via [PodTemplate](/docs/concepts/databases/mongodb.md#specpodtemplate). This tutorial will show you how to use KubeDB to run a MongoDB database with custom configuration using PodTemplate. ## Before You Begin @@ -29,7 +29,7 @@ KubeDB supports providing variation configuration for MongoDB through [PodTempla namespace/demo created ``` -> Note: Yaml files used in this tutorial are stored in [docs/examples/mongodb](https://github.com/kubedb/cli/tree/master/docs/examples/mongodb) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: Yaml files used in this tutorial are stored in [docs/examples/mongodb](https://github.com/kubedb/cli/tree/master/docs/examples/mongodb) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). ## Overview @@ -93,7 +93,7 @@ spec: ``` ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/mongodb/configuration/mgo-misc-config.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/mongodb/configuration/mgo-misc-config.yaml mongodb.kubedb.com/mgo-misc-config created ``` @@ -183,7 +183,7 @@ spec: ``` ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/mongodb/configuration/snapshot-misc-conf.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/mongodb/configuration/snapshot-misc-conf.yaml snapshot.kubedb.com/snap-mongodb-config created diff --git a/docs/guides/mongodb/configuration/using-custom-config.md b/docs/guides/mongodb/configuration/using-custom-config.md index e77202e2b..9f80e4c36 100644 --- a/docs/guides/mongodb/configuration/using-custom-config.md +++ b/docs/guides/mongodb/configuration/using-custom-config.md @@ -1,12 +1,12 @@ --- title: Run MongoDB with Custom Configuration menu: - docs_0.8.0: + docs_0.9.0-rc.0: identifier: mg-custom-config-quickstart name: Quickstart parent: mg-configuration weight: 10 -menu_name: docs_0.8.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- @@ -33,7 +33,7 @@ KubeDB supports providing custom configuration for MongoDB. This tutorial will s demo Active 10s ``` -> Note: The yaml files used in this tutorial are stored in [docs/examples/mongodb](https://github.com/kubedb/cli/tree/master/docs/examples/mongodb) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: The yaml files used in this tutorial are stored in [docs/examples/mongodb](https://github.com/kubedb/cli/tree/master/docs/examples/mongodb) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). ## Overview @@ -107,7 +107,7 @@ spec: ``` ```console -$ kubectl create-f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/mongodb/configuration/demo1.yaml +$ kubectl create-f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/mongodb/configuration/demo1.yaml mongodb.kubedb.com/mgo-custom-config created ``` diff --git a/docs/guides/mongodb/initialization/_index.md b/docs/guides/mongodb/initialization/_index.md index 9f302b441..2a78deb52 100755 --- a/docs/guides/mongodb/initialization/_index.md +++ b/docs/guides/mongodb/initialization/_index.md @@ -1,10 +1,10 @@ --- title: MongoDB Initialization menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: mg-initialization-mongodb name: Initialization parent: mg-mongodb-guides weight: 25 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/mongodb/initialization/using-script.md b/docs/guides/mongodb/initialization/using-script.md index 174925543..32c99aadc 100644 --- a/docs/guides/mongodb/initialization/using-script.md +++ b/docs/guides/mongodb/initialization/using-script.md @@ -1,12 +1,12 @@ --- title: Initialize MongoDB using Script menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: mg-using-script-initialization name: Using Script parent: mg-initialization-mongodb weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- @@ -35,7 +35,7 @@ This tutorial will show you how to use KubeDB to initialize a MongoDB database w In this tutorial we will use .js script stored in GitHub repository [kubedb/mongodb-init-scripts](https://github.com/kubedb/mongodb-init-scripts). -> Note: The yaml files used in this tutorial are stored in [docs/examples/mongodb](https://github.com/kubedb/cli/tree/master/docs/examples/mongodb) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: The yaml files used in this tutorial are stored in [docs/examples/mongodb](https://github.com/kubedb/cli/tree/master/docs/examples/mongodb) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). ## Prepare Initialization Scripts @@ -79,7 +79,7 @@ spec: ``` ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/mongodb/Initialization/demo-1.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/mongodb/Initialization/demo-1.yaml mongodb.kubedb.com/mgo-init-script created ``` diff --git a/docs/guides/mongodb/initialization/using-snapshot.md b/docs/guides/mongodb/initialization/using-snapshot.md index bfa7c5b1e..24f1486ee 100644 --- a/docs/guides/mongodb/initialization/using-snapshot.md +++ b/docs/guides/mongodb/initialization/using-snapshot.md @@ -1,12 +1,12 @@ --- title: Initialize MongoDB from Snapshot menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: mg-using-snapshot-initialization name: From Snapshot parent: mg-initialization-mongodb weight: 15 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -23,7 +23,7 @@ This tutorial will show you how to use KubeDB to initialize a MongoDB database w - This tutorial assumes that you have created a namespace `demo` and a snapshot `snapshot-infant`. Follow the steps [here](/docs/guides/mongodb/snapshot/backup-and-restore.md) to create a database and take [instant snapshot](/docs/guides/mongodb/snapshot/backup-and-restore.md#instant-backups), if you have not done so already. If you have changed the name of either namespace or snapshot object, please modify the YAMLs used in this tutorial accordingly. -> Note: The yaml files used in this tutorial are stored in [docs/examples/mongodb](https://github.com/kubedb/cli/tree/master/docs/examples/mongodb) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: The yaml files used in this tutorial are stored in [docs/examples/mongodb](https://github.com/kubedb/cli/tree/master/docs/examples/mongodb) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). ## Create MongoDB with Init-Snapshot @@ -51,7 +51,7 @@ spec: ``` ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/mongodb/Initialization/demo-2.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/mongodb/Initialization/demo-2.yaml mongodb.kubedb.com/mgo-init-snapshot created ``` diff --git a/docs/guides/mongodb/monitoring/_index.md b/docs/guides/mongodb/monitoring/_index.md index 2023ceda4..7b40198a6 100755 --- a/docs/guides/mongodb/monitoring/_index.md +++ b/docs/guides/mongodb/monitoring/_index.md @@ -1,10 +1,10 @@ --- title: Monitoring MongoDB menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: mg-monitoring-mongodb name: Monitoring parent: mg-mongodb-guides weight: 35 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/mongodb/monitoring/using-builtin-prometheus.md b/docs/guides/mongodb/monitoring/using-builtin-prometheus.md index 037ab4698..bbc80862f 100644 --- a/docs/guides/mongodb/monitoring/using-builtin-prometheus.md +++ b/docs/guides/mongodb/monitoring/using-builtin-prometheus.md @@ -1,12 +1,12 @@ --- title: Monitor MongoDB using Builtin Prometheus Discovery menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: mg-using-builtin-prometheus-monitoring name: Builtin Prometheus Discovery parent: mg-monitoring-mongodb weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- @@ -33,7 +33,7 @@ This tutorial will show you how to monitor MongoDB databases using [Prometheus]( demo Active 10s ``` -> Note: The yaml files used in this tutorial are stored in [docs/examples/mongodb](https://github.com/kubedb/cli/tree/master/docs/examples/mongodb) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: The yaml files used in this tutorial are stored in [docs/examples/mongodb](https://github.com/kubedb/cli/tree/master/docs/examples/mongodb) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). ## Monitor with builtin Prometheus @@ -59,7 +59,7 @@ spec: ``` ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/mongodb/monitoring/builtin-prometheus/demo-1.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/mongodb/monitoring/builtin-prometheus/demo-1.yaml mongodb.kubedb.com/mgo-mon-prometheus created ``` @@ -284,7 +284,7 @@ data: Create above ConfigMap ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/monitoring/builtin-prometheus/demo-1.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/monitoring/builtin-prometheus/demo-1.yaml configmap/prometheus-server-conf created ``` @@ -331,7 +331,7 @@ spec: Run the following command to deploy prometheus-server ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/monitoring/builtin-prometheus/demo-2.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/monitoring/builtin-prometheus/demo-2.yaml clusterrole.rbac.authorization.k8s.io/prometheus-server created serviceaccount/prometheus-server created clusterrolebinding.rbac.authorization.k8s.io/prometheus-server created @@ -391,7 +391,7 @@ kubectl delete -n demo mg/mgo-mon-prometheus kubectl patch -n demo drmn/mgo-mon-prometheus -p '{"spec":{"wipeOut":true}}' --type="merge" kubectl delete -n demo drmn/mgo-mon-prometheus -kubectl delete -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/monitoring/builtin-prometheus/demo-2.yaml +kubectl delete -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/monitoring/builtin-prometheus/demo-2.yaml kubectl delete ns demo ``` diff --git a/docs/guides/mongodb/monitoring/using-coreos-prometheus-operator.md b/docs/guides/mongodb/monitoring/using-coreos-prometheus-operator.md index 061ed3036..d924a7a05 100644 --- a/docs/guides/mongodb/monitoring/using-coreos-prometheus-operator.md +++ b/docs/guides/mongodb/monitoring/using-coreos-prometheus-operator.md @@ -1,12 +1,12 @@ --- title: Monitor MongoDB using Coreos Prometheus Operator menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: mg-using-coreos-prometheus-operator-monitoring name: Coreos Prometheus Operator parent: mg-monitoring-mongodb weight: 15 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- @@ -33,14 +33,14 @@ This tutorial will show you how to monitor KubeDB databases using Prometheus via demo Active 10s ``` -> Note: The yaml files used in this tutorial are stored in [docs/examples/mongodb](https://github.com/kubedb/cli/tree/master/docs/examples/mongodb) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: The yaml files used in this tutorial are stored in [docs/examples/mongodb](https://github.com/kubedb/cli/tree/master/docs/examples/mongodb) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). ## Deploy CoreOS-Prometheus Operator Run the following command to deploy CoreOS-Prometheus operator. ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/monitoring/coreos-operator/demo-0.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/monitoring/coreos-operator/demo-0.yaml namespace/demo created clusterrole.rbac.authorization.k8s.io/prometheus-operator created serviceaccount/prometheus-operator created @@ -71,7 +71,7 @@ servicemonitors.monitoring.coreos.com 2018-09-24T12:42:22Z 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.9.0-beta.1/docs/examples/monitoring/coreos-operator/demo-1.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/monitoring/coreos-operator/demo-1.yaml clusterrole.rbac.authorization.k8s.io/prometheus created serviceaccount/prometheus created clusterrolebinding.rbac.authorization.k8s.io/prometheus created @@ -171,7 +171,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.9.0-beta.1/docs/examples/mongodb/monitoring/coreos-operator/demo-1.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/mongodb/monitoring/coreos-operator/demo-1.yaml mongodb.kubedb.com/mgo-mon-coreos created ``` @@ -327,8 +327,8 @@ kubectl delete -n demo mg/mgo-mon-coreos kubectl patch -n demo drmn/mgo-mon-coreos -p '{"spec":{"wipeOut":true}}' --type="merge" kubectl delete -n demo drmn/mgo-mon-coreos -kubectl delete -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/monitoring/coreos-operator/demo-1.yaml -kubectl delete -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/monitoring/coreos-operator/demo-0.yaml +kubectl delete -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/monitoring/coreos-operator/demo-1.yaml +kubectl delete -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/monitoring/coreos-operator/demo-0.yaml kubectl delete ns demo ``` diff --git a/docs/guides/mongodb/private-registry/_index.md b/docs/guides/mongodb/private-registry/_index.md index 5b82fa07a..7d12bc644 100755 --- a/docs/guides/mongodb/private-registry/_index.md +++ b/docs/guides/mongodb/private-registry/_index.md @@ -1,10 +1,10 @@ --- title: Run MongoDB using Private Registry menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: mg-private-registry-mongodb name: Private Registry parent: mg-mongodb-guides weight: 30 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/mongodb/private-registry/using-private-registry.md b/docs/guides/mongodb/private-registry/using-private-registry.md index 91ab0fdfe..c3c83863c 100644 --- a/docs/guides/mongodb/private-registry/using-private-registry.md +++ b/docs/guides/mongodb/private-registry/using-private-registry.md @@ -1,12 +1,12 @@ --- title: Run MongoDB using Private Registry menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: mg-using-private-registry-private-registry name: Quickstart parent: mg-private-registry-mongodb weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- @@ -127,7 +127,7 @@ spec: Now run the command to deploy this `MongoDB` object: ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/mongodb/private-registry/demo-2.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/mongodb/private-registry/demo-2.yaml mongodb.kubedb.com/mgo-pvt-reg created ``` diff --git a/docs/guides/mongodb/quickstart/_index.md b/docs/guides/mongodb/quickstart/_index.md index 6589e1532..dbe3c4f01 100755 --- a/docs/guides/mongodb/quickstart/_index.md +++ b/docs/guides/mongodb/quickstart/_index.md @@ -1,10 +1,10 @@ --- title: MongoDB Quickstart menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: mg-quickstart-mongodb name: Quickstart parent: mg-mongodb-guides weight: 15 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/mongodb/quickstart/quickstart.md b/docs/guides/mongodb/quickstart/quickstart.md index 69df9b4a1..6cf2b7684 100644 --- a/docs/guides/mongodb/quickstart/quickstart.md +++ b/docs/guides/mongodb/quickstart/quickstart.md @@ -1,12 +1,12 @@ --- title: MongoDB Quickstart menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: mg-quickstart-quickstart name: Overview parent: mg-quickstart-mongodb weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -44,7 +44,7 @@ This tutorial will show you how to use KubeDB to run a MongoDB database. demo Active 10s ``` -> Note: The yaml files used in this tutorial are stored in [docs/examples/mongodb](https://github.com/kubedb/cli/tree/master/docs/examples/mongodb) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: The yaml files used in this tutorial are stored in [docs/examples/mongodb](https://github.com/kubedb/cli/tree/master/docs/examples/mongodb) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). ## Find Available MongoDBVersion @@ -83,7 +83,7 @@ spec: ``` ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/mongodb/quickstart/demo-1.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/mongodb/quickstart/demo-1.yaml mongodb.kubedb.com/mgo-quickstart created ``` @@ -91,7 +91,7 @@ Here, - `spec.version` is name of the MongoDBVersion crd where the docker images are specified. In this tutorial, a MongoDB 3.4-v1 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 purpose. -- `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. Since release 0.8.0, a storage spec is required for MongoDB. +- `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] > Note: spec.storage section is used to create PVC for database pod. It will create PVC with storage size specified instorage.resources.requests field. Don't specify limits here. PVC does not get resized automatically. @@ -374,7 +374,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.9.0-beta.1/docs/examples/mongodb/quickstart/demo-1.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/mongodb/quickstart/demo-1.yaml mongodb.kubedb.com/mgo-quickstart created ``` diff --git a/docs/guides/mongodb/snapshot/_index.md b/docs/guides/mongodb/snapshot/_index.md index 2ee8513ce..a4bcb34cb 100755 --- a/docs/guides/mongodb/snapshot/_index.md +++ b/docs/guides/mongodb/snapshot/_index.md @@ -1,10 +1,10 @@ --- title: MongoDB Snapshotting menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: mg-snapshot-mongodb name: Snapshotting parent: mg-mongodb-guides weight: 20 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/mongodb/snapshot/backup-and-restore.md b/docs/guides/mongodb/snapshot/backup-and-restore.md index f3a22d6ad..0569fe764 100644 --- a/docs/guides/mongodb/snapshot/backup-and-restore.md +++ b/docs/guides/mongodb/snapshot/backup-and-restore.md @@ -1,12 +1,12 @@ --- title: Instant Backup of MongoDB menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: mg-backup-and-restore-snapshot name: Instant Backup parent: mg-snapshot-mongodb weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- @@ -16,7 +16,7 @@ section_menu_id: guides This tutorial will show you how to take snapshots of a KubeDB managed MongoDB database. -> Note: The yaml files used in this tutorial are stored in [docs/examples/mongodb](https://github.com/kubedb/cli/tree/master/docs/examples/mongodb) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: The yaml files used in this tutorial are stored in [docs/examples/mongodb](https://github.com/kubedb/cli/tree/master/docs/examples/mongodb) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). ## Before You Begin @@ -42,7 +42,7 @@ This tutorial will show you how to take snapshots of a KubeDB managed MongoDB da NAME STATUS AGE demo Active 1m - $ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/mongodb/snapshot/demo-1.yaml + $ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/mongodb/snapshot/demo-1.yaml mongodb.kubedb.com/mgo-infant created ``` @@ -101,7 +101,7 @@ spec: ``` ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/mongodb/snapshot/demo-2.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/mongodb/snapshot/demo-2.yaml snapshot.kubedb.com/snapshot-infant created $ kubedb get snap -n demo @@ -256,7 +256,7 @@ spec: ``` ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/mongodb/snapshot/demo-3.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/mongodb/snapshot/demo-3.yaml mongodb.kubedb.com/mgo-recovered created ``` diff --git a/docs/guides/mongodb/snapshot/scheduled-backup.md b/docs/guides/mongodb/snapshot/scheduled-backup.md index 637a9bf60..fbb740c0b 100644 --- a/docs/guides/mongodb/snapshot/scheduled-backup.md +++ b/docs/guides/mongodb/snapshot/scheduled-backup.md @@ -1,12 +1,12 @@ --- title: Scheduled Backup of MongoDB menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: mg-scheduled-backup-snapshot name: Scheduled Backup parent: mg-snapshot-mongodb weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- @@ -35,7 +35,7 @@ This tutorial will show you how to use KubeDB to take scheduled snapshot of a Mo demo Active 1m ``` -> Note: The yaml files used in this tutorial are stored in [docs/examples/mongodb](https://github.com/kubedb/cli/tree/master/docs/examples/mongodb) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: The yaml files used in this tutorial are stored in [docs/examples/mongodb](https://github.com/kubedb/cli/tree/master/docs/examples/mongodb) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). ## Scheduled Backups @@ -99,7 +99,7 @@ spec: ``` ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/mongodb/snapshot/demo-4.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/mongodb/snapshot/demo-4.yaml mongodb.kubedb.com/mgo-scheduled created ``` diff --git a/docs/guides/mysql/README.md b/docs/guides/mysql/README.md index 288955d41..ab8eacc3e 100644 --- a/docs/guides/mysql/README.md +++ b/docs/guides/mysql/README.md @@ -1,16 +1,16 @@ --- title: MySQL menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: my-readme-mysql name: MySQL parent: my-mysql-guides weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides -url: /docs/0.8.0/guides/mysql/ +url: /docs/0.9.0-rc.0/guides/mysql/ aliases: - - /docs/0.8.0/guides/mysql/README/ + - /docs/0.9.0-rc.0/guides/mysql/README/ --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -42,13 +42,27 @@ aliases: ## Supported MySQL Versions -| KubeDB Version | MySQL 8.0, 8 | 5.7, 5 | 8.0-v1, 8-v1 | 5.7-v1, 5-v1 | -| :------------: | :----------: | :------: | :----------: | :----------: | -| 0.1.0 - 0.7.0 | ✗ | ✗ | ✗ | ✗ | -| 0.8.0 | ✓ | ✓ | ✗ | ✗ | -| 0.9.0-beta.1 | ✗ | ✗ | ✓ | ✓ | +| KubeDB Version | MySQL:8.0 | MySQL:5.7 | +|:--------------:|:---------:|:---------:| +| 0.1.0 - 0.7.0 | ✗ | ✗ | +| 0.8.0 | ✓ | ✓ | +| 0.9.0-rc.0 | ✓ | ✓ | + +## Supported MySQLVersion CRD + +Here, ✓ means supported and ✗ means deprecated. + +| NAME | VERSION | KubeDB: 0.9.0-rc.0 | +|----------|---------|--------------------| +| 5 | 5 | ✗ | +| 5-v1 | 5 | ✓ | +| 5.7 | 5.7 | ✗ | +| 5.7-v1 | 5.7 | ✓ | +| 8 | 8 | ✗ | +| 8-v1 | 8 | ✓ | +| 8.0 | 8.0 | ✗ | +| 8.0-v1 | 8.0 | ✓ | -
## External tools dependency diff --git a/docs/guides/mysql/_index.md b/docs/guides/mysql/_index.md index 7e03dd9a7..e3a0e1ed6 100644 --- a/docs/guides/mysql/_index.md +++ b/docs/guides/mysql/_index.md @@ -1,10 +1,10 @@ --- title: MySQL menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: my-mysql-guides name: MySQL parent: guides weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/mysql/cli/_index.md b/docs/guides/mysql/cli/_index.md index c8b398265..4ae2f6432 100755 --- a/docs/guides/mysql/cli/_index.md +++ b/docs/guides/mysql/cli/_index.md @@ -1,10 +1,10 @@ --- title: CLI | KubeDB menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: my-cli-mysql name: Cli parent: my-mysql-guides weight: 45 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/mysql/cli/cli.md b/docs/guides/mysql/cli/cli.md index 36406f694..65edc2d95 100644 --- a/docs/guides/mysql/cli/cli.md +++ b/docs/guides/mysql/cli/cli.md @@ -1,12 +1,12 @@ --- title: CLI | KubeDB menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: my-cli-cli name: Quickstart parent: my-cli-mysql weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- diff --git a/docs/guides/mysql/configuration/_index.md b/docs/guides/mysql/configuration/_index.md index 5c833288a..09ac27ac4 100755 --- a/docs/guides/mysql/configuration/_index.md +++ b/docs/guides/mysql/configuration/_index.md @@ -1,10 +1,10 @@ --- title: Run MySQL with Custom Configuration menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: my-custom-config name: Custom Configuration parent: my-mysql-guides weight: 50 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/mysql/configuration/using-CRD-configuration.md b/docs/guides/mysql/configuration/using-CRD-configuration.md index 10c16fc4c..abef325b8 100644 --- a/docs/guides/mysql/configuration/using-CRD-configuration.md +++ b/docs/guides/mysql/configuration/using-CRD-configuration.md @@ -1,12 +1,12 @@ --- title: Run MySQL with Custom Configuration menu: - docs_0.8.0: + docs_0.9.0-rc.0: identifier: my-crd-configuration name: Using CRD Config parent: my-configuration weight: 15 -menu_name: docs_0.8.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- @@ -14,7 +14,7 @@ section_menu_id: guides # Run MySQL with Custom Configuration -KubeDB supports providing custom configuration for MySQL through [PodTemplate](/docs/concepts/databases/mysql.md#specpodtemplate). This tutorial will show you how to use KubeDB to run a MySQL database with custom configuration using PodTemplate. +KubeDB supports providing custom configuration for MySQL via [PodTemplate](/docs/concepts/databases/mysql.md#specpodtemplate). This tutorial will show you how to use KubeDB to run a MySQL database with custom configuration using PodTemplate. ## Before You Begin @@ -29,7 +29,7 @@ KubeDB supports providing custom configuration for MySQL through [PodTemplate](/ namespace/demo created ``` -> Note: Yaml files used in this tutorial are stored in [docs/examples/mysql](https://github.com/kubedb/cli/tree/master/docs/examples/mysql) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: Yaml files used in this tutorial are stored in [docs/examples/mysql](https://github.com/kubedb/cli/tree/master/docs/examples/mysql) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). ## Overview @@ -95,7 +95,7 @@ spec: ``` ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/mysql/configuration/mysql-misc-config.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/mysql/configuration/mysql-misc-config.yaml mysql.kubedb.com/mysql-misc-config created ``` @@ -135,7 +135,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.9.0-beta.1/docs/examples/mysql/quickstart/demo-1.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/mysql/quickstart/demo-1.yaml deployment.extensions/myadmin created service/myadmin created ``` @@ -194,7 +194,7 @@ spec: ``` ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/mysql/configuration/snapshot-misc-conf.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/mysql/configuration/snapshot-misc-conf.yaml snapshot.kubedb.com/snap-mysql-config created diff --git a/docs/guides/mysql/configuration/using-custom-config.md b/docs/guides/mysql/configuration/using-custom-config.md index 05e6ff7f0..3a8bb3a77 100644 --- a/docs/guides/mysql/configuration/using-custom-config.md +++ b/docs/guides/mysql/configuration/using-custom-config.md @@ -1,12 +1,12 @@ --- title: Run MySQL with Custom Configuration menu: - docs_0.8.0: + docs_0.9.0-rc.0: identifier: my-custom-config-file name: Using Config File parent: my-configuration weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- @@ -33,7 +33,7 @@ KubeDB supports providing custom configuration for MySQL. This tutorial will sho demo Active 5s ``` -> Note: Yaml files used in this tutorial are stored in [docs/examples/mysql](https://github.com/kubedb/cli/tree/master/docs/examples/mysql) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: Yaml files used in this tutorial are stored in [docs/examples/mysql](https://github.com/kubedb/cli/tree/master/docs/examples/mysql) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). ## Overview @@ -89,7 +89,7 @@ metadata: Now, create MySQL crd specifying `spec.configSource` field. ```console -$ kubectl apply -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/mysql/configuration/mysql-custom.yaml +$ kubectl apply -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/mysql/configuration/mysql-custom.yaml mysql.kubedb.com/custom-mysql created ``` @@ -150,7 +150,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.9.0-beta.1/docs/examples/mysql/quickstart/demo-1.yaml + $ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/mysql/quickstart/demo-1.yaml deployment.extensions/myadmin created service/myadmin created ``` diff --git a/docs/guides/mysql/initialization/_index.md b/docs/guides/mysql/initialization/_index.md index 3f821e6e4..bd7321bc9 100755 --- a/docs/guides/mysql/initialization/_index.md +++ b/docs/guides/mysql/initialization/_index.md @@ -1,10 +1,10 @@ --- title: MySQL Initialization menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: my-initialization-mysql name: Initialization parent: my-mysql-guides weight: 25 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/mysql/initialization/using-script.md b/docs/guides/mysql/initialization/using-script.md index fa1456847..a2263e627 100644 --- a/docs/guides/mysql/initialization/using-script.md +++ b/docs/guides/mysql/initialization/using-script.md @@ -1,12 +1,12 @@ --- title: Initialize MySQL using Script menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: my-using-script-initialization name: Using Script parent: my-initialization-mysql weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- @@ -31,7 +31,7 @@ In this tutorial we will use .sql script stored in GitHub repository [kubedb/mys $ kubectl create ns demo namespace/demo created - $ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/mysql/quickstart/demo-1.yaml + $ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/mysql/quickstart/demo-1.yaml deployment.extensions/myadmin created service/myadmin created @@ -99,7 +99,7 @@ spec: ``` ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/mysql/Initialization/demo-1.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/mysql/Initialization/demo-1.yaml mysql.kubedb.com/mysql-init-script created ``` diff --git a/docs/guides/mysql/initialization/using-snapshot.md b/docs/guides/mysql/initialization/using-snapshot.md index 6dbbe91b1..26e9cac95 100644 --- a/docs/guides/mysql/initialization/using-snapshot.md +++ b/docs/guides/mysql/initialization/using-snapshot.md @@ -1,12 +1,12 @@ --- title: Initialize MySQL from Snapshot menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: my-using-snapshot-initialization name: From Snapshot parent: my-initialization-mysql weight: 15 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -53,7 +53,7 @@ spec: ``` ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/mysql/Initialization/demo-2.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/mysql/Initialization/demo-2.yaml mysql.kubedb.com/mysql-init-snapshot created ``` diff --git a/docs/guides/mysql/monitoring/_index.md b/docs/guides/mysql/monitoring/_index.md index 9eb414495..a54e3c605 100755 --- a/docs/guides/mysql/monitoring/_index.md +++ b/docs/guides/mysql/monitoring/_index.md @@ -1,10 +1,10 @@ --- title: Monitoring MySQL menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: my-monitoring-mysql name: Monitoring parent: my-mysql-guides weight: 35 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/mysql/monitoring/using-builtin-prometheus.md b/docs/guides/mysql/monitoring/using-builtin-prometheus.md index 1264a5646..91af78806 100644 --- a/docs/guides/mysql/monitoring/using-builtin-prometheus.md +++ b/docs/guides/mysql/monitoring/using-builtin-prometheus.md @@ -1,12 +1,12 @@ --- title: Monitor MySQL using Builtin Prometheus Discovery menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: my-using-builtin-prometheus-monitoring name: Builtin Prometheus Discovery parent: my-monitoring-mysql weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- @@ -59,7 +59,7 @@ spec: ``` ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/mysql/monitoring/builtin-prometheus/demo-1.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/mysql/monitoring/builtin-prometheus/demo-1.yaml mysql.kubedb.com/mysql-mon-prometheus created ``` @@ -269,7 +269,7 @@ data: Create above ConfigMap ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/monitoring/builtin-prometheus/demo-1.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/monitoring/builtin-prometheus/demo-1.yaml configmap/prometheus-server-conf created ``` @@ -316,7 +316,7 @@ spec: Run the following command to deploy prometheus-server ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/monitoring/builtin-prometheus/demo-2.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/monitoring/builtin-prometheus/demo-2.yaml clusterrole.rbac.authorization.k8s.io/prometheus-server created serviceaccount/prometheus-server created clusterrolebinding.rbac.authorization.k8s.io/prometheus-server created @@ -375,7 +375,7 @@ kubectl delete -n demo mysql/mysql-mon-prometheus kubectl patch -n demo drmn/mysql-mon-prometheus -p '{"spec":{"wipeOut":true}}' --type="merge" kubectl delete -n demo drmn/mysql-mon-prometheus -kubectl delete -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/monitoring/builtin-prometheus/demo-2.yaml +kubectl delete -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/monitoring/builtin-prometheus/demo-2.yaml kubectl delete ns demo ``` diff --git a/docs/guides/mysql/monitoring/using-coreos-prometheus-operator.md b/docs/guides/mysql/monitoring/using-coreos-prometheus-operator.md index 4488c42a1..74918fd29 100644 --- a/docs/guides/mysql/monitoring/using-coreos-prometheus-operator.md +++ b/docs/guides/mysql/monitoring/using-coreos-prometheus-operator.md @@ -1,12 +1,12 @@ --- title: Monitor MySQL using Coreos Prometheus Operator menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: my-using-coreos-prometheus-operator-monitoring name: Coreos Prometheus Operator parent: my-monitoring-mysql weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- @@ -40,7 +40,7 @@ This tutorial will show you how to monitor KubeDB databases using Prometheus via Run the following command to deploy CoreOS-Prometheus operator. ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/monitoring/coreos-operator/demo-0.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/monitoring/coreos-operator/demo-0.yaml namespace/demo created clusterrole.rbac.authorization.k8s.io/prometheus-operator created serviceaccount/prometheus-operator created @@ -72,7 +72,7 @@ servicemonitors.monitoring.coreos.com 2018-09-24T12:42:22Z 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.9.0-beta.1/docs/examples/monitoring/coreos-operator/demo-1.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/monitoring/coreos-operator/demo-1.yaml clusterrole.rbac.authorization.k8s.io/prometheus created serviceaccount/prometheus created clusterrolebinding.rbac.authorization.k8s.io/prometheus created @@ -172,7 +172,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.9.0-beta.1/docs/examples/mysql/monitoring/coreos-operator/demo-1.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/mysql/monitoring/coreos-operator/demo-1.yaml mysql.kubedb.com/mysql-mon-coreos created ``` @@ -318,8 +318,8 @@ kubectl delete -n demo mysql/mysql-mon-coreos kubectl patch -n demo drmn/mysql-mon-coreos -p '{"spec":{"wipeOut":true}}' --type="merge" kubectl delete -n demo drmn/mysql-mon-coreos -kubectl delete -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/monitoring/coreos-operator/demo-1.yaml -kubectl delete -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/monitoring/coreos-operator/demo-0.yaml +kubectl delete -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/monitoring/coreos-operator/demo-1.yaml +kubectl delete -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/monitoring/coreos-operator/demo-0.yaml kubectl delete ns demo ``` diff --git a/docs/guides/mysql/private-registry/_index.md b/docs/guides/mysql/private-registry/_index.md index 7c44510fb..8cb802471 100755 --- a/docs/guides/mysql/private-registry/_index.md +++ b/docs/guides/mysql/private-registry/_index.md @@ -1,10 +1,10 @@ --- title: Run MySQL using Private Registry menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: my-private-registry-mysql name: Private Registry parent: my-mysql-guides weight: 30 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/mysql/private-registry/using-private-registry.md b/docs/guides/mysql/private-registry/using-private-registry.md index 73e485c37..ee69f157f 100644 --- a/docs/guides/mysql/private-registry/using-private-registry.md +++ b/docs/guides/mysql/private-registry/using-private-registry.md @@ -1,12 +1,12 @@ --- title: Run MySQL using Private Registry menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: my-using-private-registry-private-registry name: Quickstart parent: my-private-registry-mysql weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- @@ -125,7 +125,7 @@ spec: Now run the command to deploy this `MySQL` object: ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/mysql/private-registry/demo-2.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/mysql/private-registry/demo-2.yaml mysql.kubedb.com/mysql-pvt-reg created ``` diff --git a/docs/guides/mysql/quickstart/_index.md b/docs/guides/mysql/quickstart/_index.md index 6cbaf7859..d43a533ee 100755 --- a/docs/guides/mysql/quickstart/_index.md +++ b/docs/guides/mysql/quickstart/_index.md @@ -1,10 +1,10 @@ --- title: MySQL Quickstart menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: my-quickstart-mysql name: Quickstart parent: my-mysql-guides weight: 15 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/mysql/quickstart/quickstart.md b/docs/guides/mysql/quickstart/quickstart.md index 27a44e49b..3c82bed6c 100644 --- a/docs/guides/mysql/quickstart/quickstart.md +++ b/docs/guides/mysql/quickstart/quickstart.md @@ -1,12 +1,12 @@ --- title: MySQL Quickstart menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: my-quickstart-quickstart name: Overview parent: my-quickstart-mysql weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -19,7 +19,7 @@ This tutorial will show you how to use KubeDB to run a MySQL database.   lifecycle

-> Note: The yaml files used in this tutorial are stored in [docs/examples/mysql](https://github.com/kubedb/cli/tree/master/docs/examples/mysql) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: The yaml files used in this tutorial are stored in [docs/examples/mysql](https://github.com/kubedb/cli/tree/master/docs/examples/mysql) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). ## Before You Begin @@ -41,7 +41,7 @@ This tutorial will show you how to use KubeDB to run a MySQL database. $ kubectl create ns demo namespace "demo" created - $ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/mysql/quickstart/demo-1.yaml + $ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/mysql/quickstart/demo-1.yaml deployment.extensions/myadmin created service/myadmin created @@ -109,7 +109,7 @@ spec: ``` ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/mysql/quickstart/demo-2.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/mysql/quickstart/demo-2.yaml mysql.kubedb.com/mysql-quickstart created ``` @@ -117,7 +117,7 @@ Here, - `spec.version` is the name of the MySQLVersion CRD where the docker images are specified. In this tutorial, a MySQL 8.0-v1 database is going to be created. - `spec.storageType` specifies the type of storage that will be used for MySQL database. It can be `Durable` or `Ephemeral`. Default value of this field is `Durable`. If `Ephemeral` is used then KubeDB will create MySQL database using `EmptyDir` volume. In this case, you don't have to specify `spec.storage` field. This is useful for testing purpose. -- `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. +- `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. - `spec.terminationPolicy` gives flexibility whether to `nullify`(reject) the delete operation of `MySQL` crd or which resources KubeDB should keep or delete when you delete `MySQL` 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/concepts/databases/mysql.md#specterminationpolicy) > Note: spec.storage section is used to create PVC for database pod. It will create PVC with storage size specified instorage.resources.requests field. Don't specify limits here. PVC does not get resized automatically. @@ -366,7 +366,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.9.0-beta.1/docs/examples/mysql/quickstart/demo-2.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/mysql/quickstart/demo-2.yaml mysql "mysql-quickstart" created ``` diff --git a/docs/guides/mysql/snapshot/_index.md b/docs/guides/mysql/snapshot/_index.md index 40dd70fbe..effabd127 100755 --- a/docs/guides/mysql/snapshot/_index.md +++ b/docs/guides/mysql/snapshot/_index.md @@ -1,10 +1,10 @@ --- title: MySQL Snapshotting menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: my-snapshot-mysql name: Snapshotting parent: my-mysql-guides weight: 20 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/mysql/snapshot/backup-and-restore.md b/docs/guides/mysql/snapshot/backup-and-restore.md index 1af6686dc..d407d46c5 100644 --- a/docs/guides/mysql/snapshot/backup-and-restore.md +++ b/docs/guides/mysql/snapshot/backup-and-restore.md @@ -1,12 +1,12 @@ --- title: Instant Backup of MySQL menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: my-backup-and-restore-snapshot name: Instant Backup parent: my-snapshot-mysql weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -15,7 +15,7 @@ section_menu_id: guides This tutorial will show you how to take snapshots of a KubeDB managed MySQL database. -> Note: The yaml files used in this tutorial are stored in [docs/examples/mysql](https://github.com/kubedb/cli/tree/master/docs/examples/mysql) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: The yaml files used in this tutorial are stored in [docs/examples/mysql](https://github.com/kubedb/cli/tree/master/docs/examples/mysql) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). ## Before You Begin @@ -41,7 +41,7 @@ This tutorial will show you how to take snapshots of a KubeDB managed MySQL data NAME STATUS AGE demo Active 1m - $ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/mysql/snapshot/demo-1.yaml + $ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/mysql/snapshot/demo-1.yaml mysql.kubedb.com/mysql-infant created ``` @@ -100,7 +100,7 @@ spec: ``` ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/mysql/snapshot/demo-2.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/mysql/snapshot/demo-2.yaml snapshot.kubedb.com/snap-mysql-infant created $ kubedb get snap -n demo @@ -248,7 +248,7 @@ spec: ``` ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/mysql/snapshot/demo-3.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/mysql/snapshot/demo-3.yaml mysql.kubedb.com/mysql-recovered created ``` diff --git a/docs/guides/mysql/snapshot/scheduled-backup.md b/docs/guides/mysql/snapshot/scheduled-backup.md index 7448a2209..d2d6c1c08 100644 --- a/docs/guides/mysql/snapshot/scheduled-backup.md +++ b/docs/guides/mysql/snapshot/scheduled-backup.md @@ -1,12 +1,12 @@ --- title: Scheduled Backup of MySQL menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: my-scheduled-backup-snapshot name: Scheduled Backup parent: my-snapshot-mysql weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- @@ -33,7 +33,7 @@ This tutorial will show you how to use KubeDB to take scheduled snapshot of a My demo Active 1m ``` -> Note: The yaml files that are used in this tutorial are stored in [docs/examples](https://github.com/kubedb/cli/tree/master/docs/examples) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: The yaml files that are used in this tutorial are stored in [docs/examples](https://github.com/kubedb/cli/tree/master/docs/examples) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). ## Scheduled Backups @@ -94,7 +94,7 @@ spec: ``` ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/mysql/snapshot/demo-4.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/mysql/snapshot/demo-4.yaml mysql.kubedb.com/mysql-scheduled created ``` diff --git a/docs/guides/postgres/README.md b/docs/guides/postgres/README.md index f8afbfb4f..98e2eea04 100644 --- a/docs/guides/postgres/README.md +++ b/docs/guides/postgres/README.md @@ -1,16 +1,16 @@ --- title: Postgres menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: pg-readme-postgres name: Postgres parent: pg-postgres-guides weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides -url: /docs/0.8.0/guides/postgres/ +url: /docs/0.9.0-rc.0/guides/postgres/ aliases: - - /docs/0.8.0/guides/postgres/README/ + - /docs/0.9.0-rc.0/guides/postgres/README/ --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -53,19 +53,20 @@ aliases: | -------------- | :----------: | :----------: | :-----------: | | 0.1.0 - 0.7.0 | ✓ | ✗ | ✗ | | 0.8.0 | ✗ | ✓ | ✓ | -| 0.9.0-beta.1 | ✗ | ✓ | ✓ | - -
+| 0.9.0-rc.0 | ✗ | ✓ | ✓ | ## Supported PostgresVersion CRD Here, ✓ means supported and ✗ means deprecated. -| KubeDB Version | 9.6 | 9.6-v1 | 9.6.7 | 9.6.7-v1 | 10.2 | 10.2-v1 | -| -------------- | :------: | :------: | :------: | :------: | :------: | :------: | -| 0.9.0-beta.1 | ✗ | ✓ | ✗ | ✓ | ✗ | ✓ | - -
+| NAME | VERSION | KubeDB: 0.9.0-rc.0 | +|----------|---------|--------------------| +| 10.2 | 10.2 | ✗ | +| 10.2-v1 | 10.2 | ✓ | +| 9.6 | 9.6 | ✗ | +| 9.6-v1 | 9.6 | ✓ | +| 9.6.7 | 9.6.7 | ✗ | +| 9.6.7-v1 | 9.6.7 | ✓ | ## External tools dependency diff --git a/docs/guides/postgres/_index.md b/docs/guides/postgres/_index.md index 7081e0037..369f4cdf7 100644 --- a/docs/guides/postgres/_index.md +++ b/docs/guides/postgres/_index.md @@ -1,10 +1,10 @@ --- title: PostgreSQL menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: pg-postgres-guides name: PostgreSQL parent: guides weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/postgres/cli/_index.md b/docs/guides/postgres/cli/_index.md index 80c4d3e18..4d2674472 100755 --- a/docs/guides/postgres/cli/_index.md +++ b/docs/guides/postgres/cli/_index.md @@ -1,10 +1,10 @@ --- title: CLI | KubeDB menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: pg-cli-postgres name: CLI parent: pg-postgres-guides weight: 55 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/postgres/cli/cli.md b/docs/guides/postgres/cli/cli.md index a9c0f9345..cdadd8c32 100644 --- a/docs/guides/postgres/cli/cli.md +++ b/docs/guides/postgres/cli/cli.md @@ -1,12 +1,12 @@ --- title: CLI | KubeDB menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: pg-cli-cli name: Quickstart parent: pg-cli-postgres weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- diff --git a/docs/guides/postgres/clustering/_index.md b/docs/guides/postgres/clustering/_index.md index 9df34ff3e..c80261d11 100755 --- a/docs/guides/postgres/clustering/_index.md +++ b/docs/guides/postgres/clustering/_index.md @@ -1,10 +1,10 @@ --- title: PostgreSQL Clustering menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: pg-clustering-postgres name: Clustering parent: pg-postgres-guides weight: 20 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/postgres/clustering/ha_cluster.md b/docs/guides/postgres/clustering/ha_cluster.md index c39d28114..823d93856 100644 --- a/docs/guides/postgres/clustering/ha_cluster.md +++ b/docs/guides/postgres/clustering/ha_cluster.md @@ -1,12 +1,12 @@ --- title: Setup HA Postgres Cluster menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: pg-ha-cluster-clustering name: HA Setup parent: pg-clustering-postgres weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- > New to KubeDB? Please start [here](/docs/concepts/README.md). diff --git a/docs/guides/postgres/clustering/streaming_replication.md b/docs/guides/postgres/clustering/streaming_replication.md index dafc4d6cf..7da635b9f 100644 --- a/docs/guides/postgres/clustering/streaming_replication.md +++ b/docs/guides/postgres/clustering/streaming_replication.md @@ -1,12 +1,12 @@ --- title: Using Postgres Streaming Replication menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: pg-streaming-replication-clustering name: Streaming Replication parent: pg-clustering-postgres weight: 15 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- @@ -34,7 +34,7 @@ NAME STATUS AGE demo Active 5s ``` -> Note: Yaml files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/cli/tree/master/docs/examples/postgres) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: Yaml files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/cli/tree/master/docs/examples/postgres) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). ## Create PostgreSQL with Streaming replication @@ -102,7 +102,7 @@ Here, Now create this Postgres object with Streaming Replication support ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/postgres/clustering/ha-postgres.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/postgres/clustering/ha-postgres.yaml postgres "ha-postgres" created ``` @@ -268,7 +268,7 @@ Here, Now create this Postgres object ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/postgres/clustering/hot-postgres.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/postgres/clustering/hot-postgres.yaml postgres "hot-postgres" created ``` diff --git a/docs/guides/postgres/custom-config/_index.md b/docs/guides/postgres/custom-config/_index.md index 40247c12f..436780629 100755 --- a/docs/guides/postgres/custom-config/_index.md +++ b/docs/guides/postgres/custom-config/_index.md @@ -1,10 +1,10 @@ --- title: Run PostgreSQL with Custom Configuration menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: pg-custom-config name: Custom Configuration parent: pg-postgres-guides weight: 40 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/postgres/custom-config/using-custom-config.md b/docs/guides/postgres/custom-config/using-custom-config.md index f5fe5081f..bc97bf1db 100644 --- a/docs/guides/postgres/custom-config/using-custom-config.md +++ b/docs/guides/postgres/custom-config/using-custom-config.md @@ -1,12 +1,12 @@ --- title: Run PostgreSQL with Custom Configuration menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: pg-custom-config-quickstart name: Quickstart parent: pg-custom-config weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -32,7 +32,7 @@ NAME STATUS AGE demo Active 5s ``` -> Note: Yaml files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/cli/tree/master/docs/examples/postgres) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: Yaml files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/cli/tree/master/docs/examples/postgres) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). ## Overview @@ -57,7 +57,7 @@ shared_buffers=256MB Now, create a configMap with this configuration file. ```console - $ kubectl create configmap -n demo pg-custom-config --from-file=https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/postgres/custom-config/user.conf + $ kubectl create configmap -n demo pg-custom-config --from-file=https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/postgres/custom-config/user.conf configmap/pg-custom-config created ``` @@ -81,7 +81,7 @@ metadata: Now, create Postgres crd specifying `spec.configSource` field. ```console -$ kubectl apply -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/postgres/custom-config/pg-custom-config.yaml +$ kubectl apply -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/postgres/custom-config/pg-custom-config.yaml postgres.kubedb.com/custom-postgres created ``` diff --git a/docs/guides/postgres/custom-versions/_index.md b/docs/guides/postgres/custom-versions/_index.md index 36f4f25d5..712324231 100644 --- a/docs/guides/postgres/custom-versions/_index.md +++ b/docs/guides/postgres/custom-versions/_index.md @@ -1,10 +1,10 @@ --- title: PostgreSQL Custom Versions menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: pg-custom-versions-postgres name: Custom Versions parent: pg-postgres-guides weight: 45 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/postgres/custom-versions/setup.md b/docs/guides/postgres/custom-versions/setup.md index 11c7555d1..e22d503ef 100644 --- a/docs/guides/postgres/custom-versions/setup.md +++ b/docs/guides/postgres/custom-versions/setup.md @@ -1,12 +1,12 @@ --- title: Setup Custom PostgresVersions menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: pg-custom-versions-setup-postgres name: Overview parent: pg-custom-versions-postgres weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -66,7 +66,7 @@ spec: db: image: "myco/postgres:timescale-0.9.1" exporter: - image: "kubedb/operator:0.9.0-beta.1" + image: "kubedb/postgres_exporter:v0.4.6" tools: image: "kubedb/postgres-tools:10.2-v1" ``` diff --git a/docs/guides/postgres/initialization/_index.md b/docs/guides/postgres/initialization/_index.md index 5ecf547cf..d219b23d7 100755 --- a/docs/guides/postgres/initialization/_index.md +++ b/docs/guides/postgres/initialization/_index.md @@ -1,10 +1,10 @@ --- title: PostgreSQL Initialization menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: pg-initialization-postgres name: Initialization parent: pg-postgres-guides weight: 30 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/postgres/initialization/script_source.md b/docs/guides/postgres/initialization/script_source.md index d99b5585d..b1d93bbd4 100644 --- a/docs/guides/postgres/initialization/script_source.md +++ b/docs/guides/postgres/initialization/script_source.md @@ -1,12 +1,12 @@ --- title: Initialize Postgres using Script Source menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: pg-script-source-initialization name: Using Script parent: pg-initialization-postgres weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- @@ -33,7 +33,7 @@ NAME STATUS AGE demo Active 5s ``` -> Note: Yaml files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/cli/tree/master/docs/examples/postgres) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: Yaml files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/cli/tree/master/docs/examples/postgres) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). ## Prepare Initialization Scripts @@ -85,7 +85,7 @@ VolumeSource provided in `init.scriptSource` will be mounted in Pod and will be Now, let's create the Postgres crd which YAML we have shown above, ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/postgres/initialization/script-postgres.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/postgres/initialization/script-postgres.yaml postgres.kubedb.com/script-postgres created ``` diff --git a/docs/guides/postgres/initialization/snapshot_source.md b/docs/guides/postgres/initialization/snapshot_source.md index 6fb17ef85..a36b78f17 100644 --- a/docs/guides/postgres/initialization/snapshot_source.md +++ b/docs/guides/postgres/initialization/snapshot_source.md @@ -1,12 +1,12 @@ --- title: Initialize Postgres using Snapshot Source menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: pg-snapshot-source-initialization name: From Snapshot parent: pg-initialization-postgres weight: 15 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- > Don't know how backup works? Check [tutorial](/docs/guides/postgres/snapshot/instant_backup.md) on Instant Backup. @@ -38,7 +38,7 @@ We need a Snapshot to perform this initialization. If you don't have a Snapshot If you have changed the name of either namespace or snapshot object, please modify the YAMLs used in this tutorial accordingly. -> Note: Yaml files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/cli/tree/master/docs/examples/postgres) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: Yaml files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/cli/tree/master/docs/examples/postgres) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). ## Create PostgreSQL with Snapshot source @@ -90,7 +90,7 @@ instant-snapshot script-postgres Succeeded 56s Now, create the Postgres object. ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/postgres/initialization/recovered-postgres.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/postgres/initialization/recovered-postgres.yaml postgres.kubedb.com/recovered-postgres created ``` diff --git a/docs/guides/postgres/initialization/wal_source.md b/docs/guides/postgres/initialization/wal_source.md index d788097fe..e38237e14 100644 --- a/docs/guides/postgres/initialization/wal_source.md +++ b/docs/guides/postgres/initialization/wal_source.md @@ -1,12 +1,12 @@ --- title: Initialize Postgres from WAL menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: pg-wal-source-initialization name: From WAL parent: pg-initialization-postgres weight: 20 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -94,7 +94,7 @@ postgres=# \q Now, we are ready to proceed for rest of the tutorial. -> Note: Yaml files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/cli/tree/master/docs/examples/postgres) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: Yaml files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/cli/tree/master/docs/examples/postgres) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). ## Create Postgres with WAL source @@ -144,7 +144,7 @@ Here, `{namespace}` & `{postgres-name}` indicates Postgres object whose WAL arch Now, let's create the Postgres object that's YAML has shown above, ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/postgres/initialization/replay-postgres.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/postgres/initialization/replay-postgres.yaml postgres.kubedb.com/replay-postgres created ``` diff --git a/docs/guides/postgres/monitoring/_index.md b/docs/guides/postgres/monitoring/_index.md index fd26b81ce..26a1e7934 100755 --- a/docs/guides/postgres/monitoring/_index.md +++ b/docs/guides/postgres/monitoring/_index.md @@ -1,10 +1,10 @@ --- title: Monitoring PostgreSQL menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: pg-monitoring-postgres name: Monitoring parent: pg-postgres-guides weight: 50 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/postgres/monitoring/using-builtin-prometheus.md b/docs/guides/postgres/monitoring/using-builtin-prometheus.md index ff56ec1f9..ada87e743 100644 --- a/docs/guides/postgres/monitoring/using-builtin-prometheus.md +++ b/docs/guides/postgres/monitoring/using-builtin-prometheus.md @@ -1,12 +1,12 @@ --- title: Monitor PostgreSQL using Builtin Prometheus Discovery menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: pg-using-builtin-prometheus-monitoring name: Builtin Prometheus Discovery parent: pg-monitoring-postgres weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- @@ -33,7 +33,7 @@ NAME STATUS AGE demo Active 5s ``` -> Note: Yaml files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/cli/tree/master/docs/examples/postgres) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: Yaml files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/cli/tree/master/docs/examples/postgres) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). This tutorial assumes that you are familiar with PostgreSQL concept. @@ -67,7 +67,7 @@ Here, Run following command to create example above. ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/postgres/monitoring/builtin-prom-postgres.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/postgres/monitoring/builtin-prom-postgres.yaml postgres.kubedb.com/builtin-prom-postgres created ``` @@ -200,7 +200,7 @@ data: Create above ConfigMap ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/monitoring/builtin-prometheus/demo-1.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/monitoring/builtin-prometheus/demo-1.yaml configmap/prometheus-server-conf created ``` @@ -247,7 +247,7 @@ spec: Run the following command to deploy prometheus-server ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/monitoring/builtin-prometheus/demo-2.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/monitoring/builtin-prometheus/demo-2.yaml clusterrole.rbac.authorization.k8s.io/prometheus-server created serviceaccount/prometheus-server created clusterrolebinding.rbac.authorization.k8s.io/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 58babbcbf..672d4a60d 100644 --- a/docs/guides/postgres/monitoring/using-coreos-prometheus-operator.md +++ b/docs/guides/postgres/monitoring/using-coreos-prometheus-operator.md @@ -1,12 +1,12 @@ --- title: Monitor PostgreSQL using Coreos Prometheus Operator menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: pg-using-coreos-prometheus-operator-monitoring name: Coreos Prometheus Operator parent: pg-monitoring-postgres weight: 15 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -28,7 +28,7 @@ $ kubectl create ns demo namespace "demo" created ``` -> Note: Yaml files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/cli/tree/master/docs/examples/postgres) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: Yaml files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/cli/tree/master/docs/examples/postgres) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). This tutorial assumes that you are familiar with PostgreSQL concept. @@ -37,7 +37,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.9.0-beta.0/docs/examples/monitoring/coreos-operator/demo-0.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/monitoring/coreos-operator/demo-0.yaml namespace/demo created clusterrole.rbac.authorization.k8s.io/prometheus-operator created serviceaccount/prometheus-operator created @@ -68,7 +68,7 @@ servicemonitors.monitoring.coreos.com 2018-09-24T12:42:22Z 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.9.0-beta.0/docs/examples/monitoring/coreos-operator/demo-1.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/monitoring/coreos-operator/demo-1.yaml clusterrole.rbac.authorization.k8s.io/prometheus created serviceaccount/prometheus created clusterrolebinding.rbac.authorization.k8s.io/prometheus created @@ -147,7 +147,7 @@ Here, Now create PostgreSQL with monitoring spec ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/postgres/monitoring/coreos-prom-postgres.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/postgres/monitoring/coreos-prom-postgres.yaml postgres.kubedb.com/coreos-prom-postgres created ``` diff --git a/docs/guides/postgres/private-registry/_index.md b/docs/guides/postgres/private-registry/_index.md index 62285dde1..f26071e46 100755 --- a/docs/guides/postgres/private-registry/_index.md +++ b/docs/guides/postgres/private-registry/_index.md @@ -1,10 +1,10 @@ --- title: Run PostgreSQL using Private Registry menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: pg-private-registry-postgres name: Private Registry parent: pg-postgres-guides weight: 35 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/postgres/private-registry/using-private-registry.md b/docs/guides/postgres/private-registry/using-private-registry.md index 58129ec9d..da0bfcf1b 100644 --- a/docs/guides/postgres/private-registry/using-private-registry.md +++ b/docs/guides/postgres/private-registry/using-private-registry.md @@ -1,12 +1,12 @@ --- title: Run PostgreSQL using Private Registry menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: pg-using-private-registry-private-registry name: Quickstart parent: pg-private-registry-postgres weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -30,7 +30,7 @@ NAME STATUS AGE demo Active 5s ``` -> Note: Yaml files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/cli/tree/master/docs/examples/postgres) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: Yaml files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/cli/tree/master/docs/examples/postgres) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). ## Prepare Private Docker Registry You will also need a docker private [registry](https://docs.docker.com/registry/) or [private repository](https://docs.docker.com/docker-hub/repos/#private-repositories). In this tutorial we will use private repository of [docker hub](https://hub.docker.com/). @@ -47,7 +47,7 @@ For Postgres, push the following images to your private registry. ```console $ export DOCKER_REGISTRY= -$ 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/operator:0.9.0-rc.0 ; docker tag kubedb/operator:0.9.0-rc.0 $DOCKER_REGISTRY/operator:0.9.0-rc.0 ; docker push $DOCKER_REGISTRY/operator:0.9.0-rc.0 $ docker pull kubedb/postgres:9.6-v1 ; docker tag kubedb/postgres:9.6-v1 $DOCKER_REGISTRY/postgres:9.6-v1 ; docker push $DOCKER_REGISTRY/postgres:9.6-v1 $ docker pull kubedb/postgres-tools:9.6-v1 ; docker tag kubedb/postgres-tools:9.6-v1 $DOCKER_REGISTRY/postgres-tools:9.6-v1 ; docker push $DOCKER_REGISTRY/postgres-tools:9.6-v1 $ docker pull kubedb/postgres_exporter:v0.4.6 ; docker tag kubedb/postgres_exporter:v0.4.6 $DOCKER_REGISTRY/postgres_exporter:v0.4.6 ; docker push $DOCKER_REGISTRY/postgres_exporter:v0.4.6 @@ -138,7 +138,7 @@ spec: Now run the command to create this Postgres object: ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/postgres/private-registry/pvt-reg-postgres.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/postgres/private-registry/pvt-reg-postgres.yaml postgres.kubedb.com/pvt-reg-postgres created ``` diff --git a/docs/guides/postgres/quickstart/_index.md b/docs/guides/postgres/quickstart/_index.md index 080fcbcba..f088a2a2c 100755 --- a/docs/guides/postgres/quickstart/_index.md +++ b/docs/guides/postgres/quickstart/_index.md @@ -1,10 +1,10 @@ --- title: PostgreSQL Quickstart menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: pg-quickstart-postgres name: Quickstart parent: pg-postgres-guides weight: 15 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/postgres/quickstart/quickstart.md b/docs/guides/postgres/quickstart/quickstart.md index f496c2c14..08f2c0072 100644 --- a/docs/guides/postgres/quickstart/quickstart.md +++ b/docs/guides/postgres/quickstart/quickstart.md @@ -1,12 +1,12 @@ --- title: PostgreSQL Quickstart menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: pg-quickstart-quickstart name: Overview parent: pg-quickstart-postgres weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -36,7 +36,7 @@ NAME STATUS AGE demo Active 5s ``` -> Note: Yaml files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/cli/tree/master/docs/examples/postgres) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: Yaml files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/cli/tree/master/docs/examples/postgres) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). >We have designed this tutorial to demonstrate a production setup of KubeDB managed PostgreSQL. If you just want to try out KubeDB, you can bypass some of the safety features following the tips [here](/docs/guides/postgres/quickstart/quickstart.md#tips-for-testing). @@ -47,7 +47,7 @@ This tutorial will also use a pgAdmin to connect and test PostgreSQL database, o Run the following command to install pgAdmin, ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/postgres/quickstart/pgadmin.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/postgres/quickstart/pgadmin.yaml deployment.apps/pgadmin created service/pgadmin created @@ -137,7 +137,7 @@ Here, Let's create Postgres crd, ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/postgres/quickstart/quick-postgres.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/postgres/quickstart/quick-postgres.yaml postgres "quick-postgres" created ``` @@ -415,7 +415,7 @@ In this tutorial, the DormantDatabase `quick-postgres` can be resumed by creatin Let's create the original Postgres object, ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.0/docs/examples/postgres/kubectl apply -f ./quickstart/quick-postgres.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/postgres/kubectl apply -f ./quickstart/quick-postgres.yaml postgres.kubedb.com/quick-postgres created ``` @@ -424,7 +424,7 @@ This will resume the previous database. All data that was inserted in previous d When the database is resumed, respective DormantDatabase object will be removed. Verify that the DormantDatabase object has been removed, ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/postgres/quickstart/quick-postgres.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.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 501351770..1522a14e4 100644 --- a/docs/guides/postgres/quickstart/rbac.md +++ b/docs/guides/postgres/quickstart/rbac.md @@ -1,12 +1,12 @@ --- title: RBAC for PostgreSQL menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: pg-rbac-quickstart name: RBAC parent: pg-quickstart-postgres weight: 15 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -41,7 +41,7 @@ NAME STATUS AGE demo Active 5s ``` -> Note: Yaml files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/cli/tree/master/docs/examples/postgres) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: Yaml files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/cli/tree/master/docs/examples/postgres) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). ## Create a PostgreSQL database @@ -69,7 +69,7 @@ spec: Create above Postgres object with following command ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/postgres/quickstart/quick-postgres.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/postgres/quickstart/quick-postgres.yaml postgres "quick-postgres" created ``` diff --git a/docs/guides/postgres/snapshot/_index.md b/docs/guides/postgres/snapshot/_index.md index e633e89fe..ba8945733 100755 --- a/docs/guides/postgres/snapshot/_index.md +++ b/docs/guides/postgres/snapshot/_index.md @@ -1,10 +1,10 @@ --- title: PostgreSQL Snapshotting menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: pg-snapshot-postgres name: Snapshotting parent: pg-postgres-guides weight: 25 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/postgres/snapshot/continuous_archiving.md b/docs/guides/postgres/snapshot/continuous_archiving.md index a5bd16c18..9624c78f1 100644 --- a/docs/guides/postgres/snapshot/continuous_archiving.md +++ b/docs/guides/postgres/snapshot/continuous_archiving.md @@ -1,12 +1,12 @@ --- title: Continuous Archiving of PostgreSQL menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: pg-continuous-archiving-snapshot name: WAL Archiving parent: pg-snapshot-postgres weight: 20 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -32,7 +32,7 @@ NAME STATUS AGE demo Active 5s ``` -> Note: Yaml files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/cli/tree/master/docs/examples/postgres) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: Yaml files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/cli/tree/master/docs/examples/postgres) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). ## Create PostgreSQL with Continuous Archiving @@ -144,7 +144,7 @@ To configure this backend, following parameters are available: Now create this Postgres object with Continuous Archiving support. ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/postgres/snapshot/wal-postgres.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.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 6fc78c107..786801e8d 100644 --- a/docs/guides/postgres/snapshot/instant_backup.md +++ b/docs/guides/postgres/snapshot/instant_backup.md @@ -1,12 +1,12 @@ --- title: Instant Backup of PostgreSQL menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: pg-instant-backup-snapshot name: Instant Backup parent: pg-snapshot-postgres weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -34,7 +34,7 @@ NAME STATUS AGE demo Active 5s ``` -> Note: Yaml files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/cli/tree/master/docs/examples/postgres) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: Yaml files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/cli/tree/master/docs/examples/postgres) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). ## Prepare Database @@ -126,7 +126,7 @@ To learn how to configure other storage destinations for snapshot data, please v Now, let's create a Snapshot object. ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/postgres/snapshot/instant-snapshot.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/postgres/snapshot/instant-snapshot.yaml snapshot.kubedb.com/instant-snapshot created ``` diff --git a/docs/guides/postgres/snapshot/scheduled_backup.md b/docs/guides/postgres/snapshot/scheduled_backup.md index 289fd622b..81554286c 100644 --- a/docs/guides/postgres/snapshot/scheduled_backup.md +++ b/docs/guides/postgres/snapshot/scheduled_backup.md @@ -1,12 +1,12 @@ --- title: Scheduled Backup of PostgreSQL menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: pg-scheduled-backup-snapshot name: Scheduled Backup parent: pg-snapshot-postgres weight: 15 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- > Don't know how backup works? Check [tutorial](/docs/guides/postgres/snapshot/instant_backup.md) on Instant Backup. @@ -32,7 +32,7 @@ NAME STATUS AGE demo Active 5s ``` -> Note: Yaml files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/cli/tree/master/docs/examples/postgres) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: Yaml files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/cli/tree/master/docs/examples/postgres) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). ## Create Postgres with BackupSchedule @@ -93,7 +93,7 @@ Here, Let's create a Postgres crd with backupSchedule, ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/postgres/snapshot/scheduled-pg.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.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 cbb9a9729..4330c3fa4 100644 --- a/docs/guides/redis/README.md +++ b/docs/guides/redis/README.md @@ -1,16 +1,16 @@ --- title: Redis menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: rd-readme-redis name: Redis parent: rd-redis-guides weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides -url: /docs/0.8.0/guides/redis/ +url: /docs/0.9.0-rc.0/guides/redis/ aliases: - - /docs/0.8.0/guides/redis/README/ + - /docs/0.9.0-rc.0/guides/redis/README/ --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -42,13 +42,24 @@ aliases: ## Supported Redis Versions -| KubeDB Version | Redis:4, 4.0, 4.0.6 | 4-v1, 4.0-v1, 4.0.6-v1 | -| :------------: | :-----------------: | :--------------------: | -| 0.1.0 - 0.7.0 | ✗ | ✗ | -| 0.8.0 | ✓ | ✗ | -| 0.9.0-beta.1 | ✗ | ✓ | +| KubeDB Version | Redis:4.0.6 | +|:--------------:|:-----------:| +| 0.1.0 - 0.7.0 | ✗ | +| 0.8.0 | ✓ | +| 0.9.0-rc.0 | ✓ | -
+## Supported RedisVersion CRD + +Here, ✓ means supported and ✗ means deprecated. + +| NAME | VERSION | KubeDB: 0.9.0-rc.0 | +|----------|---------|--------------------| +| 4 | 4 | ✗ | +| 4-v1 | 4 | ✓ | +| 4.0 | 4.0 | ✗ | +| 4.0-v1 | 4.0 | ✓ | +| 4.0.6 | 4.0.6 | ✗ | +| 4.0.6-v1 | 4.0.6 | ✓ | ## User Guide diff --git a/docs/guides/redis/_index.md b/docs/guides/redis/_index.md index c2f71ecdb..ebdb8d4fb 100644 --- a/docs/guides/redis/_index.md +++ b/docs/guides/redis/_index.md @@ -1,10 +1,10 @@ --- title: Redis menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: rd-redis-guides name: Redis parent: guides weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/redis/cli/_index.md b/docs/guides/redis/cli/_index.md index 7a5264606..90005effd 100755 --- a/docs/guides/redis/cli/_index.md +++ b/docs/guides/redis/cli/_index.md @@ -1,10 +1,10 @@ --- title: CLI | KubeDB menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: rd-cli-redis name: Cli parent: rd-redis-guides weight: 45 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/redis/cli/cli.md b/docs/guides/redis/cli/cli.md index b04e88140..a31561d35 100644 --- a/docs/guides/redis/cli/cli.md +++ b/docs/guides/redis/cli/cli.md @@ -1,12 +1,12 @@ --- title: CLI | KubeDB menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: rd-cli-cli name: Quickstart parent: rd-cli-redis weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- diff --git a/docs/guides/redis/custom-config/_index.md b/docs/guides/redis/custom-config/_index.md index 3ab77ddbd..71c86617b 100755 --- a/docs/guides/redis/custom-config/_index.md +++ b/docs/guides/redis/custom-config/_index.md @@ -1,10 +1,10 @@ --- title: Run Redis with Custom Configuration menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: rd-custom-config name: Custom Configuration parent: rd-redis-guides weight: 50 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/redis/custom-config/using-custom-config.md b/docs/guides/redis/custom-config/using-custom-config.md index 74fb80789..d3ed6cf76 100644 --- a/docs/guides/redis/custom-config/using-custom-config.md +++ b/docs/guides/redis/custom-config/using-custom-config.md @@ -1,12 +1,12 @@ --- title: Run Redis with Custom Configuration menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: rd-custom-config-quickstart name: Quickstart parent: rd-custom-config weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -32,7 +32,7 @@ KubeDB supports providing custom configuration for Redis. This tutorial will sho demo Active 5s ``` -> Note: Yaml files used in this tutorial are stored in [docs/examples/redis](https://github.com/kubedb/cli/tree/master/docs/examples/redis) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: Yaml files used in this tutorial are stored in [docs/examples/redis](https://github.com/kubedb/cli/tree/master/docs/examples/redis) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). ## Overview @@ -84,7 +84,7 @@ metadata: Now, create Redis crd specifying `spec.configSource` field. ```console -$ kubectl apply -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/redis/custom-config/redis-custom.yaml +$ kubectl apply -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/redis/custom-config/redis-custom.yaml redis.kubedb.com "custom-redis" created ``` diff --git a/docs/guides/redis/monitoring/_index.md b/docs/guides/redis/monitoring/_index.md index 8c0f41f54..cf187987b 100755 --- a/docs/guides/redis/monitoring/_index.md +++ b/docs/guides/redis/monitoring/_index.md @@ -1,10 +1,10 @@ --- title: Monitoring Redis menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: rd-monitoring-redis name: Monitoring parent: rd-redis-guides weight: 25 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/redis/monitoring/using-builtin-prometheus.md b/docs/guides/redis/monitoring/using-builtin-prometheus.md index 7bf153fb7..f9beafa7f 100644 --- a/docs/guides/redis/monitoring/using-builtin-prometheus.md +++ b/docs/guides/redis/monitoring/using-builtin-prometheus.md @@ -1,12 +1,12 @@ --- title: Monitoring Redis Using Builtin Prometheus Discovery menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: rd-using-builtin-prometheus-monitoring name: Builtin Prometheus Discovery parent: rd-monitoring-redis weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- @@ -33,7 +33,7 @@ This tutorial will show you how to monitor KubeDB databases using [Prometheus](h demo Active 10s ``` -> Note: The yaml files used in this tutorial are stored in [docs/examples/redis](https://github.com/kubedb/cli/tree/master/docs/examples/redis) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: The yaml files used in this tutorial are stored in [docs/examples/redis](https://github.com/kubedb/cli/tree/master/docs/examples/redis) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). ## Monitor with builtin Prometheus @@ -59,7 +59,7 @@ spec: ``` ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/redis/monitoring/builtin-prometheus/demo-1.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/redis/monitoring/builtin-prometheus/demo-1.yaml redis.kubedb.com/redis-mon-prometheus created ``` @@ -254,7 +254,7 @@ data: Create above ConfigMap ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/monitoring/builtin-prometheus/demo-1.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/monitoring/builtin-prometheus/demo-1.yaml configmap/prometheus-server-conf created ``` @@ -301,7 +301,7 @@ spec: Run the following command to deploy prometheus-server ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/monitoring/builtin-prometheus/demo-2.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/monitoring/builtin-prometheus/demo-2.yaml clusterrole.rbac.authorization.k8s.io/prometheus-server created serviceaccount/prometheus-server created clusterrolebinding.rbac.authorization.k8s.io/prometheus-server created @@ -362,7 +362,7 @@ kubectl delete -n demo rd/redis-mon-prometheus kubectl patch -n demo drmn/redis-mon-prometheus -p '{"spec":{"wipeOut":true}}' --type="merge" kubectl delete -n demo drmn/redis-mon-prometheus -kubectl delete -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/monitoring/builtin-prometheus/demo-2.yaml +kubectl delete -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/monitoring/builtin-prometheus/demo-2.yaml kubectl delete ns demo ``` diff --git a/docs/guides/redis/monitoring/using-coreos-prometheus-operator.md b/docs/guides/redis/monitoring/using-coreos-prometheus-operator.md index a40c561a1..d668ef6e6 100644 --- a/docs/guides/redis/monitoring/using-coreos-prometheus-operator.md +++ b/docs/guides/redis/monitoring/using-coreos-prometheus-operator.md @@ -1,12 +1,12 @@ --- title: Monitoring Redis using Coreos Prometheus Operator menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: rd-using-coreos-prometheus-operator-monitoring name: Coreos Prometheus Operator parent: rd-monitoring-redis weight: 15 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -32,14 +32,14 @@ This tutorial will show you how to monitor KubeDB databases using Prometheus via demo Active 10s ``` -> Note: The yaml files used in this tutorial are stored in [docs/examples/redis](https://github.com/kubedb/cli/tree/master/docs/examples/redis) folder in github repository [kubedb/cli](https://github.com/kubedb/cli). +> Note: The yaml files used in this tutorial are stored in [docs/examples/redis](https://github.com/kubedb/cli/tree/master/docs/examples/redis) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli). ## Deploy CoreOS-Prometheus Operator Run the following command to deploy CoreOS-Prometheus operator. ```console -$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/monitoring/coreos-operator/demo-0.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/monitoring/coreos-operator/demo-0.yaml namespace/demo created clusterrole.rbac.authorization.k8s.io/prometheus-operator created serviceaccount/prometheus-operator created @@ -70,7 +70,7 @@ servicemonitors.monitoring.coreos.com 2018-09-24T12:42:22Z 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.9.0-beta.1/docs/examples/monitoring/coreos-operator/demo-1.yaml +$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/monitoring/coreos-operator/demo-1.yaml clusterrole.rbac.authorization.k8s.io/prometheus created serviceaccount/prometheus created clusterrolebinding.rbac.authorization.k8s.io/prometheus created @@ -170,7 +170,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.9.0-beta.1/docs/examples/redis/monitoring/coreos-operator/demo-1.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/redis/monitoring/coreos-operator/demo-1.yaml redis.kubedb.com/redis-mon-coreos created ``` @@ -302,8 +302,8 @@ kubectl delete -n demo rd/redis-mon-coreos kubectl patch -n demo drmn/redis-mon-coreos -p '{"spec":{"wipeOut":true}}' --type="merge" kubectl delete -n demo drmn/redis-mon-coreos -kubectl delete -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/monitoring/coreos-operator/demo-1.yaml -kubectl delete -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/monitoring/coreos-operator/demo-0.yaml +kubectl delete -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/monitoring/coreos-operator/demo-1.yaml +kubectl delete -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/monitoring/coreos-operator/demo-0.yaml kubectl delete ns demo ``` diff --git a/docs/guides/redis/private-registry/_index.md b/docs/guides/redis/private-registry/_index.md index a575b030b..fd03b1455 100755 --- a/docs/guides/redis/private-registry/_index.md +++ b/docs/guides/redis/private-registry/_index.md @@ -1,10 +1,10 @@ --- title: Run Redis using Private Registry menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: rd-private-registry-redis name: Private Registry parent: rd-redis-guides weight: 20 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/redis/private-registry/using-private-registry.md b/docs/guides/redis/private-registry/using-private-registry.md index c736b4642..c1f4af614 100644 --- a/docs/guides/redis/private-registry/using-private-registry.md +++ b/docs/guides/redis/private-registry/using-private-registry.md @@ -1,12 +1,12 @@ --- title: Run Redis using Private Registry menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: rd-using-private-registry-private-registry name: Quickstart parent: rd-private-registry-redis weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- @@ -119,7 +119,7 @@ spec: Now run the command to deploy this `Redis` object: ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/redis/private-registry/demo-2.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/redis/private-registry/demo-2.yaml redis.kubedb.com/redis-pvt-reg created ``` diff --git a/docs/guides/redis/quickstart/_index.md b/docs/guides/redis/quickstart/_index.md index 4b8869a8e..b6563faf2 100755 --- a/docs/guides/redis/quickstart/_index.md +++ b/docs/guides/redis/quickstart/_index.md @@ -1,10 +1,10 @@ --- title: Redis Quickstart menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: rd-quickstart-redis name: Quickstart parent: rd-redis-guides weight: 15 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/guides/redis/quickstart/quickstart.md b/docs/guides/redis/quickstart/quickstart.md index cf3345701..cfa0aec95 100644 --- a/docs/guides/redis/quickstart/quickstart.md +++ b/docs/guides/redis/quickstart/quickstart.md @@ -1,12 +1,12 @@ --- title: Redis Quickstart menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: rd-quickstart-quickstart name: Overview parent: rd-quickstart-redis weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: guides --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -84,7 +84,7 @@ spec: ``` ```console -$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/docs/examples/redis/quickstart/demo-1.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/redis/quickstart/demo-1.yaml redis.kubedb.com/redis-quickstart created ``` @@ -92,7 +92,7 @@ Here, - `spec.version` is name of the RedisVersion crd where the docker images are specified. In this tutorial, a Redis 4.0-v1 database is created. - `spec.storageType` specifies the type of storage that will be used for Redis database. It can be `Durable` or `Ephemeral`. Default value of this field is `Durable`. If `Ephemeral` is used then KubeDB will create Redis database using `EmptyDir` volume. In this case, you don't have to specify `spec.storage` field. This is useful for testing purpose. -- `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. Since release 0.8.0, a storage spec is required for Redis. +- `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 `Redis` crd or which resources KubeDB should keep or delete when you delete `Redis` 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/concepts/databases/redis.md#specterminationpolicy) > Note: spec.storage section is used to create PVC for database pod. It will create PVC with storage size specified instorage.resources.requests field. Don't specify limits here. PVC does not get resized automatically. @@ -328,7 +328,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.9.0-beta.1/docs/examples/redis/quickstart/demo-1.yaml +$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/redis/quickstart/demo-1.yaml redis.kubedb.com/redis-quickstart created ``` diff --git a/docs/reference/_index.md b/docs/reference/_index.md index 77fb61e50..bdeb51f96 100644 --- a/docs/reference/_index.md +++ b/docs/reference/_index.md @@ -2,9 +2,9 @@ title: Reference description: KubeDB CLI Reference menu: - docs_0.9.0-beta.1: + docs_0.9.0-rc.0: identifier: reference name: Reference weight: 1000 -menu_name: docs_0.9.0-beta.1 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/reference/kubedb.md b/docs/reference/kubedb.md index 3fef2b8c0..cee50f491 100644 --- a/docs/reference/kubedb.md +++ b/docs/reference/kubedb.md @@ -1,16 +1,16 @@ --- title: Kubedb menu: - docs_0.9.0-beta.1: + docs_0.9.0-rc.0: identifier: kubedb name: Kubedb parent: reference weight: 0 -menu_name: docs_0.9.0-beta.1 +menu_name: docs_0.9.0-rc.0 section_menu_id: reference aliases: - - /docs/0.9.0-beta.1/reference/ + - /docs/0.9.0-rc.0/reference/ --- ## kubedb diff --git a/docs/reference/kubedb_api-resources.md b/docs/reference/kubedb_api-resources.md index 2c2200a4a..c64201dea 100644 --- a/docs/reference/kubedb_api-resources.md +++ b/docs/reference/kubedb_api-resources.md @@ -1,11 +1,11 @@ --- title: Kubedb Api-Resources menu: - docs_0.9.0-beta.1: + docs_0.9.0-rc.0: identifier: kubedb-api-resources name: Kubedb Api-Resources parent: reference -menu_name: docs_0.9.0-beta.1 +menu_name: docs_0.9.0-rc.0 section_menu_id: reference --- ## kubedb api-resources diff --git a/docs/reference/kubedb_create.md b/docs/reference/kubedb_create.md index 6767a8a94..ef4b30b6a 100644 --- a/docs/reference/kubedb_create.md +++ b/docs/reference/kubedb_create.md @@ -1,11 +1,11 @@ --- title: Kubedb Create menu: - docs_0.9.0-beta.1: + docs_0.9.0-rc.0: identifier: kubedb-create name: Kubedb Create parent: reference -menu_name: docs_0.9.0-beta.1 +menu_name: docs_0.9.0-rc.0 section_menu_id: reference --- ## kubedb create @@ -40,7 +40,7 @@ kubedb create -f FILENAME --edit Edit the API resource before creating -f, --filename strings Filename, directory, or URL to files to use to create the resource -h, --help help for create - -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]. + -o, --output string Output format. One of: json|yaml|name|template|go-template|go-template-file|templatefile|jsonpath|jsonpath-file. --raw string Raw URI to POST to the server. Uses the transport specified by the kubeconfig file. --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. diff --git a/docs/reference/kubedb_delete.md b/docs/reference/kubedb_delete.md index 32d63aad2..d0d0a0310 100644 --- a/docs/reference/kubedb_delete.md +++ b/docs/reference/kubedb_delete.md @@ -1,11 +1,11 @@ --- title: Kubedb Delete menu: - docs_0.9.0-beta.1: + docs_0.9.0-rc.0: identifier: kubedb-delete name: Kubedb Delete parent: reference -menu_name: docs_0.9.0-beta.1 +menu_name: docs_0.9.0-rc.0 section_menu_id: reference --- ## kubedb delete diff --git a/docs/reference/kubedb_describe.md b/docs/reference/kubedb_describe.md index 80ea16d64..d5698d9d6 100644 --- a/docs/reference/kubedb_describe.md +++ b/docs/reference/kubedb_describe.md @@ -1,11 +1,11 @@ --- title: Kubedb Describe menu: - docs_0.9.0-beta.1: + docs_0.9.0-rc.0: identifier: kubedb-describe name: Kubedb Describe parent: reference -menu_name: docs_0.9.0-beta.1 +menu_name: docs_0.9.0-rc.0 section_menu_id: reference --- ## kubedb describe diff --git a/docs/reference/kubedb_edit.md b/docs/reference/kubedb_edit.md index 700f65b91..e29d78ee2 100644 --- a/docs/reference/kubedb_edit.md +++ b/docs/reference/kubedb_edit.md @@ -1,11 +1,11 @@ --- title: Kubedb Edit menu: - docs_0.9.0-beta.1: + docs_0.9.0-rc.0: identifier: kubedb-edit name: Kubedb Edit parent: reference -menu_name: docs_0.9.0-beta.1 +menu_name: docs_0.9.0-rc.0 section_menu_id: reference --- ## kubedb edit @@ -39,7 +39,7 @@ kubedb edit (RESOURCE/NAME | -f FILENAME) -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-file|jsonpath. + -o, --output string Output format. One of: json|yaml|name|go-template|go-template-file|templatefile|template|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. diff --git a/docs/reference/kubedb_get.md b/docs/reference/kubedb_get.md index 31bb89f5f..c2b4f8a95 100644 --- a/docs/reference/kubedb_get.md +++ b/docs/reference/kubedb_get.md @@ -1,11 +1,11 @@ --- title: Kubedb Get menu: - docs_0.9.0-beta.1: + docs_0.9.0-rc.0: identifier: kubedb-get name: Kubedb Get parent: reference -menu_name: docs_0.9.0-beta.1 +menu_name: docs_0.9.0-rc.0 section_menu_id: reference --- ## kubedb get @@ -79,7 +79,6 @@ kubedb get [(-o|--output=)json|yaml|wide|custom-columns=...|custom-columns-file= --show-labels When printing, show all labels as the last column (default hide labels column) --sort-by string If non-empty, sort list types using this field specification. The field specification is expressed as a JSONPath expression (e.g. '{.metadata.name}'). The field in the API resource specified by this JSONPath expression must be an integer or a string. --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]. - --use-openapi-print-columns If true, use x-kubernetes-print-column metadata (if present) from the OpenAPI schema for displaying a resource. -w, --watch After listing/getting the requested object, watch for changes. Uninitialized objects are excluded if no object name is provided. --watch-only Watch for changes to the requested object(s), without listing/getting first. ``` diff --git a/docs/reference/kubedb_version.md b/docs/reference/kubedb_version.md index 44bbde967..7c92da296 100644 --- a/docs/reference/kubedb_version.md +++ b/docs/reference/kubedb_version.md @@ -1,11 +1,11 @@ --- title: Kubedb Version menu: - docs_0.9.0-beta.1: + docs_0.9.0-rc.0: identifier: kubedb-version name: Kubedb Version parent: reference -menu_name: docs_0.9.0-beta.1 +menu_name: docs_0.9.0-rc.0 section_menu_id: reference --- ## kubedb version diff --git a/docs/roadmap.md b/docs/roadmap.md index 95018745a..c7f477edd 100644 --- a/docs/roadmap.md +++ b/docs/roadmap.md @@ -2,16 +2,16 @@ title: Roadmap | KubeDB description: Roadmap of KubeDB menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: roadmap-cli name: Roadmap parent: welcome weight: 15 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: welcome -url: /docs/0.8.0/welcome/roadmap/ +url: /docs/0.9.0-rc.0/welcome/roadmap/ aliases: - - /docs/0.8.0/roadmap/ + - /docs/0.9.0-rc.0/roadmap/ --- # Project Status diff --git a/docs/setup/README.md b/docs/setup/README.md index 182d96290..d2cfa05f1 100644 --- a/docs/setup/README.md +++ b/docs/setup/README.md @@ -2,16 +2,16 @@ title: Table of Contents | Setup description: Table of Contents | Setup menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: setup-readme name: Readme parent: setup weight: -1 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: setup -url: /docs/0.8.0/setup/ +url: /docs/0.9.0-rc.0/setup/ aliases: - - /docs/0.8.0/setup/README/ + - /docs/0.9.0-rc.0/setup/README/ --- # Setup diff --git a/docs/setup/_index.md b/docs/setup/_index.md index 2108d43fe..8392cd4c2 100644 --- a/docs/setup/_index.md +++ b/docs/setup/_index.md @@ -1,9 +1,9 @@ --- title: Setup | KubeDB menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: setup name: Setup weight: 30 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/setup/developer-guide/_index.md b/docs/setup/developer-guide/_index.md index ce2b9e5e7..3c968d169 100644 --- a/docs/setup/developer-guide/_index.md +++ b/docs/setup/developer-guide/_index.md @@ -1,10 +1,10 @@ --- title: Developer Guide menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: developer-guide name: Developer Guide parent: setup weight: 40 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 --- diff --git a/docs/setup/developer-guide/overview.md b/docs/setup/developer-guide/overview.md index 4b5b8169a..e3a20452a 100644 --- a/docs/setup/developer-guide/overview.md +++ b/docs/setup/developer-guide/overview.md @@ -1,15 +1,15 @@ --- title: Developer Guide menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: developer-guide-readme name: Overview parent: developer-guide weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: setup aliases: - - /docs/0.8.0/setup/developer-guide/ + - /docs/0.9.0-rc.0/setup/developer-guide/ --- # Development Guide diff --git a/docs/setup/developer-guide/release.md b/docs/setup/developer-guide/release.md index 23230751a..9dc982e3d 100644 --- a/docs/setup/developer-guide/release.md +++ b/docs/setup/developer-guide/release.md @@ -1,12 +1,12 @@ --- title: Release menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: developer-guide-release name: Release Process parent: developer-guide weight: 20 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: setup --- diff --git a/docs/setup/install.md b/docs/setup/install.md index b14846987..fe6cd63b5 100644 --- a/docs/setup/install.md +++ b/docs/setup/install.md @@ -1,12 +1,12 @@ --- title: Install menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: install-kubedb name: Install parent: setup weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: setup --- @@ -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.9.0-beta.1/hack/deploy/kubedb.sh | bash +$ curl -fsSL https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.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.9.0-beta.1/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-rc.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.9.0-beta.1/hack/deploy/kubedb.sh | bash -s -- -h +$ curl -fsSL https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/hack/deploy/kubedb.sh | bash -s -- -h kubedb.sh - install kubedb operator kubedb.sh [options] @@ -79,7 +79,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.9.0-beta.1/hack/deploy/kubedb.sh \ +$ curl -fsSL https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/hack/deploy/kubedb.sh \ | bash -s -- --run-on-master [--rbac] ``` @@ -87,7 +87,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.9.0-beta.1/hack/deploy/kubedb.sh \ +$ curl -fsSL https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/hack/deploy/kubedb.sh \ | bash -s -- --namespace=kubedb [--run-on-master] [--rbac] ``` @@ -97,23 +97,23 @@ 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.9.0-beta.1/hack/deploy/kubedb.sh \ +$ curl -fsSL https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.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.9.0-beta.1/hack/deploy/kubedb.sh \ +$ curl -fsSL https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/hack/deploy/kubedb.sh \ | bash -s -- --enable-validating-webhook=false --enable-mutating-webhook=false [--rbac] ``` -KubeDB 0.9.0 or later releases can use status sub resource for CustomResourceDefintions. This is enabled by default for Kubernetes 1.11.0 or later releases. To disable this feature, pass the `--enable-status-subresource=false` flag. +KubeDB 0.9.0-rc.0 or later releases can use status sub resource for CustomResourceDefintions. This is enabled by default for Kubernetes 1.11.0 or later releases. To disable this feature, pass the `--enable-status-subresource=false` flag. -KubeDB 0.9.0 or later installs a catalog of database versions. To disable this pass the `--install-catalog=none` flag. +KubeDB 0.9.0-rc.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.9.0-beta.1/hack/deploy/kubedb.sh \ +$ curl -fsSL https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/hack/deploy/kubedb.sh \ | bash -s -- --install-catalog=none [--rbac] ``` @@ -129,11 +129,11 @@ $ 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.9.0-beta.1 0.9.0-beta.1 KubeDB by AppsCode - Production ready databases on Kubern... -appscode/kubedb-catalog 0.9.0-beta.1 0.9.0-beta.1 KubeDB Catalog by AppsCode - Catalog for database versions +appscode/kubedb 0.9.0-rc.0 0.9.0-rc.0 KubeDB by AppsCode - Production ready databases on Kubern... +appscode/kubedb-catalog 0.9.0-rc.0 0.9.0-rc.0 KubeDB Catalog by AppsCode - Catalog for database versions # Step 1: Install kubedb operator chart -$ helm install appscode/kubedb --name kubedb-operator --version 0.9.0-beta.1 \ +$ helm install appscode/kubedb --name kubedb-operator --version 0.9.0-rc.0 \ --namespace kube-system # Step 2: wait until crds are registered @@ -157,11 +157,11 @@ redisversions.kubedb.com 6s snapshots.kubedb.com 6s # Step 3(a): Install KubeDB catalog of database versions -$ helm install appscode/kubedb-catalog --name kubedb-catalog --version 0.9.0-beta.1 \ +$ helm install appscode/kubedb-catalog --name kubedb-catalog --version 0.9.0-rc.0 \ --namespace kube-system # Step 3(b): Or, if previously installed, upgrade KubeDB catalog of database versions -$ helm upgrade kubedb-catalog appscode/kubedb-catalog --version 0.9.0-beta.1 \ +$ helm upgrade kubedb-catalog appscode/kubedb-catalog --version 0.9.0-rc.0 \ --namespace kube-system ``` @@ -205,12 +205,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.9.0-beta.1/kubedb-linux-amd64 \ +wget -O kubedb https://github.com/kubedb/cli/releases/download/0.9.0-rc.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.9.0-beta.1/kubedb-darwin-amd64 \ +wget -O kubedb https://github.com/kubedb/cli/releases/download/0.9.0-rc.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 8c9056077..c15be2bb5 100644 --- a/docs/setup/uninstall.md +++ b/docs/setup/uninstall.md @@ -1,12 +1,12 @@ --- title: KubeDB Uninstall menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: uninstall-kubedb name: Uninstall parent: setup weight: 20 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: setup --- @@ -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.9.0-beta.1/hack/deploy/kubedb.sh \ +$ curl -fsSL https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/hack/deploy/kubedb.sh \ | bash -s -- --uninstall [--namespace=NAMESPACE] + kubectl delete deployment -l app=kubedb -n kube-system diff --git a/docs/support.md b/docs/support.md index b921f2a63..2208354d9 100644 --- a/docs/support.md +++ b/docs/support.md @@ -2,16 +2,16 @@ title: Support | KubeDB description: Support menu: - docs_0.9.0-beta.0: + docs_0.9.0-rc.0: identifier: support-cli name: Support parent: welcome weight: 10 -menu_name: docs_0.9.0-beta.0 +menu_name: docs_0.9.0-rc.0 section_menu_id: welcome -url: /docs/0.8.0/welcome/support/ +url: /docs/0.9.0-rc.0/welcome/support/ aliases: - - /docs/0.8.0/support/ + - /docs/0.9.0-rc.0/support/ --- # Support diff --git a/glide.lock b/glide.lock index 274aab8c7..1f066835d 100644 --- a/glide.lock +++ b/glide.lock @@ -1,5 +1,5 @@ -hash: cfc5cdba9ab0ce4ba240fd58402cdf494cc54cb1a243d95eea6ea1e2b4a429d4 -updated: 2018-10-13T14:49:52.619655025-07:00 +hash: bf6e31594783ad276ef60937fcf3809bc4130f8156dd516a443d1092e252b415 +updated: 2018-10-14T08:44:41.14388067-07:00 imports: - name: cloud.google.com/go version: fe3d41e1ecb2ce36ad3a979037c9b9a2b726226f @@ -24,7 +24,7 @@ imports: - name: github.com/appscode/jsonpatch version: 5af499cf01c842bfdd7761a433fc90525ccd6836 - name: github.com/appscode/kutil - version: 303298aa86dad096fed4c49ba117700e506eca2c + version: 25382b15981e816818803a66b6e1a1270efa89ab subpackages: - apiextensions/v1beta1 - meta @@ -104,7 +104,7 @@ imports: subpackages: - log - name: github.com/evanphx/json-patch - version: 94e38aa1586e8a6c8a75770bddf5ff84c48a106b + version: 36442dbdb585210f8d5a1b45e67aa323c197d5c4 - name: github.com/exponent-io/jsonpath version: d6023ce2651d8eafb5c75bb0c7167536102ec9f5 - name: github.com/fatih/camelcase @@ -204,9 +204,9 @@ imports: - client/clientset/versioned/scheme - client/clientset/versioned/typed/kubedb/v1alpha1 - name: github.com/kubedb/elasticsearch - version: 649a5b6876059640b05d399a8bad5bab18252681 + version: de49d7de9667e925c4c5aad4f9dfa8289cb2785e - name: github.com/kubedb/etcd - version: d2774bdcada77c341ce718c60b812317582b5950 + version: 8354b4ff99cc0529facab54dc9f2e528a667da50 - name: github.com/kubedb/memcached version: f319545fe539b0e49b1ff240ed5142f171f88115 - name: github.com/kubedb/mongodb @@ -214,7 +214,7 @@ imports: - name: github.com/kubedb/mysql version: 7bcfbc48dcff2c378f06387ee3e1f0eb7f0e47ef - name: github.com/kubedb/postgres - version: 3d8881804af7d03a243948493557ebec7c7678ff + version: 65249080ec5d1241b406fe6393b75e36ca52a97b - name: github.com/kubedb/redis version: 1c2bcbd6d69cfe5d15be5e16a115cc81deab36f2 - name: github.com/mailru/easyjson @@ -263,7 +263,7 @@ imports: subpackages: - doc - name: github.com/spf13/pflag - version: 583c0c0531f06d5278b7d917446061adc344b5cd + version: 298182f68c66c05229eb03ac171abe6e309ee79a - name: github.com/yudai/gojsondiff version: 7b1b7adf999dab73a6eb02669c3d82dbb27a3dd6 subpackages: @@ -717,7 +717,7 @@ imports: - apis/appcatalog - apis/appcatalog/v1alpha1 - name: kmodules.xyz/monitoring-agent-api - version: cb29a44ae61b9096ce83750c2b070d57daa8d953 + version: 626ef00ec8baebe0d2b451cf8f06450c2588f237 repo: https://github.com/kmodules/monitoring-agent-api.git vcs: git subpackages: diff --git a/glide.yaml b/glide.yaml index 6d24a93bd..eb8995be7 100644 --- a/glide.yaml +++ b/glide.yaml @@ -25,7 +25,7 @@ import: - package: github.com/spf13/cobra version: v0.0.3 - package: github.com/spf13/pflag - version: v1.0.1 + version: v1.0.3 - package: github.com/yudai/gojsondiff version: 1.0.0 - package: k8s.io/api diff --git a/hack/deploy/kubedb.sh b/hack/deploy/kubedb.sh index aa40fb5c2..ded2f9310 100755 --- a/hack/deploy/kubedb.sh +++ b/hack/deploy/kubedb.sh @@ -129,7 +129,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.9.0-beta.1 +export KUBEDB_OPERATOR_TAG=0.9.0-rc.0 export KUBEDB_OPERATOR_NAME=operator export KUBEDB_IMAGE_PULL_SECRET= export KUBEDB_IMAGE_PULL_POLICY=IfNotPresent @@ -141,7 +141,7 @@ export KUBEDB_BYPASS_VALIDATING_WEBHOOK_XRAY=false export KUBEDB_USE_KUBEAPISERVER_FQDN_FOR_AKS=true export APPSCODE_ENV=${APPSCODE_ENV:-prod} -export SCRIPT_LOCATION="curl -fsSL https://raw.githubusercontent.com/kubedb/cli/0.9.0-beta.1/" +export SCRIPT_LOCATION="curl -fsSL https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.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 e7ca59dd4..5941fd777 100644 --- a/hack/gendocs/main.go +++ b/hack/gendocs/main.go @@ -16,7 +16,7 @@ import ( ) const ( - version = "0.9.0-beta.1" + version = "0.9.0-rc.0" ) var ( diff --git a/hack/release.py b/hack/release.py index ac939ee81..06258205a 100755 --- a/hack/release.py +++ b/hack/release.py @@ -41,16 +41,16 @@ def check_antipackage(): libbuild.REPO_ROOT = expandvars('$GOPATH') + '/src/github.com/kubedb/cli' DATABASES = ['postgres', 'elasticsearch', 'etcd', 'mysql', 'mongodb', 'memcached', 'redis'] RELEASE_TAGS = { - 'cli': '0.9.0-beta.1', - 'operator': '0.9.0-beta.1', - 'apimachinery': '0.9.0-beta.1', - 'postgres': '0.9.0-beta.1', - 'elasticsearch': '0.9.0-beta.1', - 'etcd': '0.1.0-beta.1', - 'mysql': '0.2.0-beta.1', - 'mongodb': '0.2.0-beta.1', - 'memcached': '0.2.0-beta.1', - 'redis': '0.2.0-beta.1', + 'cli': '0.9.0-rc.0', + 'operator': '0.9.0-rc.0', + 'apimachinery': '0.9.0-rc.0', + 'postgres': '0.9.0-rc.0', + 'elasticsearch': '0.9.0-rc.0', + 'etcd': '0.1.0-rc.0', + 'mysql': '0.2.0-rc.0', + 'mongodb': '0.2.0-rc.0', + 'memcached': '0.2.0-rc.0', + 'redis': '0.2.0-rc.0', } diff --git a/vendor/github.com/evanphx/json-patch/patch.go b/vendor/github.com/evanphx/json-patch/patch.go index 1a3aa387e..3d76e9e38 100644 --- a/vendor/github.com/evanphx/json-patch/patch.go +++ b/vendor/github.com/evanphx/json-patch/patch.go @@ -204,7 +204,7 @@ func (n *lazyNode) equal(o *lazyNode) bool { } func (o operation) kind() string { - if obj, ok := o["op"]; ok { + if obj, ok := o["op"]; ok && obj != nil { var op string err := json.Unmarshal(*obj, &op) @@ -220,7 +220,7 @@ func (o operation) kind() string { } func (o operation) path() string { - if obj, ok := o["path"]; ok { + if obj, ok := o["path"]; ok && obj != nil { var op string err := json.Unmarshal(*obj, &op) @@ -236,7 +236,7 @@ func (o operation) path() string { } func (o operation) from() string { - if obj, ok := o["from"]; ok { + if obj, ok := o["from"]; ok && obj != nil { var op string err := json.Unmarshal(*obj, &op) @@ -389,17 +389,13 @@ func (d *partialArray) add(key string, val *lazyNode) error { cur := *d - if idx < 0 { - idx *= -1 - - if idx > len(ary) { - return fmt.Errorf("Unable to access invalid index: %d", idx) - } - idx = len(ary) - idx - } - if idx < 0 || idx >= len(ary) || idx > len(cur) { + if idx < -len(ary) || idx >= len(ary) { return fmt.Errorf("Unable to access invalid index: %d", idx) } + + if idx < 0 { + idx += len(ary) + } copy(ary[0:idx], cur[0:idx]) ary[idx] = val copy(ary[idx+1:], cur[idx:]) @@ -430,9 +426,12 @@ func (d *partialArray) remove(key string) error { cur := *d - if idx >= len(cur) { + if idx < -len(cur) || idx >= len(cur) { return fmt.Errorf("Unable to remove invalid index: %d", idx) } + if idx < 0 { + idx += len(cur) + } ary := make([]*lazyNode, len(cur)-1) @@ -450,7 +449,7 @@ func (p Patch) add(doc *container, op operation) error { con, key := findObject(doc, path) if con == nil { - return fmt.Errorf("jsonpatch add operation does not apply: doc is missing path: %s", path) + return fmt.Errorf("jsonpatch add operation does not apply: doc is missing path: \"%s\"", path) } return con.add(key, op.value()) @@ -462,7 +461,7 @@ func (p Patch) remove(doc *container, op operation) error { con, key := findObject(doc, path) if con == nil { - return fmt.Errorf("jsonpatch remove operation does not apply: doc is missing path: %s", path) + return fmt.Errorf("jsonpatch remove operation does not apply: doc is missing path: \"%s\"", path) } return con.remove(key) @@ -477,8 +476,8 @@ func (p Patch) replace(doc *container, op operation) error { return fmt.Errorf("jsonpatch replace operation does not apply: doc is missing path: %s", path) } - val, ok := con.get(key) - if val == nil || ok != nil { + _, ok := con.get(key) + if ok != nil { return fmt.Errorf("jsonpatch replace operation does not apply: doc is missing key: %s", path) } @@ -535,6 +534,8 @@ func (p Patch) test(doc *container, op operation) error { return nil } return fmt.Errorf("Testing value %s failed", path) + } else if op.value() == nil { + return fmt.Errorf("Testing value %s failed", path) } if val.equal(op.value()) { diff --git a/vendor/github.com/spf13/pflag/bytes.go b/vendor/github.com/spf13/pflag/bytes.go index 12c58db9f..67d530457 100644 --- a/vendor/github.com/spf13/pflag/bytes.go +++ b/vendor/github.com/spf13/pflag/bytes.go @@ -1,6 +1,7 @@ package pflag import ( + "encoding/base64" "encoding/hex" "fmt" "strings" @@ -9,10 +10,12 @@ import ( // BytesHex adapts []byte for use as a flag. Value of flag is HEX encoded type bytesHexValue []byte +// String implements pflag.Value.String. func (bytesHex bytesHexValue) String() string { return fmt.Sprintf("%X", []byte(bytesHex)) } +// Set implements pflag.Value.Set. func (bytesHex *bytesHexValue) Set(value string) error { bin, err := hex.DecodeString(strings.TrimSpace(value)) @@ -25,6 +28,7 @@ func (bytesHex *bytesHexValue) Set(value string) error { return nil } +// Type implements pflag.Value.Type. func (*bytesHexValue) Type() string { return "bytesHex" } @@ -103,3 +107,103 @@ func BytesHex(name string, value []byte, usage string) *[]byte { func BytesHexP(name, shorthand string, value []byte, usage string) *[]byte { return CommandLine.BytesHexP(name, shorthand, value, usage) } + +// BytesBase64 adapts []byte for use as a flag. Value of flag is Base64 encoded +type bytesBase64Value []byte + +// String implements pflag.Value.String. +func (bytesBase64 bytesBase64Value) String() string { + return base64.StdEncoding.EncodeToString([]byte(bytesBase64)) +} + +// Set implements pflag.Value.Set. +func (bytesBase64 *bytesBase64Value) Set(value string) error { + bin, err := base64.StdEncoding.DecodeString(strings.TrimSpace(value)) + + if err != nil { + return err + } + + *bytesBase64 = bin + + return nil +} + +// Type implements pflag.Value.Type. +func (*bytesBase64Value) Type() string { + return "bytesBase64" +} + +func newBytesBase64Value(val []byte, p *[]byte) *bytesBase64Value { + *p = val + return (*bytesBase64Value)(p) +} + +func bytesBase64ValueConv(sval string) (interface{}, error) { + + bin, err := base64.StdEncoding.DecodeString(sval) + if err == nil { + return bin, nil + } + + return nil, fmt.Errorf("invalid string being converted to Bytes: %s %s", sval, err) +} + +// GetBytesBase64 return the []byte value of a flag with the given name +func (f *FlagSet) GetBytesBase64(name string) ([]byte, error) { + val, err := f.getFlagType(name, "bytesBase64", bytesBase64ValueConv) + + if err != nil { + return []byte{}, err + } + + return val.([]byte), nil +} + +// BytesBase64Var defines an []byte flag with specified name, default value, and usage string. +// The argument p points to an []byte variable in which to store the value of the flag. +func (f *FlagSet) BytesBase64Var(p *[]byte, name string, value []byte, usage string) { + f.VarP(newBytesBase64Value(value, p), name, "", usage) +} + +// BytesBase64VarP is like BytesBase64Var, but accepts a shorthand letter that can be used after a single dash. +func (f *FlagSet) BytesBase64VarP(p *[]byte, name, shorthand string, value []byte, usage string) { + f.VarP(newBytesBase64Value(value, p), name, shorthand, usage) +} + +// BytesBase64Var defines an []byte flag with specified name, default value, and usage string. +// The argument p points to an []byte variable in which to store the value of the flag. +func BytesBase64Var(p *[]byte, name string, value []byte, usage string) { + CommandLine.VarP(newBytesBase64Value(value, p), name, "", usage) +} + +// BytesBase64VarP is like BytesBase64Var, but accepts a shorthand letter that can be used after a single dash. +func BytesBase64VarP(p *[]byte, name, shorthand string, value []byte, usage string) { + CommandLine.VarP(newBytesBase64Value(value, p), name, shorthand, usage) +} + +// BytesBase64 defines an []byte flag with specified name, default value, and usage string. +// The return value is the address of an []byte variable that stores the value of the flag. +func (f *FlagSet) BytesBase64(name string, value []byte, usage string) *[]byte { + p := new([]byte) + f.BytesBase64VarP(p, name, "", value, usage) + return p +} + +// BytesBase64P is like BytesBase64, but accepts a shorthand letter that can be used after a single dash. +func (f *FlagSet) BytesBase64P(name, shorthand string, value []byte, usage string) *[]byte { + p := new([]byte) + f.BytesBase64VarP(p, name, shorthand, value, usage) + return p +} + +// BytesBase64 defines an []byte flag with specified name, default value, and usage string. +// The return value is the address of an []byte variable that stores the value of the flag. +func BytesBase64(name string, value []byte, usage string) *[]byte { + return CommandLine.BytesBase64P(name, "", value, usage) +} + +// BytesBase64P is like BytesBase64, but accepts a shorthand letter that can be used after a single dash. +func BytesBase64P(name, shorthand string, value []byte, usage string) *[]byte { + return CommandLine.BytesBase64P(name, shorthand, value, usage) +} diff --git a/vendor/github.com/spf13/pflag/flag.go b/vendor/github.com/spf13/pflag/flag.go index 5eadc84e3..9beeda8ec 100644 --- a/vendor/github.com/spf13/pflag/flag.go +++ b/vendor/github.com/spf13/pflag/flag.go @@ -925,13 +925,16 @@ func stripUnknownFlagValue(args []string) []string { } first := args[0] - if first[0] == '-' { + if len(first) > 0 && first[0] == '-' { //--unknown --next-flag ... return args } //--unknown arg ... (args will be arg ...) - return args[1:] + if len(args) > 1 { + return args[1:] + } + return nil } func (f *FlagSet) parseLongArg(s string, args []string, fn parseFunc) (a []string, err error) { @@ -990,11 +993,12 @@ func (f *FlagSet) parseLongArg(s string, args []string, fn parseFunc) (a []strin } func (f *FlagSet) parseSingleShortArg(shorthands string, args []string, fn parseFunc) (outShorts string, outArgs []string, err error) { + outArgs = args + if strings.HasPrefix(shorthands, "test.") { return } - outArgs = args outShorts = shorthands[1:] c := shorthands[0] diff --git a/vendor/github.com/spf13/pflag/string_to_int.go b/vendor/github.com/spf13/pflag/string_to_int.go new file mode 100644 index 000000000..5ceda3965 --- /dev/null +++ b/vendor/github.com/spf13/pflag/string_to_int.go @@ -0,0 +1,149 @@ +package pflag + +import ( + "bytes" + "fmt" + "strconv" + "strings" +) + +// -- stringToInt Value +type stringToIntValue struct { + value *map[string]int + changed bool +} + +func newStringToIntValue(val map[string]int, p *map[string]int) *stringToIntValue { + ssv := new(stringToIntValue) + ssv.value = p + *ssv.value = val + return ssv +} + +// Format: a=1,b=2 +func (s *stringToIntValue) Set(val string) error { + ss := strings.Split(val, ",") + out := make(map[string]int, len(ss)) + for _, pair := range ss { + kv := strings.SplitN(pair, "=", 2) + if len(kv) != 2 { + return fmt.Errorf("%s must be formatted as key=value", pair) + } + var err error + out[kv[0]], err = strconv.Atoi(kv[1]) + if err != nil { + return err + } + } + if !s.changed { + *s.value = out + } else { + for k, v := range out { + (*s.value)[k] = v + } + } + s.changed = true + return nil +} + +func (s *stringToIntValue) Type() string { + return "stringToInt" +} + +func (s *stringToIntValue) String() string { + var buf bytes.Buffer + i := 0 + for k, v := range *s.value { + if i > 0 { + buf.WriteRune(',') + } + buf.WriteString(k) + buf.WriteRune('=') + buf.WriteString(strconv.Itoa(v)) + i++ + } + return "[" + buf.String() + "]" +} + +func stringToIntConv(val string) (interface{}, error) { + val = strings.Trim(val, "[]") + // An empty string would cause an empty map + if len(val) == 0 { + return map[string]int{}, nil + } + ss := strings.Split(val, ",") + out := make(map[string]int, len(ss)) + for _, pair := range ss { + kv := strings.SplitN(pair, "=", 2) + if len(kv) != 2 { + return nil, fmt.Errorf("%s must be formatted as key=value", pair) + } + var err error + out[kv[0]], err = strconv.Atoi(kv[1]) + if err != nil { + return nil, err + } + } + return out, nil +} + +// GetStringToInt return the map[string]int value of a flag with the given name +func (f *FlagSet) GetStringToInt(name string) (map[string]int, error) { + val, err := f.getFlagType(name, "stringToInt", stringToIntConv) + if err != nil { + return map[string]int{}, err + } + return val.(map[string]int), nil +} + +// StringToIntVar defines a string flag with specified name, default value, and usage string. +// The argument p points to a map[string]int variable in which to store the values of the multiple flags. +// The value of each argument will not try to be separated by comma +func (f *FlagSet) StringToIntVar(p *map[string]int, name string, value map[string]int, usage string) { + f.VarP(newStringToIntValue(value, p), name, "", usage) +} + +// StringToIntVarP is like StringToIntVar, but accepts a shorthand letter that can be used after a single dash. +func (f *FlagSet) StringToIntVarP(p *map[string]int, name, shorthand string, value map[string]int, usage string) { + f.VarP(newStringToIntValue(value, p), name, shorthand, usage) +} + +// StringToIntVar defines a string flag with specified name, default value, and usage string. +// The argument p points to a map[string]int variable in which to store the value of the flag. +// The value of each argument will not try to be separated by comma +func StringToIntVar(p *map[string]int, name string, value map[string]int, usage string) { + CommandLine.VarP(newStringToIntValue(value, p), name, "", usage) +} + +// StringToIntVarP is like StringToIntVar, but accepts a shorthand letter that can be used after a single dash. +func StringToIntVarP(p *map[string]int, name, shorthand string, value map[string]int, usage string) { + CommandLine.VarP(newStringToIntValue(value, p), name, shorthand, usage) +} + +// StringToInt defines a string flag with specified name, default value, and usage string. +// The return value is the address of a map[string]int variable that stores the value of the flag. +// The value of each argument will not try to be separated by comma +func (f *FlagSet) StringToInt(name string, value map[string]int, usage string) *map[string]int { + p := map[string]int{} + f.StringToIntVarP(&p, name, "", value, usage) + return &p +} + +// StringToIntP is like StringToInt, but accepts a shorthand letter that can be used after a single dash. +func (f *FlagSet) StringToIntP(name, shorthand string, value map[string]int, usage string) *map[string]int { + p := map[string]int{} + f.StringToIntVarP(&p, name, shorthand, value, usage) + return &p +} + +// StringToInt defines a string flag with specified name, default value, and usage string. +// The return value is the address of a map[string]int variable that stores the value of the flag. +// The value of each argument will not try to be separated by comma +func StringToInt(name string, value map[string]int, usage string) *map[string]int { + return CommandLine.StringToIntP(name, "", value, usage) +} + +// StringToIntP is like StringToInt, but accepts a shorthand letter that can be used after a single dash. +func StringToIntP(name, shorthand string, value map[string]int, usage string) *map[string]int { + return CommandLine.StringToIntP(name, shorthand, value, usage) +} diff --git a/vendor/github.com/spf13/pflag/string_to_string.go b/vendor/github.com/spf13/pflag/string_to_string.go new file mode 100644 index 000000000..890a01afc --- /dev/null +++ b/vendor/github.com/spf13/pflag/string_to_string.go @@ -0,0 +1,160 @@ +package pflag + +import ( + "bytes" + "encoding/csv" + "fmt" + "strings" +) + +// -- stringToString Value +type stringToStringValue struct { + value *map[string]string + changed bool +} + +func newStringToStringValue(val map[string]string, p *map[string]string) *stringToStringValue { + ssv := new(stringToStringValue) + ssv.value = p + *ssv.value = val + return ssv +} + +// Format: a=1,b=2 +func (s *stringToStringValue) Set(val string) error { + var ss []string + n := strings.Count(val, "=") + switch n { + case 0: + return fmt.Errorf("%s must be formatted as key=value", val) + case 1: + ss = append(ss, strings.Trim(val, `"`)) + default: + r := csv.NewReader(strings.NewReader(val)) + var err error + ss, err = r.Read() + if err != nil { + return err + } + } + + out := make(map[string]string, len(ss)) + for _, pair := range ss { + kv := strings.SplitN(pair, "=", 2) + if len(kv) != 2 { + return fmt.Errorf("%s must be formatted as key=value", pair) + } + out[kv[0]] = kv[1] + } + if !s.changed { + *s.value = out + } else { + for k, v := range out { + (*s.value)[k] = v + } + } + s.changed = true + return nil +} + +func (s *stringToStringValue) Type() string { + return "stringToString" +} + +func (s *stringToStringValue) String() string { + records := make([]string, 0, len(*s.value)>>1) + for k, v := range *s.value { + records = append(records, k+"="+v) + } + + var buf bytes.Buffer + w := csv.NewWriter(&buf) + if err := w.Write(records); err != nil { + panic(err) + } + w.Flush() + return "[" + strings.TrimSpace(buf.String()) + "]" +} + +func stringToStringConv(val string) (interface{}, error) { + val = strings.Trim(val, "[]") + // An empty string would cause an empty map + if len(val) == 0 { + return map[string]string{}, nil + } + r := csv.NewReader(strings.NewReader(val)) + ss, err := r.Read() + if err != nil { + return nil, err + } + out := make(map[string]string, len(ss)) + for _, pair := range ss { + kv := strings.SplitN(pair, "=", 2) + if len(kv) != 2 { + return nil, fmt.Errorf("%s must be formatted as key=value", pair) + } + out[kv[0]] = kv[1] + } + return out, nil +} + +// GetStringToString return the map[string]string value of a flag with the given name +func (f *FlagSet) GetStringToString(name string) (map[string]string, error) { + val, err := f.getFlagType(name, "stringToString", stringToStringConv) + if err != nil { + return map[string]string{}, err + } + return val.(map[string]string), nil +} + +// StringToStringVar defines a string flag with specified name, default value, and usage string. +// The argument p points to a map[string]string variable in which to store the values of the multiple flags. +// The value of each argument will not try to be separated by comma +func (f *FlagSet) StringToStringVar(p *map[string]string, name string, value map[string]string, usage string) { + f.VarP(newStringToStringValue(value, p), name, "", usage) +} + +// StringToStringVarP is like StringToStringVar, but accepts a shorthand letter that can be used after a single dash. +func (f *FlagSet) StringToStringVarP(p *map[string]string, name, shorthand string, value map[string]string, usage string) { + f.VarP(newStringToStringValue(value, p), name, shorthand, usage) +} + +// StringToStringVar defines a string flag with specified name, default value, and usage string. +// The argument p points to a map[string]string variable in which to store the value of the flag. +// The value of each argument will not try to be separated by comma +func StringToStringVar(p *map[string]string, name string, value map[string]string, usage string) { + CommandLine.VarP(newStringToStringValue(value, p), name, "", usage) +} + +// StringToStringVarP is like StringToStringVar, but accepts a shorthand letter that can be used after a single dash. +func StringToStringVarP(p *map[string]string, name, shorthand string, value map[string]string, usage string) { + CommandLine.VarP(newStringToStringValue(value, p), name, shorthand, usage) +} + +// StringToString defines a string flag with specified name, default value, and usage string. +// The return value is the address of a map[string]string variable that stores the value of the flag. +// The value of each argument will not try to be separated by comma +func (f *FlagSet) StringToString(name string, value map[string]string, usage string) *map[string]string { + p := map[string]string{} + f.StringToStringVarP(&p, name, "", value, usage) + return &p +} + +// StringToStringP is like StringToString, but accepts a shorthand letter that can be used after a single dash. +func (f *FlagSet) StringToStringP(name, shorthand string, value map[string]string, usage string) *map[string]string { + p := map[string]string{} + f.StringToStringVarP(&p, name, shorthand, value, usage) + return &p +} + +// StringToString defines a string flag with specified name, default value, and usage string. +// The return value is the address of a map[string]string variable that stores the value of the flag. +// The value of each argument will not try to be separated by comma +func StringToString(name string, value map[string]string, usage string) *map[string]string { + return CommandLine.StringToStringP(name, "", value, usage) +} + +// StringToStringP is like StringToString, but accepts a shorthand letter that can be used after a single dash. +func StringToStringP(name, shorthand string, value map[string]string, usage string) *map[string]string { + return CommandLine.StringToStringP(name, shorthand, value, usage) +} diff --git a/vendor/kmodules.xyz/monitoring-agent-api/api/v1/openapi_generated.go b/vendor/kmodules.xyz/monitoring-agent-api/api/v1/openapi_generated.go index 3e67d7528..3b1ac6431 100644 --- a/vendor/kmodules.xyz/monitoring-agent-api/api/v1/openapi_generated.go +++ b/vendor/kmodules.xyz/monitoring-agent-api/api/v1/openapi_generated.go @@ -52,7 +52,7 @@ func schema_kmodulesxyz_monitoring_agent_api_api_v1_AgentSpec(ref common.Referen }, "resources": { SchemaProps: spec.SchemaProps{ - Description: "Compute Resources required by the sidecar container. Deprecated: Use podTemplate.spec.resources", + Description: "Compute Resources required by the exporter container.", Ref: ref("k8s.io/api/core/v1.ResourceRequirements"), }, }, diff --git a/vendor/kmodules.xyz/monitoring-agent-api/api/v1/types.go b/vendor/kmodules.xyz/monitoring-agent-api/api/v1/types.go index d6f1c4825..9c212ba3d 100644 --- a/vendor/kmodules.xyz/monitoring-agent-api/api/v1/types.go +++ b/vendor/kmodules.xyz/monitoring-agent-api/api/v1/types.go @@ -2,8 +2,9 @@ package v1 import ( "strings" - core "k8s.io/api/core/v1" + "github.com/appscode/kutil" + core "k8s.io/api/core/v1" ) type AgentType string @@ -29,9 +30,8 @@ func (at AgentType) Vendor() string { type AgentSpec struct { Agent AgentType `json:"agent,omitempty"` Prometheus *PrometheusSpec `json:"prometheus,omitempty"` - // Compute Resources required by the sidecar container. - // Deprecated: Use podTemplate.spec.resources - Resources *core.ResourceRequirements `json:"resources,omitempty"` + // Compute Resources required by the exporter container. + Resources core.ResourceRequirements `json:"resources,omitempty"` } type PrometheusSpec struct { diff --git a/vendor/kmodules.xyz/monitoring-agent-api/api/v1/zz_generated.deepcopy.go b/vendor/kmodules.xyz/monitoring-agent-api/api/v1/zz_generated.deepcopy.go index 4b4a17650..e8ce1ca95 100644 --- a/vendor/kmodules.xyz/monitoring-agent-api/api/v1/zz_generated.deepcopy.go +++ b/vendor/kmodules.xyz/monitoring-agent-api/api/v1/zz_generated.deepcopy.go @@ -20,10 +20,6 @@ limitations under the License. package v1 -import ( - corev1 "k8s.io/api/core/v1" -) - // DeepCopyInto is an autogenerated deepcopy function, copying the receiver, writing into out. in must be non-nil. func (in *AgentSpec) DeepCopyInto(out *AgentSpec) { *out = *in @@ -32,11 +28,7 @@ func (in *AgentSpec) DeepCopyInto(out *AgentSpec) { *out = new(PrometheusSpec) (*in).DeepCopyInto(*out) } - if in.Resources != nil { - in, out := &in.Resources, &out.Resources - *out = new(corev1.ResourceRequirements) - (*in).DeepCopyInto(*out) - } + in.Resources.DeepCopyInto(&out.Resources) return }