diff --git a/docs/CONTRIBUTING.md b/docs/CONTRIBUTING.md index 3f4023a7d0..a4d42f6c00 100644 --- a/docs/CONTRIBUTING.md +++ b/docs/CONTRIBUTING.md @@ -2,16 +2,16 @@ title: Contributing | KubeDB description: Contributing menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: contributing-cli name: Contributing parent: welcome weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: welcome -url: /docs/0.12.0/welcome/contributing/ +url: /docs/v0.13.0-rc.0/welcome/contributing/ aliases: - - /docs/0.12.0/CONTRIBUTING/ + - /docs/v0.13.0-rc.0/CONTRIBUTING/ --- # Contribution Guidelines diff --git a/docs/README.md b/docs/README.md index 7c8dd4519e..9f418240f0 100644 --- a/docs/README.md +++ b/docs/README.md @@ -2,17 +2,17 @@ title: Welcome | KubeDB description: Welcome to KubeDB menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: readme-cli name: Readme parent: welcome weight: -1 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: welcome -url: /docs/0.12.0/welcome/ +url: /docs/v0.13.0-rc.0/welcome/ aliases: - - /docs/0.12.0/ - - /docs/0.12.0/README/ + - /docs/v0.13.0-rc.0/ + - /docs/v0.13.0-rc.0/README/ --- # Welcome diff --git a/docs/_index.md b/docs/_index.md index d66bb87bb4..530d7d6f22 100644 --- a/docs/_index.md +++ b/docs/_index.md @@ -1,9 +1,9 @@ --- title: KubeDB menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: welcome name: Welcome weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/concepts/README.md b/docs/concepts/README.md index a8d6ccac5c..07fca43e97 100644 --- a/docs/concepts/README.md +++ b/docs/concepts/README.md @@ -1,16 +1,16 @@ --- title: Concepts | KubeDB menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: concepts-readme name: Readme parent: concepts weight: -1 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: concepts -url: /docs/0.12.0/concepts/ +url: /docs/v0.13.0-rc.0/concepts/ aliases: - - /docs/0.12.0/concepts/README/ + - /docs/v0.13.0-rc.0/concepts/README/ --- # Concepts diff --git a/docs/concepts/_index.md b/docs/concepts/_index.md index 9c5f9e4eab..c34134cbd3 100644 --- a/docs/concepts/_index.md +++ b/docs/concepts/_index.md @@ -2,9 +2,9 @@ title: Concepts description: Concepts menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: concepts name: Concepts weight: 20 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/concepts/catalog/_index.md b/docs/concepts/catalog/_index.md index 15860ed98d..52e16901f7 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.12.0: + docs_v0.13.0-rc.0: identifier: catalog parent: concepts name: Catalog weight: 20 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/concepts/catalog/elasticsearch.md b/docs/concepts/catalog/elasticsearch.md index a07b08875a..16dc7b5f4e 100644 --- a/docs/concepts/catalog/elasticsearch.md +++ b/docs/concepts/catalog/elasticsearch.md @@ -1,12 +1,12 @@ --- title: ElasticsearchVersion menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: elasticsearh-version name: ElasticsearchVersion parent: catalog weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: concepts --- diff --git a/docs/concepts/catalog/memcached.md b/docs/concepts/catalog/memcached.md index 4bcebc6fc0..06152b1653 100644 --- a/docs/concepts/catalog/memcached.md +++ b/docs/concepts/catalog/memcached.md @@ -1,12 +1,12 @@ --- title: MemcachedVersion menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: memcached-version name: MemcachedVersion parent: catalog weight: 30 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: concepts --- diff --git a/docs/concepts/catalog/mongodb.md b/docs/concepts/catalog/mongodb.md index 3f1227df1b..371859ebbd 100644 --- a/docs/concepts/catalog/mongodb.md +++ b/docs/concepts/catalog/mongodb.md @@ -1,12 +1,12 @@ --- title: MongoDBVersion menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: mongodb-version name: MongoDBVersion parent: catalog weight: 30 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: concepts --- diff --git a/docs/concepts/catalog/mysql.md b/docs/concepts/catalog/mysql.md index 610f0a0379..4d230892c9 100644 --- a/docs/concepts/catalog/mysql.md +++ b/docs/concepts/catalog/mysql.md @@ -1,12 +1,12 @@ --- title: MySQLVersion menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: mysql-version name: MySQLVersion parent: catalog weight: 30 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: concepts --- diff --git a/docs/concepts/catalog/postgres.md b/docs/concepts/catalog/postgres.md index 4f25ace5c1..5d86c0c50c 100644 --- a/docs/concepts/catalog/postgres.md +++ b/docs/concepts/catalog/postgres.md @@ -1,12 +1,12 @@ --- title: PostgresVersion menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: postgres-version name: PostgresVersion parent: catalog weight: 30 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: concepts --- diff --git a/docs/concepts/catalog/redis.md b/docs/concepts/catalog/redis.md index b273ff0c4b..8133bdfde5 100644 --- a/docs/concepts/catalog/redis.md +++ b/docs/concepts/catalog/redis.md @@ -1,12 +1,12 @@ --- title: RedisVersion menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: redis-version name: RedisVersion parent: catalog weight: 30 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: concepts --- diff --git a/docs/concepts/database-monitoring/_index.md b/docs/concepts/database-monitoring/_index.md index 8a1a91bc4d..1d7536ca77 100644 --- a/docs/concepts/database-monitoring/_index.md +++ b/docs/concepts/database-monitoring/_index.md @@ -2,10 +2,10 @@ title: Database Monitoring | KubeDB description: Database Monitoring menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: database-monitoring parent: concepts name: Database Monitoring weight: 30 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/concepts/database-monitoring/overview.md b/docs/concepts/database-monitoring/overview.md index 486a32dc17..c1cbc0fc52 100644 --- a/docs/concepts/database-monitoring/overview.md +++ b/docs/concepts/database-monitoring/overview.md @@ -2,12 +2,12 @@ title: Database Monitoring Overview description: Database Monitoring Overview menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: database-monitoring-overview name: Overview parent: database-monitoring weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: concepts --- diff --git a/docs/concepts/databases/_index.md b/docs/concepts/databases/_index.md index 090662761c..fc619328fa 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.12.0: + docs_v0.13.0-rc.0: identifier: databases parent: concepts name: Supported Databases weight: 15 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/concepts/databases/elasticsearch.md b/docs/concepts/databases/elasticsearch.md index e8fd746105..d50f2101bc 100644 --- a/docs/concepts/databases/elasticsearch.md +++ b/docs/concepts/databases/elasticsearch.md @@ -1,12 +1,12 @@ --- title: Elasticsearch menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: elasticsearch-db name: Elasticsearch parent: databases weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: concepts --- diff --git a/docs/concepts/databases/memcached.md b/docs/concepts/databases/memcached.md index 4e506de3b4..ad610d08bd 100644 --- a/docs/concepts/databases/memcached.md +++ b/docs/concepts/databases/memcached.md @@ -1,12 +1,12 @@ --- title: Memcached menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: memcached-db name: Memcached parent: databases weight: 15 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: concepts --- diff --git a/docs/concepts/databases/mongodb.md b/docs/concepts/databases/mongodb.md index d067ec63a1..ebed0bb28c 100644 --- a/docs/concepts/databases/mongodb.md +++ b/docs/concepts/databases/mongodb.md @@ -1,12 +1,12 @@ --- title: MongoDB menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: mongodb-db name: MongoDB parent: databases weight: 20 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: concepts --- diff --git a/docs/concepts/databases/mysql.md b/docs/concepts/databases/mysql.md index a6f24b0c22..648f1d1d2e 100644 --- a/docs/concepts/databases/mysql.md +++ b/docs/concepts/databases/mysql.md @@ -1,12 +1,12 @@ --- title: MySQL menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: mysql-db name: MySQL parent: databases weight: 25 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: concepts --- diff --git a/docs/concepts/databases/postgres.md b/docs/concepts/databases/postgres.md index 7c574ca15a..94026d555f 100644 --- a/docs/concepts/databases/postgres.md +++ b/docs/concepts/databases/postgres.md @@ -1,12 +1,12 @@ --- title: Postgres menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: postgres-db name: Postgres parent: databases weight: 30 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: concepts --- diff --git a/docs/concepts/databases/redis.md b/docs/concepts/databases/redis.md index d5d03c1e3e..f9d38b7b2f 100644 --- a/docs/concepts/databases/redis.md +++ b/docs/concepts/databases/redis.md @@ -1,12 +1,12 @@ --- title: Redis menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: redis-db name: Redis parent: databases weight: 35 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: concepts --- diff --git a/docs/concepts/snapshot.md b/docs/concepts/snapshot.md index 83a74ee674..00176e98c9 100644 --- a/docs/concepts/snapshot.md +++ b/docs/concepts/snapshot.md @@ -1,12 +1,12 @@ --- title: Snapshot menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: snapshot-concepts name: Snapshot parent: concepts weight: 35 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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 b24da30637..590e593ecc 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.12.0: + docs_v0.13.0-rc.0: identifier: what-is-kubedb parent: concepts name: What is KubeDB weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/concepts/what-is-kubedb/overview.md b/docs/concepts/what-is-kubedb/overview.md index 8fe22d1366..5f66c44f95 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.12.0: + docs_v0.13.0-rc.0: identifier: overview-concepts name: Overview parent: what-is-kubedb weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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 bb8390d200..d4f3d677dd 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.12.0" + image: "kubedb/operator:v0.13.0-rc.0" tools: image: "kubedb/postgres-tools:10.2-v2" diff --git a/docs/guides/README.md b/docs/guides/README.md index 2969828d47..d5729b5e4b 100644 --- a/docs/guides/README.md +++ b/docs/guides/README.md @@ -1,16 +1,16 @@ --- title: Guides | KubeDB menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: guides-readme name: Readme parent: guides weight: -1 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides -url: /docs/0.12.0/guides/ +url: /docs/v0.13.0-rc.0/guides/ aliases: - - /docs/0.12.0/guides/README/ + - /docs/v0.13.0-rc.0/guides/README/ --- # Guides diff --git a/docs/guides/_index.md b/docs/guides/_index.md index db906fdb97..67a723e6cc 100644 --- a/docs/guides/_index.md +++ b/docs/guides/_index.md @@ -1,10 +1,10 @@ --- title: Guides | KubeDB menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: guides name: Guides weight: 40 pre: dropdown -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/elasticsearch/README.md b/docs/guides/elasticsearch/README.md index 3da6fa6e97..8e35646025 100644 --- a/docs/guides/elasticsearch/README.md +++ b/docs/guides/elasticsearch/README.md @@ -1,16 +1,16 @@ --- title: Elasticsearch menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: es-readme-elasticsearch name: Elasticsearch parent: es-elasticsearch-guides weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides -url: /docs/0.12.0/guides/elasticsearch/ +url: /docs/v0.13.0-rc.0/guides/elasticsearch/ aliases: - - /docs/0.12.0/guides/elasticsearch/README/ + - /docs/v0.13.0-rc.0/guides/elasticsearch/README/ --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -33,16 +33,12 @@ aliases: | Custom Configuration | ✓ | | Using Custom Docker Image | ✓ | -
- ## Life Cycle of an Elasticsearch Object

lifecycle

-
- ## Supported Elasticsearch Version | KubeDB Version | Elasticsearch:2.3 | Elasticsearch:5.6 | Elasticsearch:6.2 | Elasticsearch:6.3 | Elasticsearch:6.4 | @@ -53,27 +49,28 @@ aliases: | 0.10.0 | ✗ | ✓ | ✓ | ✓ | ✓ | | 0.11.0 | ✗ | ✓ | ✓ | ✓ | ✓ | | 0.12.0 | ✗ | ✓ | ✓ | ✓ | ✓ | +| v0.13.0-rc.0 | ✗ | ✓ | ✓ | ✓ | ✓ | ## Supported ElasticsearchVersion CRD Here, ✓ means supported and ✗ means deprecated. -| NAME | VERSION | KubeDB: 0.9.0 | KubeDB: 0.10.0 | KubeDB: 0.11.0 | KubeDB: 0.12.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 | ✓ | ✓ | ✓ | ✓ | +| NAME | VERSION | KubeDB: 0.9.0 | KubeDB: 0.10.0 | KubeDB: 0.11.0 | KubeDB: 0.12.0 | KubeDB: v0.13.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 @@ -84,8 +81,6 @@ Here, ✓ means supported and ✗ means deprecated. | [osm](https://github.com/appscode/osm) | `0.9.1` | | [yq](https://github.com/mikefarah/yq) | `2.1.1` | -
- ## User Guide - [Quickstart Elasticsearch](/docs/guides/elasticsearch/quickstart/quickstart.md) with KubeDB Operator. diff --git a/docs/guides/elasticsearch/_index.md b/docs/guides/elasticsearch/_index.md index 49053fcaf9..6be1940276 100644 --- a/docs/guides/elasticsearch/_index.md +++ b/docs/guides/elasticsearch/_index.md @@ -1,10 +1,10 @@ --- title: Elasticsearch menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: es-elasticsearch-guides name: Elasticsearch parent: guides weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/elasticsearch/cli/_index.md b/docs/guides/elasticsearch/cli/_index.md index 6f84e2d3ad..bfb71f14b5 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.12.0: + docs_v0.13.0-rc.0: identifier: es-cli-elasticsearch name: CLI parent: es-elasticsearch-guides weight: 65 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/elasticsearch/cli/cli.md b/docs/guides/elasticsearch/cli/cli.md index c0a0bb5e9c..cff4512c8b 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.12.0: + docs_v0.13.0-rc.0: identifier: es-cli-cli name: Quickstart parent: es-cli-elasticsearch weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- diff --git a/docs/guides/elasticsearch/clustering/_index.md b/docs/guides/elasticsearch/clustering/_index.md index 516da9039a..4ae2dd4d98 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.12.0: + docs_v0.13.0-rc.0: identifier: es-clustering-elasticsearch name: Clustering parent: es-elasticsearch-guides weight: 20 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/elasticsearch/clustering/topology.md b/docs/guides/elasticsearch/clustering/topology.md index 4b3e4909d5..7a23597678 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.12.0: + docs_v0.13.0-rc.0: identifier: es-topology-clustering name: Topology parent: es-clustering-elasticsearch weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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/docs/tree/0.12.0/docs/examples/elasticsearch) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/elasticsearch) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Create multi-node Elasticsearch @@ -68,7 +68,7 @@ Here, Create example above with following command ```console -$ kubectl create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/elasticsearch/clustering/multi-node-es.yaml +$ kubectl create -f https://github.com/kubedb/docs/raw/v0.13.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://github.com/kubedb/docs/raw/0.12.0/docs/examples/elasticsearch/clustering/topology-es.yaml +$ kubectl create -f https://github.com/kubedb/docs/raw/v0.13.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 6c6149cc8e..e515feaeef 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.12.0: + docs_v0.13.0-rc.0: identifier: es-custom-config name: Custom Configuration parent: es-elasticsearch-guides weight: 40 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/elasticsearch/custom-config/overview.md b/docs/guides/elasticsearch/custom-config/overview.md index 5fe1db97bc..60bbf21873 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.12.0: + docs_v0.13.0-rc.0: identifier: es-custom-config-overview name: Overview parent: es-custom-config weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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 7218552268..f71a08c0a9 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.12.0: + docs_v0.13.0-rc.0: identifier: es-custom-config-with-topology name: With Topology parent: es-custom-config weight: 20 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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/docs/tree/0.12.0/docs/examples/elasticsearch) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/elasticsearch) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Use Custom Configuration @@ -120,7 +120,7 @@ metadata: Now, create an Elasticsearch crd with topology specified, ```console -$ kubectl apply -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/elasticsearch/custom-config/es-custom-with-topology.yaml +$ kubectl apply -f https://github.com/kubedb/docs/raw/v0.13.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 b727e24aa3..2dbd0ad061 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.12.0: + docs_v0.13.0-rc.0: identifier: es-custom-config-without-topology name: Without Topology parent: es-custom-config weight: 30 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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/docs/tree/0.12.0/docs/examples/elasticsearch) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/elasticsearch) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Use Custom Configuration @@ -111,7 +111,7 @@ metadata: Now, create an Elasticsearch crd without topology, ```console -$ kubectl apply -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/elasticsearch/custom-config/es-custom.yaml +$ kubectl apply -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/elasticsearch/custom-config/es-custom.yaml elasticsearch.kubedb.com/custom-elasticsearch created ``` diff --git a/docs/guides/elasticsearch/custom-rbac/_index.md b/docs/guides/elasticsearch/custom-rbac/_index.md index f5210a0f16..293fa17cf7 100755 --- a/docs/guides/elasticsearch/custom-rbac/_index.md +++ b/docs/guides/elasticsearch/custom-rbac/_index.md @@ -1,10 +1,10 @@ --- title: Run Elasticsearch with Custom RBAC resources menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: es-custom-rbac name: Custom RBAC parent: es-elasticsearch-guides weight: 85 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/elasticsearch/custom-rbac/using-custom-rbac.md b/docs/guides/elasticsearch/custom-rbac/using-custom-rbac.md index beffab8d36..86765c5cbf 100644 --- a/docs/guides/elasticsearch/custom-rbac/using-custom-rbac.md +++ b/docs/guides/elasticsearch/custom-rbac/using-custom-rbac.md @@ -1,12 +1,12 @@ --- title: Run Elasticsearch with Custom RBAC resources menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: es-custom-rbac-quickstart name: Custom RBAC parent: es-custom-rbac weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- @@ -29,7 +29,7 @@ $ kubectl create ns demo namespace/demo created ``` -> Note: YAML files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/docs/tree/0.12.0/docs/examples/elasticsearch) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/elasticsearch) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Overview @@ -71,7 +71,7 @@ secrets: Now, we need to create a role that has necessary access permissions for the Elasticsearch instance named `quick-elasticsearch`. ```console -$ kubectl apply -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/elasticsearch/custom-rbac/es-custom-role.yaml +$ kubectl apply -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/elasticsearch/custom-rbac/es-custom-role.yaml role.rbac.authorization.k8s.io/my-custom-role created ``` @@ -131,7 +131,7 @@ subjects: Now, create a Elasticsearch crd specifying `spec.podTemplate.spec.serviceAccountName` field to `my-custom-serviceaccount`. ```console -$ kubectl apply -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/elasticsearch/custom-rbac/es-custom-db.yaml +$ kubectl apply -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/elasticsearch/custom-rbac/es-custom-db.yaml elasticsearch.kubedb.com/quick-elasticsearch created ``` @@ -214,7 +214,7 @@ An existing service account can be reused in another Elasticsearch Database. No Now, create Elasticsearch crd `minute-elasticsearch` using the existing service account name `my-custom-serviceaccount` in the `spec.podTemplate.spec.serviceAccountName` field. ```console -$ kubectl apply -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/elasticsearch/custom-rbac/es-custom-db-two.yaml +$ kubectl apply -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/elasticsearch/custom-rbac/es-custom-db-two.yaml elasticsearch.kubedb.com/quick-elasticsearch created ``` diff --git a/docs/guides/elasticsearch/initialization/_index.md b/docs/guides/elasticsearch/initialization/_index.md index 5cea147e1d..3657c457fe 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.12.0: + docs_v0.13.0-rc.0: identifier: es-initialization-elasticsearch name: Initialization parent: es-elasticsearch-guides weight: 30 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/elasticsearch/initialization/snapshot_source.md b/docs/guides/elasticsearch/initialization/snapshot_source.md index 14a09e3b6e..84727f3591 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.12.0: + docs_v0.13.0-rc.0: identifier: es-snapshot-source-initialization name: Using Snapshot parent: es-initialization-elasticsearch weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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/docs/tree/0.12.0/docs/examples/elasticsearch) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/elasticsearch) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Prepare Snapshot @@ -92,7 +92,7 @@ instant-snapshot instant-elasticsearch Succeeded 51m Now, create the Elasticsearch object. ```console -$ kubectl create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/elasticsearch/initialization/recovered-es.yaml +$ kubectl create -f https://github.com/kubedb/docs/raw/v0.13.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 3aaf2a22e8..37211ff49a 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.12.0: + docs_v0.13.0-rc.0: identifier: es-kibana name: Kibana parent: es-elasticsearch-guides weight: 55 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/elasticsearch/kibana/connect-kibana.md b/docs/guides/elasticsearch/kibana/connect-kibana.md index 172c73aca4..b0d962c95b 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.12.0: + docs_v0.13.0-rc.0: identifier: es-kibana-connect name: Use Kibana parent: es-kibana weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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/docs/tree/0.12.0/docs/examples/elasticsearch) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/elasticsearch) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Overview @@ -257,7 +257,7 @@ metadata: Now, create Elasticsearch crd specifying `spec.databaseSecret` and `spec.configSource` field. ```console -$ kubectl apply -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/elasticsearch/kibana/es-kibana-demo.yaml +$ kubectl apply -f https://github.com/kubedb/docs/raw/v0.13.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://github.com/kubedb/docs/raw/0.12.0/docs/examples/elasticsearch/kibana/kibana-deployment.yaml +$ kubectl apply -f https://github.com/kubedb/docs/raw/v0.13.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 af4d6731f8..639f025504 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.12.0: + docs_v0.13.0-rc.0: identifier: es-monitoring-elasticsearch name: Monitoring parent: es-elasticsearch-guides weight: 45 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/elasticsearch/monitoring/using-builtin-prometheus.md b/docs/guides/elasticsearch/monitoring/using-builtin-prometheus.md index 3c6bc68570..a576254409 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.12.0: + docs_v0.13.0-rc.0: identifier: es-using-builtin-prometheus-monitoring name: Builtin Prometheus Discovery parent: es-monitoring-elasticsearch weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -35,7 +35,7 @@ This tutorial will show you how to monitor Elasticsearch database using builtin namespace/demo created ``` -> Note: YAML files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/docs/tree/0.12.0/docs/examples/elasticsearch) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/elasticsearch) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Deploy Elasticsearch with Monitoring Enabled @@ -68,7 +68,7 @@ Here, Let's create the Elasticsearch crd we have shown above. ```console -$ kubectl apply -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/elasticsearch/monitoring/builtin-prom-es.yaml +$ kubectl apply -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/elasticsearch/monitoring/builtin-prom-es.yaml elasticsearch.kubedb.com/builtin-prom-es created ``` @@ -274,7 +274,7 @@ data: Let's create above `ConfigMap`, ```console -$ kubectl apply -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/monitoring/builtin-prometheus/prom-config.yaml +$ kubectl apply -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/monitoring/builtin-prometheus/prom-config.yaml configmap/prometheus-config created ``` diff --git a/docs/guides/elasticsearch/monitoring/using-coreos-prometheus-operator.md b/docs/guides/elasticsearch/monitoring/using-coreos-prometheus-operator.md index ea86fbc4fd..ace8a54234 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.12.0: + docs_v0.13.0-rc.0: identifier: es-using-coreos-prometheus-operator-monitoring name: Coreos Prometheus Operator parent: es-monitoring-elasticsearch weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -35,7 +35,7 @@ CoreOS [prometheus-operator](https://github.com/coreos/prometheus-operator) prov - If you already don't have a Prometheus server running, deploy one following tutorial from [here](https://github.com/appscode/third-party-tools/blob/master/monitoring/prometheus/coreos-operator/README.md#deploy-prometheus-server). -> Note: YAML files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/docs/tree/0.12.0/docs/examples/elasticsearch) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/elasticsearch) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Find out required labels for ServiceMonitor @@ -124,7 +124,7 @@ Here, Let's create the Elasticsearch object that we have shown above, ```console -$ kubectl create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/elasticsearch/monitoring/coreos-prom-es.yaml +$ kubectl create -f https://github.com/kubedb/docs/raw/v0.13.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 4da259f485..b14fe313c0 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.12.0: + docs_v0.13.0-rc.0: identifier: es-private-registry-elasticsearch name: Private Registry parent: es-elasticsearch-guides weight: 35 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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 4f04a86427..9ace0c4f05 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.12.0: + docs_v0.13.0-rc.0: identifier: es-using-private-registry-private-registry name: Quickstart parent: es-private-registry-elasticsearch weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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/docs/tree/0.12.0/docs/examples/elasticsearch) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/elasticsearch) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## 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.12.0 ; docker tag kubedb/operator:0.12.0 $DOCKER_REGISTRY/operator:0.12.0 ; docker push $DOCKER_REGISTRY/operator:0.12.0 +$ docker pull kubedb/operator:v0.13.0-rc.0 ; docker tag kubedb/operator:v0.13.0-rc.0 $DOCKER_REGISTRY/operator:v0.13.0-rc.0 ; docker push $DOCKER_REGISTRY/operator:v0.13.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://github.com/kubedb/docs/raw/0.12.0/docs/examples/elasticsearch/private-registry/private-registry.yaml +$ kubectl create -f https://github.com/kubedb/docs/raw/v0.13.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 07250c4d38..fe22611de7 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.12.0: + docs_v0.13.0-rc.0: identifier: es-quickstart-elasticsearch name: Quickstart parent: es-elasticsearch-guides weight: 15 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/elasticsearch/quickstart/quickstart.md b/docs/guides/elasticsearch/quickstart/quickstart.md index f1234d9dfd..efcff99aeb 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.12.0: + docs_v0.13.0-rc.0: identifier: es-quickstart-quickstart name: Overview parent: es-quickstart-elasticsearch weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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/docs/tree/0.12.0/docs/examples/elasticsearch) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/elasticsearch) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). >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). @@ -115,7 +115,7 @@ Here, Let's create Elasticsearch crd that is shown above with following command ```console -$ kubectl create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/elasticsearch/quickstart/quick-elasticsearch.yaml +$ kubectl create -f https://github.com/kubedb/docs/raw/v0.13.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://github.com/kubedb/docs/raw/0.12.0/docs/examples/elasticsearch/quickstart/quick-elasticsearch.yaml +$ kubectl create -f https://github.com/kubedb/docs/raw/v0.13.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 1e9f554ad5..403bcd4b81 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.12.0: + docs_v0.13.0-rc.0: identifier: es-search-guard-elasticsearch name: Search Guard parent: es-elasticsearch-guides weight: 50 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/elasticsearch/search-guard/configuration.md b/docs/guides/elasticsearch/search-guard/configuration.md index e2389713d8..773a535b19 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.12.0: + docs_v0.13.0-rc.0: identifier: es-configuration-search-guard name: Configuration parent: es-search-guard-elasticsearch weight: 15 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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/docs/tree/0.12.0/docs/examples/elasticsearch) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/elasticsearch) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Create Configuration @@ -99,7 +99,7 @@ searchguard: ``` ```console -$ wget https://github.com/kubedb/docs/raw/0.12.0/docs/examples/elasticsearch/search-guard/sg-config/sg_config.yml +$ wget https://github.com/kubedb/docs/raw/v0.13.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://github.com/kubedb/docs/raw/0.12.0/docs/examples/elasticsearch/search-guard/sg-config/sg_internal_users.yml | envsubst > sg_internal_users.yml +$ curl https://github.com/kubedb/docs/raw/v0.13.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://github.com/kubedb/docs/raw/0.12.0/docs/examples/elasticsearch/search-guard/sg-config/sg_action_groups.yml +$ wget https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/elasticsearch/search-guard/sg-config/sg_action_groups.yml ``` ```yml @@ -254,7 +254,7 @@ sg_readall: ``` ```console -$ wget https://github.com/kubedb/docs/raw/0.12.0/docs/examples/elasticsearch/search-guard/sg-config/sg_roles.yml +$ wget https://github.com/kubedb/docs/raw/v0.13.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://github.com/kubedb/docs/raw/0.12.0/docs/examples/elasticsearch/search-guard/sg-config/sg_roles_mapping.yml +$ wget https://github.com/kubedb/docs/raw/v0.13.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://github.com/kubedb/docs/raw/0.12.0/docs/examples/elasticsearch/search-guard/config-elasticsearch.yaml +$ kubectl create -f https://github.com/kubedb/docs/raw/v0.13.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 edff0b24fc..197d335c6c 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.12.0: + docs_v0.13.0-rc.0: identifier: es-disable-search-guard name: Disable Search Guard parent: es-search-guard-elasticsearch weight: 30 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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/docs/tree/0.12.0/docs/examples/elasticsearch) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/elasticsearch) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Create Elasticsearch @@ -62,7 +62,7 @@ spec: Let's create the Elasticsearch object we have shown above, ```console -$ kubectl create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/elasticsearch/search-guard/es-sg-disabled.yaml +$ kubectl create -f https://github.com/kubedb/docs/raw/v0.13.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 829a9b85a1..2f587b920f 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.12.0: + docs_v0.13.0-rc.0: identifier: es-issue-certificate-search-guard name: Issue Certificate parent: es-search-guard-elasticsearch weight: 25 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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/docs/tree/0.12.0/docs/examples/elasticsearch) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/elasticsearch) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Generate truststore @@ -81,7 +81,7 @@ You need to follow these steps 1. Get root certificate configuration file ```console - $ wget https://github.com/kubedb/docs/raw/0.12.0/docs/examples/elasticsearch/search-guard/openssl-config/openssl-ca.ini + $ wget https://github.com/kubedb/docs/raw/v0.13.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://github.com/kubedb/docs/raw/0.12.0/docs/examples/elasticsearch/search-guard/openssl-config/openssl-sign.ini +$ wget https://github.com/kubedb/docs/raw/v0.13.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://github.com/kubedb/docs/raw/0.12.0/docs/examples/elasticsearch/search-guard/openssl-config/openssl-node.ini +$ wget https://github.com/kubedb/docs/raw/v0.13.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://github.com/kubedb/docs/raw/0.12.0/docs/examples/elasticsearch/search-guard/openssl-config/openssl-client.ini +$ wget https://github.com/kubedb/docs/raw/v0.13.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://github.com/kubedb/docs/raw/0.12.0/docs/examples/elasticsearch/search-guard/openssl-config/openssl-sgadmin.ini +$ wget https://github.com/kubedb/docs/raw/v0.13.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://github.com/kubedb/docs/raw/0.12.0/docs/examples/elasticsearch/search-guard/sg-elasticsearch.yaml +$ kubectl create -f https://github.com/kubedb/docs/raw/v0.13.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 3a0f2e8c78..72d6dda85e 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.12.0: + docs_v0.13.0-rc.0: identifier: es-search-guard-search-guard name: Overview parent: es-search-guard-elasticsearch weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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 e934908ed3..39703f0a68 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.12.0: + docs_v0.13.0-rc.0: identifier: es-use-tls-search-guard name: Use TLS parent: es-search-guard-elasticsearch weight: 20 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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/docs/tree/0.12.0/docs/examples/elasticsearch) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/elasticsearch) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Create Elasticsearch @@ -63,7 +63,7 @@ spec: Let's create the Elasticsearch object we have shown above, ```console -$ kubectl create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/elasticsearch/search-guard/ssl-elasticsearch.yaml +$ kubectl create -f https://github.com/kubedb/docs/raw/v0.13.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 202871bcdb..042fddd9f9 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.12.0: + docs_v0.13.0-rc.0: identifier: es-snapshot-elasticsearch name: Snapshotting parent: es-elasticsearch-guides weight: 25 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/elasticsearch/snapshot/instant_backup.md b/docs/guides/elasticsearch/snapshot/instant_backup.md index 4ada18bb6e..4d67ee5b94 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.12.0: + docs_v0.13.0-rc.0: identifier: es-instant-backup-snapshot name: Instant Backup parent: es-snapshot-elasticsearch weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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/docs/tree/0.12.0/docs/examples/elasticsearch) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/elasticsearch) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## 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://github.com/kubedb/docs/raw/0.12.0/docs/examples/elasticsearch/quickstart/instant-elasticsearch.yaml +$ kubectl create -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/elasticsearch/quickstart/instant-elasticsearch.yaml elasticsearch "instant-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://github.com/kubedb/docs/raw/0.12.0/docs/examples/elasticsearch/snapshot/instant-snapshot.yaml +$ kubectl create -f https://github.com/kubedb/docs/raw/v0.13.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 e1723e8e29..2ed58cf996 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.12.0: + docs_v0.13.0-rc.0: identifier: es-scheduled-backup-snapshot name: Scheduled Backup parent: es-snapshot-elasticsearch weight: 15 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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/docs/tree/0.12.0/docs/examples/elasticsearch) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/elasticsearch) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## 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://github.com/kubedb/docs/raw/0.12.0/docs/examples/elasticsearch/snapshot/scheduled-es.yaml +$ kubectl create -f https://github.com/kubedb/docs/raw/v0.13.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 37d33c58b7..b1d234a98b 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.12.0: + docs_v0.13.0-rc.0: identifier: es-x-pack name: X-Pack parent: es-elasticsearch-guides weight: 60 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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 7f498dd7f7..34aab80dfa 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.12.0: + docs_v0.13.0-rc.0: identifier: es-x-pack-monitoring name: Monitoring parent: es-x-pack weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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/docs/tree/0.12.0/docs/examples/elasticsearch) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/elasticsearch) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## 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://github.com/kubedb/docs/raw/0.12.0/docs/examples/elasticsearch/x-pack/es-mon-demo.yaml +$ kubectl apply -f kubectl apply -f https://github.com/kubedb/docs/raw/v0.13.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://github.com/kubedb/docs/raw/0.12.0/docs/examples/elasticsearch/kibana/kibana-deployment.yaml +$ kubectl apply -f https://github.com/kubedb/docs/raw/v0.13.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 406a36459e..a10e881689 100644 --- a/docs/guides/memcached/README.md +++ b/docs/guides/memcached/README.md @@ -1,16 +1,16 @@ --- title: Memcached menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: mc-readme-memcached name: Memcached parent: mc-memcached-guides weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides -url: /docs/0.12.0/guides/memcached/ +url: /docs/v0.13.0-rc.0/guides/memcached/ aliases: - - /docs/0.12.0/guides/memcached/README/ + - /docs/v0.13.0-rc.0/guides/memcached/README/ --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -30,16 +30,12 @@ aliases: | Builtin Prometheus Discovery | ✓ | | Using CoreOS Prometheus Operator | ✓ | -
- ## Life Cycle of a Memcached Object

  lifecycle

-
- ## Supported Memcached Versions | KubeDB Version | Memcached:1.5.4 | @@ -49,18 +45,19 @@ aliases: | 0.9.0 | ✓ | | 0.10.0 | ✓ | | 0.11.0 | ✓ | -| 0.12.0 | ✓ | +| v0.12.0 | ✓ | +| v0.13.0-rc.0 | ✓ | ## Supported MemcachedVersion CRD Here, ✓ means supported and ✗ means deprecated. -| NAME | VERSION | KubeDB: 0.9.0 | KubeDB: 0.10.0 | KubeDB: 0.11.0 | KubeDB: 0.12.0 | -| :------: | :-----: | :-----------: | :------------: | :------------: | :------------: | -| 1.5 | 1.5 | ✗ | ✗ | ✗ | ✗ | -| 1.5-v1 | 1.5 | ✓ | ✓ | ✓ | ✓ | -| 1.5.4 | 1.5.4 | ✗ | ✗ | ✗ | ✗ | -| 1.5.4-v1 | 1.5.4 | ✓ | ✓ | ✓ | ✓ | +| NAME | VERSION | KubeDB: 0.9.0 | KubeDB: 0.10.0 | KubeDB: 0.11.0 | KubeDB: 0.12.0 | KubeDB: v0.13.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 5bfa1a5ed4..e6fd8559ea 100644 --- a/docs/guides/memcached/_index.md +++ b/docs/guides/memcached/_index.md @@ -1,10 +1,10 @@ --- title: Memcached menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: mc-memcached-guides name: Memcached parent: guides weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/memcached/cli/_index.md b/docs/guides/memcached/cli/_index.md index b5003ed848..8dbc6d9640 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.12.0: + docs_v0.13.0-rc.0: identifier: mc-cli-memcached name: Cli parent: mc-memcached-guides weight: 45 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/memcached/cli/cli.md b/docs/guides/memcached/cli/cli.md index 668708f918..66b0e61fd3 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.12.0: + docs_v0.13.0-rc.0: identifier: mc-cli-cli name: Quickstart parent: mc-cli-memcached weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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 8765ab22d3..dc0c1a9d22 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.12.0: + docs_v0.13.0-rc.0: identifier: mc-custom-config name: Custom Configuration parent: mc-memcached-guides weight: 50 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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 46283f5290..6e567cf4bb 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.12.0: + docs_v0.13.0-rc.0: identifier: mc-custom-config-quickstart name: Quickstart parent: mc-custom-config weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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/docs/tree/0.12.0/docs/examples/memcached) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/memcached](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/memcached) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Overview @@ -119,7 +119,7 @@ metadata: Now, create Memcached crd specifying `spec.configSource` field. ```console -$ kubectl apply -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/memcached/custom-config/mc-custom.yaml +$ kubectl apply -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/memcached/custom-config/mc-custom.yaml memcached.kubedb.com/custom-memcached created ``` diff --git a/docs/guides/memcached/custom-rbac/_index.md b/docs/guides/memcached/custom-rbac/_index.md index 1ca4fc70a1..36034d6658 100755 --- a/docs/guides/memcached/custom-rbac/_index.md +++ b/docs/guides/memcached/custom-rbac/_index.md @@ -1,10 +1,10 @@ --- title: Run Memcached with Custom RBAC resources menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: mc-custom-rbac name: Custom RBAC parent: mc-memcached-guides weight: 85 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/memcached/custom-rbac/using-custom-rbac.md b/docs/guides/memcached/custom-rbac/using-custom-rbac.md index 520d083f2e..5a2b900ed5 100644 --- a/docs/guides/memcached/custom-rbac/using-custom-rbac.md +++ b/docs/guides/memcached/custom-rbac/using-custom-rbac.md @@ -1,12 +1,12 @@ --- title: Run Memcached with Custom RBAC resources menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: mc-custom-rbac-quickstart name: Custom RBAC parent: mc-custom-rbac weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- @@ -29,7 +29,7 @@ $ kubectl create ns demo namespace/demo created ``` -> Note: YAML files used in this tutorial are stored in [docs/examples/memcached](https://github.com/kubedb/docs/tree/0.12.0/docs/examples/memcached) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/memcached](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/memcached) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Overview @@ -70,7 +70,7 @@ secrets: Now, we need to create a role that has necessary access permissions for the Memcached instance named `quick-memcached`. ```console -$ kubectl apply -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/memcached/custom-rbac/mc-custom-role.yaml +$ kubectl apply -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/memcached/custom-rbac/mc-custom-role.yaml role.rbac.authorization.k8s.io/my-custom-role created ``` @@ -130,7 +130,7 @@ subjects: Now, create a Memcached crd specifying `spec.podTemplate.spec.serviceAccountName` field to `my-custom-serviceaccount`. ```console -$ kubectl apply -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/memcached/custom-rbac/mc-custom-db.yaml +$ kubectl apply -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/memcached/custom-rbac/mc-custom-db.yaml memcached.kubedb.com/quick-memcached created ``` @@ -182,7 +182,7 @@ An existing service account can be reused in another Memcached instance. No new Now, create Memcached crd `minute-memcached` using the existing service account name `my-custom-serviceaccount` in the `spec.podTemplate.spec.serviceAccountName` field. ```console -$ kubectl apply -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/memcached/custom-rbac/mc-custom-db-two.yaml +$ kubectl apply -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/memcached/custom-rbac/mc-custom-db-two.yaml memcached.kubedb.com/quick-memcached created ``` diff --git a/docs/guides/memcached/monitoring/_index.md b/docs/guides/memcached/monitoring/_index.md index bfb9fc0531..5bf909b892 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.12.0: + docs_v0.13.0-rc.0: identifier: mc-monitoring-memcached name: Monitoring parent: mc-memcached-guides weight: 25 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/memcached/monitoring/using-builtin-prometheus.md b/docs/guides/memcached/monitoring/using-builtin-prometheus.md index 07a4f67526..d94caf2569 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.12.0: + docs_v0.13.0-rc.0: identifier: mc-using-builtin-prometheus-monitoring name: Builtin Prometheus Discovery parent: mc-monitoring-memcached weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- @@ -36,7 +36,7 @@ This tutorial will show you how to monitor Memcached server using builtin [Prome namespace/demo created ``` -> Note: YAML files used in this tutorial are stored in [docs/examples/memcached](https://github.com/kubedb/docs/tree/0.12.0/docs/examples/memcached) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/memcached](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/memcached) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Deploy Memcached server with Monitoring Enabled @@ -72,7 +72,7 @@ Here, Let's create the Memcached crd we have shown above. ```console -$ kubectl apply -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/memcached/monitoring/builtin-prom-memcd.yaml +$ kubectl apply -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/memcached/monitoring/builtin-prom-memcd.yaml memcached.kubedb.com/builtin-prom-memcd created ``` @@ -268,7 +268,7 @@ data: Let's create above `ConfigMap`, ```console -$ kubectl apply -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/monitoring/builtin-prometheus/prom-config.yaml +$ kubectl apply -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/monitoring/builtin-prometheus/prom-config.yaml configmap/prometheus-config created ``` diff --git a/docs/guides/memcached/monitoring/using-coreos-prometheus-operator.md b/docs/guides/memcached/monitoring/using-coreos-prometheus-operator.md index 2ff9e839dc..f2c0a64fc0 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.12.0: + docs_v0.13.0-rc.0: identifier: mc-using-coreos-prometheus-operator-monitoring name: Coreos Prometheus Operator parent: mc-monitoring-memcached weight: 15 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -35,7 +35,7 @@ CoreOS [prometheus-operator](https://github.com/coreos/prometheus-operator) prov - If you already don't have a Prometheus server running, deploy one following tutorial from [here](https://github.com/appscode/third-party-tools/blob/master/monitoring/prometheus/coreos-operator/README.md#deploy-prometheus-server). -> Note: YAML files used in this tutorial are stored in [docs/examples/memcached](https://github.com/kubedb/docs/tree/0.12.0/docs/examples/memcached) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/memcached](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/memcached) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Find out required labels for ServiceMonitor @@ -127,7 +127,7 @@ Here, Let's create the Memcached object that we have shown above, ```console -$ kubectl create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/memcached/monitoring/coreos-prom-memcd.yaml +$ kubectl create -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/memcached/monitoring/coreos-prom-memcd.yaml memcached.kubedb.com/coreos-prom-memcd created ``` diff --git a/docs/guides/memcached/private-registry/_index.md b/docs/guides/memcached/private-registry/_index.md index bdadde835c..1c24efb11c 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.12.0: + docs_v0.13.0-rc.0: identifier: mc-private-registry-memcached name: Private Registry parent: mc-memcached-guides weight: 20 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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 322c17046e..ea7f7f64a9 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.12.0: + docs_v0.13.0-rc.0: identifier: mc-using-private-registry-private-registry name: Quickstart parent: mc-private-registry-memcached weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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://github.com/kubedb/docs/raw/0.12.0/docs/examples/memcached/private-registry/demo-2.yaml +$ kubedb create -f https://github.com/kubedb/docs/raw/v0.13.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 88b4716cd3..cf855fbd98 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.12.0: + docs_v0.13.0-rc.0: identifier: mc-quickstart-memcached name: Quickstart parent: mc-memcached-guides weight: 15 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/memcached/quickstart/quickstart.md b/docs/guides/memcached/quickstart/quickstart.md index 82f2573204..1d50870bd5 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.12.0: + docs_v0.13.0-rc.0: identifier: mc-quickstart-quickstart name: Overview parent: mc-quickstart-memcached weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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 server.   lifecycle

-> Note: The yaml files used in this tutorial are stored in [docs/examples/memcached](https://github.com/kubedb/docs/tree/0.12.0/docs/examples/memcached) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: The yaml files used in this tutorial are stored in [docs/examples/memcached](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/memcached) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Before You Begin @@ -77,7 +77,7 @@ spec: ``` ```console -$ kubedb create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/memcached/quickstart/demo-1.yaml +$ kubedb create -f https://github.com/kubedb/docs/raw/v0.13.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://github.com/kubedb/docs/raw/0.12.0/docs/examples/memcached/quickstart/demo-1.yaml +$ kubedb create -f https://github.com/kubedb/docs/raw/v0.13.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 776012c60e..6240ac9cd1 100644 --- a/docs/guides/mongodb/README.md +++ b/docs/guides/mongodb/README.md @@ -1,16 +1,16 @@ --- title: MongoDB menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: mg-readme-mongodb name: MongoDB parent: mg-mongodb-guides weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides -url: /docs/0.12.0/guides/mongodb/ +url: /docs/v0.13.0-rc.0/guides/mongodb/ aliases: - - /docs/0.12.0/guides/mongodb/README/ + - /docs/v0.13.0-rc.0/guides/mongodb/README/ --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -47,47 +47,36 @@ aliases: | 0.10.0 | ✓ | ✓ | ✓ | ✓ | | 0.11.0 | ✓ | ✓ | ✓ | ✓ | | 0.12.0 | ✓ | ✓ | ✓ | ✓ | +| v0.13.0-rc.0 | ✓ | ✓ | ✓ | ✓ | -## Supported MongoDB +## Supported MongoDBVersion CRD Here, ✓ means supported and ✗ means deprecated. -| NAME | VERSION | KubeDB: 0.9.0 | KubeDB: 0.12.0 | KubeDB: 0.10.0 | KubeDB: 0.11.0 | -| :--------: | :-----: | :-----------: | :------------: | :------------: | :------------: | -| 3.4 | 3.4 | ✓ | ✓ | ✓ | ✓ | -| 3.6 | 3.6 | ✓ | ✓ | ✓ | ✓ | -| 4.0.5, 4.0 | 4.0.5 | ✗ | ✗ | ✓ | ✓ | -| 4.1.7 | 4.1.7 | ✗ | ✗ | ✓ | ✓ | - -## Latest Supported MongoDBVersion Objects - -Supported MongoDBVersion objects for KubeDB-0.13.0 release is, - -```bash -$ kubectl get mongodbversions -NAME VERSION DB_IMAGE DEPRECATED AGE -3.4 3.4 kubedb/mongo:3.4 true 110m -3.4-v1 3.4 kubedb/mongo:3.4-v1 true 110m -3.4-v2 3.4 kubedb/mongo:3.4-v2 true 110m -3.4-v3 3.4 kubedb/mongo:3.4-v3 110m -3.4-v4 3.4 kubedb/mongo:3.4-v4 110m -3.6 3.6 kubedb/mongo:3.6 true 110m -3.6-v1 3.6 kubedb/mongo:3.6-v1 true 110m -3.6-v2 3.6 kubedb/mongo:3.6-v2 true 110m -3.6-v3 3.6 kubedb/mongo:3.6-v3 110m -3.6-v4 3.6 kubedb/mongo:3.6-v4 110m -4.0 4.0.5 kubedb/mongo:4.0 true 110m -4.0-v1 4.0.5 kubedb/mongo:4.0-v1 110m -4.0-v2 4.0.5 kubedb/mongo:4.0-v2 110m -4.0.5 4.0.5 kubedb/mongo:4.0.5 true 110m -4.0.5-v1 4.0.5 kubedb/mongo:4.0.5-v1 110m -4.0.5-v2 4.0.5 kubedb/mongo:4.0.5-v2 110m -4.1.7 4.1.7 kubedb/mongo:4.1.7 true 110m -4.1.7-v1 4.1.7 kubedb/mongo:4.1.7-v1 110m -4.1.7-v2 4.1.7 kubedb/mongo:4.1.7-v2 110m -``` - -Here `Deprecated: true` `MongoDBVersions` are not supported in latest release. +| NAME | VERSION | KubeDB: 0.9.0 | KubeDB: 0.10.0 | KubeDB: 0.11.0 | KubeDB: 0.12.0 | KubeDB: v0.13.0-rc.0 | +| :--------------: | :------: | :-----------: | :------------: | :------------: | :------------: | :------------------: | +| 3.4 | 3.4 | ✗ | ✗ | ✗ | ✗ | ✗ | +| 3.4-v1 | 3.4 | ✓ | ✗ | ✗ | ✗ | ✗ | +| 3.4-v2 | 3.4 | ✗ | ✓ | ✓ | ✗ | ✗ | +| 3.4-v3 | 3.4 | ✗ | ✗ | ✗ | ✓ | ✓ | +| 3.4.14 | 3.4.17 | ✗ | ✗ | ✗ | ✗ | ✓ | +| 3.4.22, 3.4-v4 | 3.4.22 | ✗ | ✗ | ✗ | ✗ | ✓ | +| 3.6 | 3.6 | ✗ | ✗ | ✗ | ✗ | ✗ | +| 3.6-v1 | 3.6 | ✓ | ✗ | ✗ | ✗ | ✗ | +| 3.6-v2 | 3.6 | ✗ | ✓ | ✓ | ✗ | ✗ | +| 3.6-v3 | 3.6 | ✗ | ✗ | ✗ | ✓ | ✓ | +| 3.6.8 | 3.6.8 | ✗ | ✗ | ✗ | ✗ | ✓ | +| 3.6.13, 3.6-v4 | 3.6.13 | ✗ | ✗ | ✗ | ✗ | ✓ | +| 4.0.5, 4.0 | 4.0.5 | ✗ | ✓ | ✓ | ✗ | ✗ | +| 4.0.5-v1, 4.0-v1 | 4.0.5 | ✗ | ✗ | ✗ | ✓ | ✓ | +| 4.0.3 | 4.0.3 | ✗ | ✗ | ✗ | ✗ | ✓ | +| 4.0.5-v2 | 4.0.5 | ✗ | ✗ | ✗ | ✗ | ✓ | +| 4.0.11, 4.0-v2 | 4.0.11 | ✗ | ✗ | ✗ | ✗ | ✓ | +| 4.1.7 | 4.1.7 | ✗ | ✓ | ✓ | ✗ | ✗ | +| 4.1.7-v1 | 4.1.7 | ✗ | ✗ | ✗ | ✓ | ✓ | +| 4.1.4 | 4.1.4 | ✗ | ✗ | ✗ | ✗ | ✓ | +| 4.1.7-v2 | 4.1.7-v2 | ✗ | ✗ | ✗ | ✗ | ✓ | +| 4.1.13, 4.1 | 4.1.13 | ✗ | ✗ | ✗ | ✗ | ✓ | ## External tools dependency diff --git a/docs/guides/mongodb/_index.md b/docs/guides/mongodb/_index.md index e54f4bf3b8..a972b4bcd5 100644 --- a/docs/guides/mongodb/_index.md +++ b/docs/guides/mongodb/_index.md @@ -1,10 +1,10 @@ --- title: MongoDB menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: mg-mongodb-guides name: MongoDB parent: guides weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/mongodb/cli/_index.md b/docs/guides/mongodb/cli/_index.md index 2151e78bf3..d5982dfaf5 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.12.0: + docs_v0.13.0-rc.0: identifier: mg-cli-mongodb name: Cli parent: mg-mongodb-guides weight: 45 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/mongodb/cli/cli.md b/docs/guides/mongodb/cli/cli.md index ead4e90277..30d0d17c78 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.12.0: + docs_v0.13.0-rc.0: identifier: mg-cli-cli name: Quickstart parent: mg-cli-mongodb weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- diff --git a/docs/guides/mongodb/clustering/_index.md b/docs/guides/mongodb/clustering/_index.md index d7cca7992b..819660c9d6 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.12.0: + docs_v0.13.0-rc.0: identifier: mg-clustering-mongodb name: Clustering parent: mg-mongodb-guides weight: 17 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/mongodb/clustering/replicaset.md b/docs/guides/mongodb/clustering/replicaset.md index c01343d50c..41ed588745 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.12.0: + docs_v0.13.0-rc.0: identifier: mg-clustering-replicaset name: ReplicaSet Guide parent: mg-clustering-mongodb weight: 15 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- @@ -33,7 +33,7 @@ Before proceeding: namespace/demo created ``` -> Note: The yaml files used in this tutorial are stored in [docs/examples/mongodb](https://github.com/kubedb/docs/tree/0.12.0/docs/examples/mongodb) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: The yaml files used in this tutorial are stored in [docs/examples/mongodb](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/mongodb) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Deploy MongoDB ReplicaSet @@ -62,7 +62,7 @@ spec: ``` ```console -$ kubedb create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/mongodb/clustering/demo-1.yaml +$ kubedb create -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/mongodb/clustering/demo-1.yaml mongodb.kubedb.com/mgo-replicaset created ``` @@ -525,7 +525,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://github.com/kubedb/docs/raw/0.12.0/docs/examples/mongodb/clustering/demo-1.yaml +$ kubedb create -f https://github.com/kubedb/docs/raw/v0.13.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 e51cae54b0..2cc0ac4fcd 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.12.0: + docs_v0.13.0-rc.0: identifier: mg-clustering-replicaset-concept name: ReplicaSet Concept parent: mg-clustering-mongodb weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- diff --git a/docs/guides/mongodb/clustering/sharding.md b/docs/guides/mongodb/clustering/sharding.md index 2c2b32807e..f5c0b315a6 100644 --- a/docs/guides/mongodb/clustering/sharding.md +++ b/docs/guides/mongodb/clustering/sharding.md @@ -1,12 +1,12 @@ --- title: MongoDB Sharding Guide menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: mg-clustering-sharding name: Sharding Guide parent: mg-clustering-mongodb weight: 25 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- @@ -33,7 +33,7 @@ Before proceeding: namespace/demo created ``` -> Note: The yaml files used in this tutorial are stored in [docs/examples/mongodb](https://github.com/kubedb/docs/tree/0.12.0/docs/examples/mongodb) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: The yaml files used in this tutorial are stored in [docs/examples/mongodb](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/mongodb) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Deploy Sharded MongoDB Cluster @@ -72,7 +72,7 @@ spec: ``` ```console -$ kubectl create -f https://github.com/kubedb/docs/raw/0.12.0//docs/examples/mongodb/clustering/mongo-sharding.yaml +$ kubectl create -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0//docs/examples/mongodb/clustering/mongo-sharding.yaml mongodb.kubedb.com/mongo-sh created ``` @@ -993,7 +993,7 @@ In this tutorial, the dormant database can be resumed by creating original Mongo The below command will resume the DormantDatabase `mongo-sh`. ```console -$ kubectl create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/mongodb/clustering/mongo-sh.yaml +$ kubectl create -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/mongodb/clustering/mongo-sh.yaml mongodb.kubedb.com/mongo-sh created ``` diff --git a/docs/guides/mongodb/clustering/sharding_concept.md b/docs/guides/mongodb/clustering/sharding_concept.md index 8ddb7efb88..751f4a7b7c 100644 --- a/docs/guides/mongodb/clustering/sharding_concept.md +++ b/docs/guides/mongodb/clustering/sharding_concept.md @@ -1,12 +1,12 @@ --- title: MongoDB Sharding Concept menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: mg-clustering-sharding-concept name: Sharding Concept parent: mg-clustering-mongodb weight: 20 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- diff --git a/docs/guides/mongodb/configuration/_index.md b/docs/guides/mongodb/configuration/_index.md index c3159ba684..e18c135bf7 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.12.0: + docs_v0.13.0-rc.0: identifier: mg-configuration name: Custom Configuration parent: mg-mongodb-guides weight: 27 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/mongodb/configuration/using-CRD-configuration.md b/docs/guides/mongodb/configuration/using-CRD-configuration.md index a9deae07f8..18fa95fddd 100644 --- a/docs/guides/mongodb/configuration/using-CRD-configuration.md +++ b/docs/guides/mongodb/configuration/using-CRD-configuration.md @@ -1,12 +1,12 @@ --- title: Run MongoDB with Custom Configuration menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: mg-crd-configuration name: Using CRD Config parent: mg-configuration weight: 15 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- @@ -29,7 +29,7 @@ KubeDB supports providing custom configuration for MongoDB via [PodTemplate](/do namespace/demo created ``` -> Note: YAML files used in this tutorial are stored in [docs/examples/mongodb](https://github.com/kubedb/docs/tree/0.12.0/docs/examples/mongodb) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/mongodb](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/mongodb) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Overview @@ -93,7 +93,7 @@ spec: ``` ```console -$ kubedb create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/mongodb/configuration/mgo-misc-config.yaml +$ kubedb create -f https://github.com/kubedb/docs/raw/v0.13.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://github.com/kubedb/docs/raw/0.12.0/docs/examples/mongodb/configuration/snapshot-misc-conf.yaml +$ kubedb create -f https://github.com/kubedb/docs/raw/v0.13.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 6f37e758d1..c9caf7b9ae 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.12.0: + docs_v0.13.0-rc.0: identifier: mg-custom-config-quickstart name: Quickstart parent: mg-configuration weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- @@ -29,7 +29,7 @@ KubeDB supports providing custom configuration for MongoDB. This tutorial will s namespace/demo created ``` -> Note: The yaml files used in this tutorial are stored in [docs/examples/mongodb](https://github.com/kubedb/docs/tree/0.12.0/docs/examples/mongodb) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: The yaml files used in this tutorial are stored in [docs/examples/mongodb](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/mongodb) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Overview @@ -103,7 +103,7 @@ spec: ``` ```console -$ kubectl create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/mongodb/configuration/demo-1.yaml +$ kubectl create -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/mongodb/configuration/demo-1.yaml mongodb.kubedb.com/mgo-custom-config created ``` diff --git a/docs/guides/mongodb/custom-rbac/_index.md b/docs/guides/mongodb/custom-rbac/_index.md index a3c90e9254..ed582640d3 100755 --- a/docs/guides/mongodb/custom-rbac/_index.md +++ b/docs/guides/mongodb/custom-rbac/_index.md @@ -1,10 +1,10 @@ --- title: Run MongoDB with Custom RBAC resources menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: mg-custom-rbac name: Custom RBAC parent: mg-mongodb-guides weight: 85 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/mongodb/custom-rbac/using-custom-rbac.md b/docs/guides/mongodb/custom-rbac/using-custom-rbac.md index 6819a5accc..e7ce475f45 100644 --- a/docs/guides/mongodb/custom-rbac/using-custom-rbac.md +++ b/docs/guides/mongodb/custom-rbac/using-custom-rbac.md @@ -1,12 +1,12 @@ --- title: Run MongoDB with Custom RBAC resources menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: mg-custom-rbac-quickstart name: Custom RBAC parent: mg-custom-rbac weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- @@ -29,7 +29,7 @@ $ kubectl create ns demo namespace/demo created ``` -> Note: YAML files used in this tutorial are stored in [docs/examples/mongodb](https://github.com/kubedb/docs/tree/0.12.0/docs/examples/mongodb) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/mongodb](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/mongodb) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Overview @@ -70,7 +70,7 @@ secrets: Now, we need to create a role that has necessary access permissions for the MongoDB instance named `quick-mongodb`. ```console -$ kubectl apply -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/mongodb/custom-rbac/mg-custom-role.yaml +$ kubectl apply -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/mongodb/custom-rbac/mg-custom-role.yaml role.rbac.authorization.k8s.io/my-custom-role created ``` @@ -130,7 +130,7 @@ subjects: Now, create a MongoDB crd specifying `spec.podTemplate.spec.serviceAccountName` field to `my-custom-serviceaccount`. ```console -$ kubectl apply -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/mongodb/custom-rbac/mg-custom-db.yaml +$ kubectl apply -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/mongodb/custom-rbac/mg-custom-db.yaml mongodb.kubedb.com/quick-mongodb created ``` @@ -195,7 +195,7 @@ An existing service account can be reused in another MongoDB instance. No new ac Now, create MongoDB crd `minute-mongodb` using the existing service account name `my-custom-serviceaccount` in the `spec.podTemplate.spec.serviceAccountName` field. ```console -$ kubectl apply -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/mongodb/custom-rbac/mg-custom-db-two.yaml +$ kubectl apply -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/mongodb/custom-rbac/mg-custom-db-two.yaml mongodb.kubedb.com/quick-mongodb created ``` diff --git a/docs/guides/mongodb/initialization/_index.md b/docs/guides/mongodb/initialization/_index.md index 5796f72440..5f0dc9b92e 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.12.0: + docs_v0.13.0-rc.0: identifier: mg-initialization-mongodb name: Initialization parent: mg-mongodb-guides weight: 25 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/mongodb/initialization/using-script.md b/docs/guides/mongodb/initialization/using-script.md index 0ee2f39caf..b4a1628d6a 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.12.0: + docs_v0.13.0-rc.0: identifier: mg-using-script-initialization name: Using Script parent: mg-initialization-mongodb weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- @@ -31,7 +31,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/docs/tree/0.12.0/docs/examples/mongodb) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: The yaml files used in this tutorial are stored in [docs/examples/mongodb](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/mongodb) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Prepare Initialization Scripts @@ -75,7 +75,7 @@ spec: ``` ```console -$ kubedb create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/mongodb/Initialization/demo-1.yaml +$ kubedb create -f https://github.com/kubedb/docs/raw/v0.13.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 641ceb1303..659b36a0b7 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.12.0: + docs_v0.13.0-rc.0: identifier: mg-using-snapshot-initialization name: From Snapshot parent: mg-initialization-mongodb weight: 15 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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-instant`. 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/docs/tree/0.12.0/docs/examples/mongodb) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: The yaml files used in this tutorial are stored in [docs/examples/mongodb](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/mongodb) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Create MongoDB with Init-Snapshot @@ -51,7 +51,7 @@ spec: ``` ```console -$ kubedb create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/mongodb/Initialization/demo-2.yaml +$ kubedb create -f https://github.com/kubedb/docs/raw/v0.13.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 47a4ce5827..27a52eec6f 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.12.0: + docs_v0.13.0-rc.0: identifier: mg-monitoring-mongodb name: Monitoring parent: mg-mongodb-guides weight: 35 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/mongodb/monitoring/using-builtin-prometheus.md b/docs/guides/mongodb/monitoring/using-builtin-prometheus.md index 966c538d6b..0d0d9d75b1 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.12.0: + docs_v0.13.0-rc.0: identifier: mg-using-builtin-prometheus-monitoring name: Builtin Prometheus Discovery parent: mg-monitoring-mongodb weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- @@ -36,7 +36,7 @@ This tutorial will show you how to monitor MongoDB database using builtin [Prome namespace/demo created ``` -> Note: YAML files used in this tutorial are stored in [docs/examples/mongodb](https://github.com/kubedb/docs/tree/0.12.0/docs/examples/mongodb) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/mongodb](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/mongodb) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Deploy MongoDB with Monitoring Enabled @@ -69,7 +69,7 @@ Here, Let's create the MongoDB crd we have shown above. ```console -$ kubectl apply -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/mongodb/monitoring/builtin-prom-mgo.yaml +$ kubectl apply -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/mongodb/monitoring/builtin-prom-mgo.yaml mongodb.kubedb.com/builtin-prom-mgo created ``` @@ -275,7 +275,7 @@ data: Let's create above `ConfigMap`, ```console -$ kubectl apply -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/monitoring/builtin-prometheus/prom-config.yaml +$ kubectl apply -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/monitoring/builtin-prometheus/prom-config.yaml configmap/prometheus-config created ``` diff --git a/docs/guides/mongodb/monitoring/using-coreos-prometheus-operator.md b/docs/guides/mongodb/monitoring/using-coreos-prometheus-operator.md index d0af5b3773..75d205112c 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.12.0: + docs_v0.13.0-rc.0: identifier: mg-using-coreos-prometheus-operator-monitoring name: Coreos Prometheus Operator parent: mg-monitoring-mongodb weight: 15 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- @@ -36,7 +36,7 @@ CoreOS [prometheus-operator](https://github.com/coreos/prometheus-operator) prov - If you already don't have a Prometheus server running, deploy one following tutorial from [here](https://github.com/appscode/third-party-tools/blob/master/monitoring/prometheus/coreos-operator/README.md#deploy-prometheus-server). -> Note: YAML files used in this tutorial are stored in [docs/examples/mongodb](https://github.com/kubedb/docs/tree/0.12.0/docs/examples/mongodb) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/mongodb](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/mongodb) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Find out required labels for ServiceMonitor @@ -125,7 +125,7 @@ Here, Let's create the MongoDB object that we have shown above, ```console -$ kubectl create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/mongodb/monitoring/coreos-prom-mgo.yaml +$ kubectl create -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/mongodb/monitoring/coreos-prom-mgo.yaml mongodb.kubedb.com/coreos-prom-mgo created ``` diff --git a/docs/guides/mongodb/private-registry/_index.md b/docs/guides/mongodb/private-registry/_index.md index c6f42c7441..a8cc3ef886 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.12.0: + docs_v0.13.0-rc.0: identifier: mg-private-registry-mongodb name: Private Registry parent: mg-mongodb-guides weight: 30 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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 aecb2e39be..f16f9c7887 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.12.0: + docs_v0.13.0-rc.0: identifier: mg-using-private-registry-private-registry name: Quickstart parent: mg-private-registry-mongodb weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- @@ -134,7 +134,7 @@ spec: Now run the command to deploy this `MongoDB` object: ```console -$ kubedb create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/mongodb/private-registry/demo-2.yaml +$ kubedb create -f https://github.com/kubedb/docs/raw/v0.13.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 44e5474002..43a67bcce7 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.12.0: + docs_v0.13.0-rc.0: identifier: mg-quickstart-mongodb name: Quickstart parent: mg-mongodb-guides weight: 15 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/mongodb/quickstart/quickstart.md b/docs/guides/mongodb/quickstart/quickstart.md index c86eab823e..e944c6b179 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.12.0: + docs_v0.13.0-rc.0: identifier: mg-quickstart-quickstart name: Overview parent: mg-quickstart-mongodb weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -40,7 +40,7 @@ This tutorial will show you how to use KubeDB to run a MongoDB database. namespace/demo created ``` -> Note: The yaml files used in this tutorial are stored in [docs/examples/mongodb](https://github.com/kubedb/docs/tree/0.12.0/docs/examples/mongodb) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: The yaml files used in this tutorial are stored in [docs/examples/mongodb](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/mongodb) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Find Available MongoDBVersion @@ -89,7 +89,7 @@ spec: ``` ```console -$ kubedb create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/mongodb/quickstart/demo-1.yaml +$ kubedb create -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/mongodb/quickstart/demo-1.yaml mongodb.kubedb.com/mgo-quickstart created ``` @@ -437,7 +437,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://github.com/kubedb/docs/raw/0.12.0/docs/examples/mongodb/quickstart/demo-1.yaml +$ kubedb create -f https://github.com/kubedb/docs/raw/v0.13.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 792b3361bc..a800134b7f 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.12.0: + docs_v0.13.0-rc.0: identifier: mg-snapshot-mongodb name: Snapshotting parent: mg-mongodb-guides weight: 20 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/mongodb/snapshot/backup-and-restore.md b/docs/guides/mongodb/snapshot/backup-and-restore.md index e88d9b1e25..56be222d9c 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.12.0: + docs_v0.13.0-rc.0: identifier: mg-backup-and-restore-snapshot name: Instant Backup parent: mg-snapshot-mongodb weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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/docs/tree/0.12.0/docs/examples/mongodb) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: The yaml files used in this tutorial are stored in [docs/examples/mongodb](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/mongodb) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Before You Begin @@ -38,7 +38,7 @@ This tutorial will show you how to take snapshots of a KubeDB managed MongoDB da $ kubectl create ns demo namespace/demo created - $ kubedb create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/mongodb/snapshot/demo-1.yaml + $ kubedb create -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/mongodb/snapshot/demo-1.yaml mongodb.kubedb.com/mgo-instant created ``` @@ -97,7 +97,7 @@ spec: ``` ```console -$ kubedb create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/mongodb/snapshot/demo-2.yaml +$ kubedb create -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/mongodb/snapshot/demo-2.yaml snapshot.kubedb.com/snapshot-instant created $ kubedb get snap -n demo @@ -255,7 +255,7 @@ spec: ``` ```console -$ kubedb create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/mongodb/snapshot/demo-3.yaml +$ kubedb create -f https://github.com/kubedb/docs/raw/v0.13.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 3413e480eb..55ca0833cd 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.12.0: + docs_v0.13.0-rc.0: identifier: mg-scheduled-backup-snapshot name: Scheduled Backup parent: mg-snapshot-mongodb weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- @@ -31,7 +31,7 @@ This tutorial will show you how to use KubeDB to take scheduled snapshot of a Mo namespace/demo created ``` -> Note: The yaml files used in this tutorial are stored in [docs/examples/mongodb](https://github.com/kubedb/docs/tree/0.12.0/docs/examples/mongodb) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: The yaml files used in this tutorial are stored in [docs/examples/mongodb](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/mongodb) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Scheduled Backups @@ -95,7 +95,7 @@ spec: ``` ```console -$ kubedb create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/mongodb/snapshot/demo-4.yaml +$ kubedb create -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/mongodb/snapshot/demo-4.yaml mongodb.kubedb.com/mgo-scheduled created ``` diff --git a/docs/guides/mongodb/tls-ssl-encryption/_index.md b/docs/guides/mongodb/tls-ssl-encryption/_index.md index 30824a3a1b..4872b50ad6 100755 --- a/docs/guides/mongodb/tls-ssl-encryption/_index.md +++ b/docs/guides/mongodb/tls-ssl-encryption/_index.md @@ -1,10 +1,10 @@ --- title: Run mongodb with TLS menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: mg-tls name: TLS/SSL Encryption parent: mg-mongodb-guides weight: 19 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/mongodb/tls-ssl-encryption/tls-ssl-encryption.md b/docs/guides/mongodb/tls-ssl-encryption/tls-ssl-encryption.md index 0b4053197d..ef8adcb8e3 100644 --- a/docs/guides/mongodb/tls-ssl-encryption/tls-ssl-encryption.md +++ b/docs/guides/mongodb/tls-ssl-encryption/tls-ssl-encryption.md @@ -1,12 +1,12 @@ --- title: TLS/SSL (Transport Encryption) menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: mg-tls-encryption name: TLS/SSL (Transport Encryption) parent: mg-tls weight: 15 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- @@ -29,7 +29,7 @@ KubeDB supports providing TLS/SSL encryption (via, `sslMode` and `clusterAuthMod namespace/demo created ``` -> Note: YAML files used in this tutorial are stored in [docs/examples/mongodb](https://github.com/kubedb/docs/tree/0.12.0/docs/examples/mongodb) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/mongodb](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/mongodb) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Overview diff --git a/docs/guides/mysql/README.md b/docs/guides/mysql/README.md index e9a8b4377a..506e6aa832 100644 --- a/docs/guides/mysql/README.md +++ b/docs/guides/mysql/README.md @@ -1,16 +1,16 @@ --- title: MySQL menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: my-readme-mysql name: MySQL parent: my-mysql-guides weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides -url: /docs/0.12.0/guides/mysql/ +url: /docs/v0.13.0-rc.0/guides/mysql/ aliases: - - /docs/0.12.0/guides/mysql/README/ + - /docs/v0.13.0-rc.0/guides/mysql/README/ --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -30,16 +30,12 @@ aliases: | Builtin Prometheus Discovery | ✓ | | Using CoreOS Prometheus Operator | ✓ | -
- ## Life Cycle of a MySQL Object

  lifecycle

-
- ## Supported MySQL Versions | KubeDB Version | MySQL:8.0 | MySQL:5.7 | @@ -50,26 +46,27 @@ aliases: | 0.10.0 | ✓ | ✓ | | 0.11.0 | ✓ | ✓ | | 0.12.0 | ✓ | ✓ | +| v0.13.0-rc.0 | ✓ | ✓ | ## Supported MySQLVersion CRD Here, ✓ means supported and ✗ means deprecated. -| NAME | VERSION | KubeDB: 0.9.0 | KubeDB: 0.10.0 | KubeDB: 0.11.0 | KubeDB: 0.12.0 | -| :------: | :-------: | :-------------: | :--------------: | :--------------: | :--------------: | -| 5 | 5 | ✗ | ✗ | ✗ | ✗ | -| 5.7 | 5.7 | ✗ | ✗ | ✗ | ✗ | -| 8 | 8 | ✗ | ✗ | ✗ | ✗ | -| 8.0 | 8.0 | ✗ | ✗ | ✗ | ✗ | -| 5-v1 | 5 | ✓ | ✗ | ✗ | ✗ | -| 5.7-v1 | 5.7 | ✓ | ✓ | ✗ | ✓ | -| 5.7-v2 | 5.7.25 | ✗ | ✗ | ✗ | ✓ | -| 5.7.25 | 5.7.25 | ✗ | ✗ | ✗ | ✓ | -| 8-v1 | 8 | ✓ | ✗ | ✗ | ✗ | -| 8.0-v1 | 8.0.3 | ✓ | ✗ | ✗ | ✓ | -| 8.0-v2 | 8.0.14 | ✗ | ✓ | ✓ | ✓ | -| 8.0.3 | 8.0.3 | ✗ | ✓ | ✓ | ✓ | -| 8.0.14 | 8.0.14 | ✗ | ✓ | ✓ | ✓ | +| NAME | VERSION | KubeDB: 0.9.0 | KubeDB: 0.10.0 | KubeDB: 0.11.0 | KubeDB: 0.12.0 | KubeDB: v0.13.0-rc.0 | +| :----: | :-----: | :-----------: | :------------: | :------------: | :------------: | :------------------: | +| 5 | 5 | ✗ | ✗ | ✗ | ✗ | ✗ | +| 5.7 | 5.7 | ✗ | ✗ | ✗ | ✗ | ✗ | +| 8 | 8 | ✗ | ✗ | ✗ | ✗ | ✗ | +| 8.0 | 8.0 | ✗ | ✗ | ✗ | ✗ | ✗ | +| 5-v1 | 5 | ✓ | ✗ | ✗ | ✗ | ✗ | +| 5.7-v1 | 5.7 | ✓ | ✓ | ✗ | ✓ | ✓ | +| 5.7-v2 | 5.7.25 | ✗ | ✗ | ✗ | ✓ | ✓ | +| 5.7.25 | 5.7.25 | ✗ | ✗ | ✗ | ✓ | ✓ | +| 8-v1 | 8 | ✓ | ✗ | ✗ | ✗ | ✗ | +| 8.0-v1 | 8.0.3 | ✓ | ✗ | ✗ | ✓ | ✓ | +| 8.0-v2 | 8.0.14 | ✗ | ✓ | ✓ | ✓ | ✓ | +| 8.0.3 | 8.0.3 | ✗ | ✓ | ✓ | ✓ | ✓ | +| 8.0.14 | 8.0.14 | ✗ | ✓ | ✓ | ✓ | ✓ | ## External tools dependency @@ -78,8 +75,6 @@ Here, ✓ means supported and ✗ means deprecated. | [peer-finder](https://github.com/kubernetes/contrib/tree/master/peer-finder) | latest | | [osm](https://github.com/appscode/osm) | 0.9.1 | -
- ## User Guide - [Quickstart MySQL](/docs/guides/mysql/quickstart/quickstart.md) with KubeDB Operator. diff --git a/docs/guides/mysql/_index.md b/docs/guides/mysql/_index.md index f93ff87d1f..30ca0b9714 100644 --- a/docs/guides/mysql/_index.md +++ b/docs/guides/mysql/_index.md @@ -1,10 +1,10 @@ --- title: MySQL menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: my-mysql-guides name: MySQL parent: guides weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/mysql/cli/_index.md b/docs/guides/mysql/cli/_index.md index 218835ea2f..02f8ea28e2 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.12.0: + docs_v0.13.0-rc.0: identifier: my-cli-mysql name: Cli parent: my-mysql-guides weight: 45 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/mysql/cli/cli.md b/docs/guides/mysql/cli/cli.md index 7c061bd3fe..5d1e4a5a8a 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.12.0: + docs_v0.13.0-rc.0: identifier: my-cli-cli name: Quickstart parent: my-cli-mysql weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- diff --git a/docs/guides/mysql/clustering/_index.md b/docs/guides/mysql/clustering/_index.md index 7de8baa8bf..93c8818598 100644 --- a/docs/guides/mysql/clustering/_index.md +++ b/docs/guides/mysql/clustering/_index.md @@ -1,10 +1,10 @@ --- title: MySQL Clustering menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: my-clustering-mysql name: MySQL Clustering parent: my-mysql-guides weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/mysql/clustering/group_replication_single_primary.md b/docs/guides/mysql/clustering/group_replication_single_primary.md index 6083046fff..63f88e840f 100644 --- a/docs/guides/mysql/clustering/group_replication_single_primary.md +++ b/docs/guides/mysql/clustering/group_replication_single_primary.md @@ -1,12 +1,12 @@ --- title: MySQL Group Replcation Guide menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: my-group-replication-guide-mysql name: MySQL Group Replication Guide parent: my-clustering-mysql weight: 20 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- @@ -33,7 +33,7 @@ Before proceeding: namespace/demo created ``` -> Note: The yaml files used in this tutorial are stored in [docs/examples/mysql](https://github.com/kubedb/docs/tree/0.12.0/docs/examples/mysql) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: The yaml files used in this tutorial are stored in [docs/examples/mysql](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/mysql) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Deploy MySQL Cluster @@ -67,7 +67,7 @@ spec: ``` ```console -$ kubedb create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/mysql/clustering/demo-1.yaml +$ kubedb create -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/mysql/clustering/demo-1.yaml mysql.kubedb.com/my-group created ``` diff --git a/docs/guides/mysql/clustering/overview.md b/docs/guides/mysql/clustering/overview.md index 1d7572d373..51dae5c529 100644 --- a/docs/guides/mysql/clustering/overview.md +++ b/docs/guides/mysql/clustering/overview.md @@ -1,12 +1,12 @@ --- title: MySQL Group Replication Overview menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: my-group-replication-overview-mysql name: MySQL Group Replication Overview parent: my-clustering-mysql weight: 15 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- diff --git a/docs/guides/mysql/configuration/_index.md b/docs/guides/mysql/configuration/_index.md index d0a54870fa..9684518ba6 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.12.0: + docs_v0.13.0-rc.0: identifier: my-custom-config name: Custom Configuration parent: my-mysql-guides weight: 50 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/mysql/configuration/using-CRD-configuration.md b/docs/guides/mysql/configuration/using-CRD-configuration.md index 6648f30545..fa667ec394 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.12.0: + docs_v0.13.0-rc.0: identifier: my-crd-configuration name: Using CRD Config parent: my-custom-config weight: 15 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- @@ -29,7 +29,7 @@ KubeDB supports providing custom configuration for MySQL via [PodTemplate](/docs namespace/demo created ``` -> Note: YAML files used in this tutorial are stored in [docs/examples/mysql](https://github.com/kubedb/docs/tree/0.12.0/docs/examples/mysql) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/mysql](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/mysql) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Overview @@ -95,7 +95,7 @@ spec: ``` ```console -$ kubedb create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/mysql/configuration/mysql-misc-config.yaml +$ kubedb create -f https://github.com/kubedb/docs/raw/v0.13.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://github.com/kubedb/docs/raw/0.12.0/docs/examples/mysql/quickstart/demo-1.yaml +$ kubectl create -f https://github.com/kubedb/docs/raw/v0.13.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://github.com/kubedb/docs/raw/0.12.0/docs/examples/mysql/configuration/snapshot-misc-conf.yaml +$ kubedb create -f https://github.com/kubedb/docs/raw/v0.13.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 6e58b508bc..bb04d018bd 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.12.0: + docs_v0.13.0-rc.0: identifier: my-custom-config-file name: Using Config File parent: my-custom-config weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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/docs/tree/0.12.0/docs/examples/mysql) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/mysql](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/mysql) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Overview @@ -89,7 +89,7 @@ metadata: Now, create MySQL crd specifying `spec.configSource` field. ```console -$ kubectl apply -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/mysql/configuration/mysql-custom.yaml +$ kubectl apply -f https://github.com/kubedb/docs/raw/v0.13.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://github.com/kubedb/docs/raw/0.12.0/docs/examples/mysql/quickstart/demo-1.yaml + $ kubectl create -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/mysql/quickstart/demo-1.yaml deployment.extensions/myadmin created service/myadmin created ``` diff --git a/docs/guides/mysql/custom-rbac/_index.md b/docs/guides/mysql/custom-rbac/_index.md index 7b59b4cece..7c738465a6 100755 --- a/docs/guides/mysql/custom-rbac/_index.md +++ b/docs/guides/mysql/custom-rbac/_index.md @@ -1,10 +1,10 @@ --- title: Run MySQL with Custom RBAC resources menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: my-custom-rbac name: Custom RBAC parent: my-mysql-guides weight: 85 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/mysql/custom-rbac/using-custom-rbac.md b/docs/guides/mysql/custom-rbac/using-custom-rbac.md index de930f853d..00c891a2a6 100644 --- a/docs/guides/mysql/custom-rbac/using-custom-rbac.md +++ b/docs/guides/mysql/custom-rbac/using-custom-rbac.md @@ -1,12 +1,12 @@ --- title: Run MySQL with Custom RBAC resources menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: my-custom-rbac-quickstart name: Custom RBAC parent: my-custom-rbac weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- @@ -29,7 +29,7 @@ $ kubectl create ns demo namespace/demo created ``` -> Note: YAML files used in this tutorial are stored in [docs/examples/mysql](https://github.com/kubedb/docs/tree/0.12.0/docs/examples/mysql) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/mysql](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/mysql) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Overview @@ -70,7 +70,7 @@ secrets: Now, we need to create a role that has necessary access permissions for the MySQL instance named `quick-mysql`. ```console -$ kubectl apply -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/mysql/custom-rbac/my-custom-role.yaml +$ kubectl apply -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/mysql/custom-rbac/my-custom-role.yaml role.rbac.authorization.k8s.io/my-custom-role created ``` @@ -130,7 +130,7 @@ subjects: Now, create a MySQL crd specifying `spec.podTemplate.spec.serviceAccountName` field to `my-custom-serviceaccount`. ```console -$ kubectl apply -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/mysql/custom-rbac/my-custom-db.yaml +$ kubectl apply -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/mysql/custom-rbac/my-custom-db.yaml mysql.kubedb.com/quick-mysql created ``` @@ -206,7 +206,7 @@ An existing service account can be reused in another MySQL instance. No new acce Now, create MySQL crd `minute-mysql` using the existing service account name `my-custom-serviceaccount` in the `spec.podTemplate.spec.serviceAccountName` field. ```console -$ kubectl apply -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/mysql/custom-rbac/my-custom-db-two.yaml +$ kubectl apply -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/mysql/custom-rbac/my-custom-db-two.yaml mysql.kubedb.com/quick-mysql created ``` diff --git a/docs/guides/mysql/initialization/_index.md b/docs/guides/mysql/initialization/_index.md index 855a5a6232..82720bb7bb 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.12.0: + docs_v0.13.0-rc.0: identifier: my-initialization-mysql name: Initialization parent: my-mysql-guides weight: 25 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/mysql/initialization/using-script.md b/docs/guides/mysql/initialization/using-script.md index 592b8c7a78..726e67330c 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.12.0: + docs_v0.13.0-rc.0: identifier: my-using-script-initialization name: Using Script parent: my-initialization-mysql weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- @@ -17,7 +17,7 @@ section_menu_id: guides This tutorial will show you how to use KubeDB to initialize a MySQL database with \*.sql, \*.sh and/or \*.sql.gz script. In this tutorial we will use .sql script stored in GitHub repository [kubedb/mysql-init-scripts](https://github.com/kubedb/mysql-init-scripts). -> Note: The yaml files that are used in this tutorial are stored in [docs/examples](https://github.com/kubedb/docs/tree/0.12.0/docs/examples) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: The yaml files that are used in this tutorial are stored in [docs/examples](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Before You Begin @@ -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://github.com/kubedb/docs/raw/0.12.0/docs/examples/mysql/quickstart/demo-1.yaml + $ kubectl create -f https://github.com/kubedb/docs/raw/v0.13.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://github.com/kubedb/docs/raw/0.12.0/docs/examples/mysql/Initialization/demo-1.yaml +$ kubedb create -f https://github.com/kubedb/docs/raw/v0.13.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 87ebf3d796..f270c7a3fd 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.12.0: + docs_v0.13.0-rc.0: identifier: my-using-snapshot-initialization name: From Snapshot parent: my-initialization-mysql weight: 15 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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 MySQL database wit - This tutorial assumes that you have created a namespace `demo` and a snapshot `snapshot-instant`. Follow the steps [here](/docs/guides/mysql/snapshot/backup-and-restore.md) to create a database and take [instant snapshot](/docs/guides/mysql/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 that are used in this tutorial are stored in [docs/examples](https://github.com/kubedb/docs/tree/0.12.0/docs/examples) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: The yaml files that are used in this tutorial are stored in [docs/examples](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Create MySQL with Init-Snapshot @@ -53,7 +53,7 @@ spec: ``` ```console -$ kubedb create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/mysql/Initialization/demo-2.yaml +$ kubedb create -f https://github.com/kubedb/docs/raw/v0.13.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 9fb1becc1e..597b00d815 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.12.0: + docs_v0.13.0-rc.0: identifier: my-monitoring-mysql name: Monitoring parent: my-mysql-guides weight: 35 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/mysql/monitoring/using-builtin-prometheus.md b/docs/guides/mysql/monitoring/using-builtin-prometheus.md index 0c2567c7f0..77cef355f4 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.12.0: + docs_v0.13.0-rc.0: identifier: my-using-builtin-prometheus-monitoring name: Builtin Prometheus Discovery parent: my-monitoring-mysql weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- @@ -36,7 +36,7 @@ This tutorial will show you how to monitor MySQL database using builtin [Prometh namespace/demo created ``` -> Note: YAML files used in this tutorial are stored in [docs/examples/mysql](https://github.com/kubedb/docs/tree/0.12.0/docs/examples/mysql) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/mysql](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/mysql) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Deploy MySQL with Monitoring Enabled @@ -69,7 +69,7 @@ Here, Let's create the MySQL crd we have shown above. ```console -$ kubectl apply -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/mysql/monitoring/builtin-prom-mysql.yaml +$ kubectl apply -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/mysql/monitoring/builtin-prom-mysql.yaml mysql.kubedb.com/builtin-prom-mysql created ``` @@ -274,7 +274,7 @@ data: Let's create above `ConfigMap`, ```console -$ kubectl apply -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/monitoring/builtin-prometheus/prom-config.yaml +$ kubectl apply -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/monitoring/builtin-prometheus/prom-config.yaml configmap/prometheus-config created ``` diff --git a/docs/guides/mysql/monitoring/using-coreos-prometheus-operator.md b/docs/guides/mysql/monitoring/using-coreos-prometheus-operator.md index e3d1d75862..8278ba0b0a 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.12.0: + docs_v0.13.0-rc.0: identifier: my-using-coreos-prometheus-operator-monitoring name: Coreos Prometheus Operator parent: my-monitoring-mysql weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- @@ -36,7 +36,7 @@ CoreOS [prometheus-operator](https://github.com/coreos/prometheus-operator) prov - If you already don't have a Prometheus server running, deploy one following tutorial from [here](https://github.com/appscode/third-party-tools/blob/master/monitoring/prometheus/coreos-operator/README.md#deploy-prometheus-server). -> Note: YAML files used in this tutorial are stored in [docs/examples/mysql](https://github.com/kubedb/docs/tree/0.12.0/docs/examples/mysql) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/mysql](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/mysql) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Find out required labels for ServiceMonitor @@ -125,7 +125,7 @@ Here, Let's create the MySQL object that we have shown above, ```console -$ kubectl create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/mysql/monitoring/coreos-prom-mysql.yaml +$ kubectl create -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/mysql/monitoring/coreos-prom-mysql.yaml mysql.kubedb.com/coreos-prom-mysql created ``` diff --git a/docs/guides/mysql/private-registry/_index.md b/docs/guides/mysql/private-registry/_index.md index 4b8634b44d..6a52af7cee 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.12.0: + docs_v0.13.0-rc.0: identifier: my-private-registry-mysql name: Private Registry parent: my-mysql-guides weight: 30 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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 881010b9f4..6d7481bdf5 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.12.0: + docs_v0.13.0-rc.0: identifier: my-using-private-registry-private-registry name: Quickstart parent: my-private-registry-mysql weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- @@ -130,7 +130,7 @@ spec: Now run the command to deploy this `MySQL` object: ```console -$ kubedb create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/mysql/private-registry/demo-2.yaml +$ kubedb create -f https://github.com/kubedb/docs/raw/v0.13.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 6cf5c3fec8..e052ddf5ad 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.12.0: + docs_v0.13.0-rc.0: identifier: my-quickstart-mysql name: Quickstart parent: my-mysql-guides weight: 15 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/mysql/quickstart/quickstart.md b/docs/guides/mysql/quickstart/quickstart.md index 81a9b69153..7ad359e20c 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.12.0: + docs_v0.13.0-rc.0: identifier: my-quickstart-quickstart name: Overview parent: my-quickstart-mysql weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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/docs/tree/0.12.0/docs/examples/mysql) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: The yaml files used in this tutorial are stored in [docs/examples/mysql](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/mysql) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## 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://github.com/kubedb/docs/raw/0.12.0/docs/examples/mysql/quickstart/demo-1.yaml + $ kubectl create -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/mysql/quickstart/demo-1.yaml deployment.extensions/myadmin created service/myadmin created @@ -114,7 +114,7 @@ spec: ``` ```console -$ kubedb create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/mysql/quickstart/demo-2.yaml +$ kubedb create -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/mysql/quickstart/demo-2.yaml mysql.kubedb.com/mysql-quickstart created ``` @@ -381,7 +381,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://github.com/kubedb/docs/raw/0.12.0/docs/examples/mysql/quickstart/demo-2.yaml +$ kubedb create -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/mysql/quickstart/demo-2.yaml mysql.kubedb.com/mysql-quickstart created ``` diff --git a/docs/guides/mysql/snapshot/_index.md b/docs/guides/mysql/snapshot/_index.md index af876cd4e2..27d5dcaf88 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.12.0: + docs_v0.13.0-rc.0: identifier: my-snapshot-mysql name: Snapshotting parent: my-mysql-guides weight: 20 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/mysql/snapshot/backup-and-restore.md b/docs/guides/mysql/snapshot/backup-and-restore.md index 62a55f4561..303c6cd163 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.12.0: + docs_v0.13.0-rc.0: identifier: my-backup-and-restore-snapshot name: Instant Backup parent: my-snapshot-mysql weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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/docs/tree/0.12.0/docs/examples/mysql) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: The yaml files used in this tutorial are stored in [docs/examples/mysql](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/mysql) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Before You Begin @@ -37,7 +37,7 @@ This tutorial will show you how to take snapshots of a KubeDB managed MySQL data $ kubectl create ns demo namespace/demo created - $ kubedb create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/mysql/snapshot/demo-1.yaml + $ kubedb create -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/mysql/snapshot/demo-1.yaml mysql.kubedb.com/mysql-instant created ``` @@ -96,7 +96,7 @@ spec: ``` ```console -$ kubedb create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/mysql/snapshot/demo-2.yaml +$ kubedb create -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/mysql/snapshot/demo-2.yaml snapshot.kubedb.com/snap-mysql-instant created $ kubedb get snap -n demo @@ -243,7 +243,7 @@ spec: ``` ```console -$ kubedb create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/mysql/snapshot/demo-3.yaml +$ kubedb create -f https://github.com/kubedb/docs/raw/v0.13.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 793276b463..78e21a1230 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.12.0: + docs_v0.13.0-rc.0: identifier: my-scheduled-backup-snapshot name: Scheduled Backup parent: my-snapshot-mysql weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- @@ -29,7 +29,7 @@ This tutorial will show you how to use KubeDB to take scheduled snapshot of a My namespace/demo created ``` -> Note: The yaml files that are used in this tutorial are stored in [docs/examples](https://github.com/kubedb/docs/tree/0.12.0/docs/examples) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: The yaml files that are used in this tutorial are stored in [docs/examples](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Scheduled Backups @@ -90,7 +90,7 @@ spec: ``` ```console -$ kubedb create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/mysql/snapshot/demo-4.yaml +$ kubedb create -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/mysql/snapshot/demo-4.yaml mysql.kubedb.com/mysql-scheduled created ``` diff --git a/docs/guides/mysql/upgrading/_index.md b/docs/guides/mysql/upgrading/_index.md index 3893408b60..cce5830bf0 100644 --- a/docs/guides/mysql/upgrading/_index.md +++ b/docs/guides/mysql/upgrading/_index.md @@ -1,10 +1,10 @@ --- title: Upgrading MySQL menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: my-upgrading-mysql name: Upgrading MySQL parent: my-mysql-guides weight: 60 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/mysql/upgrading/manual.md b/docs/guides/mysql/upgrading/manual.md index e2086d771c..5e5842b8a6 100644 --- a/docs/guides/mysql/upgrading/manual.md +++ b/docs/guides/mysql/upgrading/manual.md @@ -1,12 +1,12 @@ --- title: Upgrading MySQL menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: my-upgrade-manul name: Manual parent: my-upgrading-mysql weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- diff --git a/docs/guides/postgres/README.md b/docs/guides/postgres/README.md index 53dfe886ec..81a5728886 100644 --- a/docs/guides/postgres/README.md +++ b/docs/guides/postgres/README.md @@ -1,16 +1,16 @@ --- title: Postgres menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: pg-readme-postgres name: Postgres parent: pg-postgres-guides weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides -url: /docs/0.12.0/guides/postgres/ +url: /docs/v0.13.0-rc.0/guides/postgres/ aliases: - - /docs/0.12.0/guides/postgres/README/ + - /docs/v0.13.0-rc.0/guides/postgres/README/ --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -37,16 +37,12 @@ aliases: | Custom Configuration | ✓ | | Using Custom docker image | ✓ | -
- ## Life Cycle of a PostgreSQL Object

lifecycle

-
- ## Supported PostgreSQL Versions | KubeDB Version | Postgres:9.5 | Postgres:9.6 | Postgres:10.2 | Postgres:10.6 | Postgres:11.1 | @@ -56,24 +52,26 @@ aliases: | 0.9.0 | ✗ | ✓ | ✓ | ✗ | ✗ | | 0.10.0 | ✗ | ✓ | ✓ | ✓ | ✓ | | 0.11.0 | ✗ | ✓ | ✓ | ✓ | ✓ | +| 0.12.0 | ✗ | ✓ | ✓ | ✓ | ✓ | +| v0.13.0-rc.0 | ✗ | ✓ | ✓ | ✓ | ✓ | ## Supported PostgresVersion CRD Here, ✓ means supported and ✗ means deprecated. -| NAME | VERSION | KubeDB: 0.9.0 | KubeDB: 0.10.0 | KubeDB: 0.11.0 | KubeDB: 0.12.0 | -| :------: | :-----: | :-----------: | :------------: | :------------: | :------------: | -| 9.6 | 9.6 | ✗ | ✗ | ✗ | ✗ | -| 9.6.7 | 9.6.7 | ✗ | ✗ | ✗ | ✗ | -| 10.2 | 10.2 | ✗ | ✗ | ✗ | ✗ | -| 9.6-v1 | 9.6 | ✓ | ✗ | ✗ | ✗ | -| 9.6.7-v1 | 9.6.7 | ✓ | ✗ | ✗ | ✗ | -| 10.2-v1 | 10.2 | ✓ | ✗ | ✗ | ✗ | -| 9.6-v2 | 9.6 | ✗ | ✓ | ✓ | ✓ | -| 9.6.7-v2 | 9.6.7 | ✗ | ✓ | ✓ | ✓ | -| 10.2-v2 | 10.2 | ✗ | ✓ | ✓ | ✓ | -| 10.6 | 10.6 | ✗ | ✓ | ✓ | ✓ | -| 11.1 | 11.1 | ✗ | ✓ | ✓ | ✓ | +| NAME | VERSION | KubeDB: 0.9.0 | KubeDB: 0.10.0 | KubeDB: 0.11.0 | KubeDB: 0.12.0 | KubeDB: v0.13.0-rc.0 | +| :------: | :-----: | :-----------: | :------------: | :------------: | :------------: | :------------------: | +| 9.6 | 9.6 | ✗ | ✗ | ✗ | ✗ | ✗ | +| 9.6.7 | 9.6.7 | ✗ | ✗ | ✗ | ✗ | ✗ | +| 10.2 | 10.2 | ✗ | ✗ | ✗ | ✗ | ✗ | +| 9.6-v1 | 9.6 | ✓ | ✗ | ✗ | ✗ | ✗ | +| 9.6.7-v1 | 9.6.7 | ✓ | ✗ | ✗ | ✗ | ✗ | +| 10.2-v1 | 10.2 | ✓ | ✗ | ✗ | ✗ | ✗ | +| 9.6-v2 | 9.6 | ✗ | ✓ | ✓ | ✓ | ✓ | +| 9.6.7-v2 | 9.6.7 | ✗ | ✓ | ✓ | ✓ | ✓ | +| 10.2-v2 | 10.2 | ✗ | ✓ | ✓ | ✓ | ✓ | +| 10.6 | 10.6 | ✗ | ✓ | ✓ | ✓ | ✓ | +| 11.1 | 11.1 | ✗ | ✓ | ✓ | ✓ | ✓ | ## External tools dependency diff --git a/docs/guides/postgres/_index.md b/docs/guides/postgres/_index.md index 0277ef5126..79f4dc5f57 100644 --- a/docs/guides/postgres/_index.md +++ b/docs/guides/postgres/_index.md @@ -1,10 +1,10 @@ --- title: PostgreSQL menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: pg-postgres-guides name: PostgreSQL parent: guides weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/postgres/cli/_index.md b/docs/guides/postgres/cli/_index.md index d5a2bf7e17..bcd5ff487e 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.12.0: + docs_v0.13.0-rc.0: identifier: pg-cli-postgres name: CLI parent: pg-postgres-guides weight: 55 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/postgres/cli/cli.md b/docs/guides/postgres/cli/cli.md index a8a241d44b..11e8834bb0 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.12.0: + docs_v0.13.0-rc.0: identifier: pg-cli-cli name: Quickstart parent: pg-cli-postgres weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- diff --git a/docs/guides/postgres/clustering/_index.md b/docs/guides/postgres/clustering/_index.md index a74f41b829..55357699dc 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.12.0: + docs_v0.13.0-rc.0: identifier: pg-clustering-postgres name: Clustering parent: pg-postgres-guides weight: 20 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/postgres/clustering/ha_cluster.md b/docs/guides/postgres/clustering/ha_cluster.md index e04746a886..d89da726e3 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.12.0: + docs_v0.13.0-rc.0: identifier: pg-ha-cluster-clustering name: HA Setup parent: pg-clustering-postgres weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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 bc5dde371a..049de985d9 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.12.0: + docs_v0.13.0-rc.0: identifier: pg-streaming-replication-clustering name: Streaming Replication parent: pg-clustering-postgres weight: 15 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- @@ -30,7 +30,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/docs/tree/0.12.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Create PostgreSQL with Streaming replication @@ -98,7 +98,7 @@ Here, Now create this Postgres object with Streaming Replication support ```console -$ kubedb create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/postgres/clustering/ha-postgres.yaml +$ kubedb create -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/postgres/clustering/ha-postgres.yaml postgres.kubedb.com/ha-postgres created ``` @@ -324,7 +324,7 @@ Here, Now create this Postgres object ```console -$ kubedb create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/postgres/clustering/hot-postgres.yaml +$ kubedb create -f https://github.com/kubedb/docs/raw/v0.13.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 564c35cd45..4de69933de 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.12.0: + docs_v0.13.0-rc.0: identifier: pg-custom-config name: Custom Configuration parent: pg-postgres-guides weight: 40 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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 41d8ef2d88..6b85f6e5f5 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.12.0: + docs_v0.13.0-rc.0: identifier: pg-custom-config-quickstart name: Quickstart parent: pg-custom-config weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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/docs/tree/0.12.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Overview @@ -53,7 +53,7 @@ shared_buffers=256MB Now, create a configMap with this configuration file. ```console -$ kubectl create configmap -n demo pg-custom-config --from-literal=user.conf="$(curl -fsSL https://github.com/kubedb/docs/raw/0.12.0/docs/examples/postgres/custom-config/user.conf)" +$ kubectl create configmap -n demo pg-custom-config --from-literal=user.conf="$(curl -fsSL https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/postgres/custom-config/user.conf)" configmap/pg-custom-config created ``` @@ -79,7 +79,7 @@ metadata: Now, create Postgres crd specifying `spec.configSource` field. ```console -$ kubectl apply -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/postgres/custom-config/pg-custom-config.yaml +$ kubectl apply -f https://github.com/kubedb/docs/raw/v0.13.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-rbac/_index.md b/docs/guides/postgres/custom-rbac/_index.md index bfdb7b8ac2..d8d0464802 100755 --- a/docs/guides/postgres/custom-rbac/_index.md +++ b/docs/guides/postgres/custom-rbac/_index.md @@ -1,10 +1,10 @@ --- title: Run PostgreSQL with Custom RBAC resources menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: pg-custom-rbac name: Custom RBAC parent: pg-postgres-guides weight: 80 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/postgres/custom-rbac/using-custom-rbac.md b/docs/guides/postgres/custom-rbac/using-custom-rbac.md index 1b91f1f87a..bc1b666fd7 100644 --- a/docs/guides/postgres/custom-rbac/using-custom-rbac.md +++ b/docs/guides/postgres/custom-rbac/using-custom-rbac.md @@ -1,12 +1,12 @@ --- title: Run PostgreSQL with Custom RBAC resources menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: pg-custom-rbac-quickstart name: Custom RBAC parent: pg-custom-rbac weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- @@ -29,7 +29,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/docs/tree/0.12.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Overview @@ -70,7 +70,7 @@ secrets: Now, we need to create a role that has necessary access permissions for the PostgreSQl Database named `quick-postgres`. ```console -$ kubectl apply -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/postgres/custom-rbac/pg-custom-role.yaml +$ kubectl apply -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/postgres/custom-rbac/pg-custom-role.yaml role.rbac.authorization.k8s.io/my-custom-role created ``` @@ -160,7 +160,7 @@ subjects: Now, create a Postgres CRD specifying `spec.podTemplate.spec.serviceAccountName` field to `my-custom-serviceaccount`. ```console -$ kubectl apply -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/postgres/custom-rbac/pg-custom-db.yaml +$ kubectl apply -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/postgres/custom-rbac/pg-custom-db.yaml postgres.kubedb.com/quick-postgres created ``` @@ -242,7 +242,7 @@ An existing service account can be reused in another Postgres Database. However, For example, to reuse `my-custom-serviceaccount` in a new Database `minute-postgres`, create a role that has all the necessary access permissions for this PostgreSQl Database. ```console -$ kubectl apply -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/postgres/custom-rbac/pg-custom-role-two.yaml +$ kubectl apply -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/postgres/custom-rbac/pg-custom-role-two.yaml role.rbac.authorization.k8s.io/my-custom-role created ``` @@ -285,7 +285,7 @@ rolebinding.rbac.authorization.k8s.io/my-custom-rolebinding-two created Now, create Postgres CRD `minute-postgres` using the existing service account name `my-custom-serviceaccount` in the `spec.podTemplate.spec.serviceAccountName` field. ```console -$ kubectl apply -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/postgres/custom-rbac/pg-custom-db-two.yaml +$ kubectl apply -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/postgres/custom-rbac/pg-custom-db-two.yaml postgres.kubedb.com/quick-postgres created ``` diff --git a/docs/guides/postgres/custom-versions/_index.md b/docs/guides/postgres/custom-versions/_index.md index d9963a6e13..f5cc25679a 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.12.0: + docs_v0.13.0-rc.0: identifier: pg-custom-versions-postgres name: Custom Versions parent: pg-postgres-guides weight: 45 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/postgres/custom-versions/setup.md b/docs/guides/postgres/custom-versions/setup.md index d0d4cffc5d..32aff3fb82 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.12.0: + docs_v0.13.0-rc.0: identifier: pg-custom-versions-setup-postgres name: Overview parent: pg-custom-versions-postgres weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- > New to KubeDB? Please start [here](/docs/concepts/README.md). diff --git a/docs/guides/postgres/initialization/_index.md b/docs/guides/postgres/initialization/_index.md index 5ad83b7902..e9000f5368 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.12.0: + docs_v0.13.0-rc.0: identifier: pg-initialization-postgres name: Initialization parent: pg-postgres-guides weight: 30 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/postgres/initialization/point-in-time-recovery.md b/docs/guides/postgres/initialization/point-in-time-recovery.md index 7595d3f063..a632694c04 100644 --- a/docs/guides/postgres/initialization/point-in-time-recovery.md +++ b/docs/guides/postgres/initialization/point-in-time-recovery.md @@ -1,12 +1,12 @@ --- title: Point-in-Time Recovery (PITR) | Postgres menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: pg-pitr name: Point-in-Time Recovery parent: pg-initialization-postgres weight: 20 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -32,7 +32,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/docs/tree/0.12.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Overview @@ -99,7 +99,7 @@ We have configured the above database to continuously backup WAL logs into `kube Let's create the database we have shown above, ```console -$ kubectl apply -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/postgres/initialization/pitr/pg-original.yaml +$ kubectl apply -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/postgres/initialization/pitr/pg-original.yaml postgres.kubedb.com/pg-original created ``` @@ -220,7 +220,7 @@ spec: Let's create the above Postgres crd, ```console -$ kubectl apply -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/postgres/initialization/pitr/pitr-1.yaml +$ kubectl apply -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/postgres/initialization/pitr/pitr-1.yaml postgres.kubedb.com/pitr-1 created ``` @@ -287,7 +287,7 @@ spec: Let's create the above Postgres crd, ```console -$ kubectl apply -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/postgres/initialization/pitr/pitr-2.yaml +$ kubectl apply -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/postgres/initialization/pitr/pitr-2.yaml postgres.kubedb.com/pitr-2 created ``` diff --git a/docs/guides/postgres/initialization/replay_from_azure.md b/docs/guides/postgres/initialization/replay_from_azure.md index 6cc19accd7..3663c5791a 100644 --- a/docs/guides/postgres/initialization/replay_from_azure.md +++ b/docs/guides/postgres/initialization/replay_from_azure.md @@ -1,12 +1,12 @@ --- title: Initialize Postgres from Azure menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: pg-wal-source-initialization-azure name: From WAL(Azure) parent: pg-initialization-postgres weight: 35 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- @@ -90,7 +90,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/docs/tree/0.12.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Create Postgres with WAL source @@ -141,7 +141,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://github.com/kubedb/docs/raw/0.12.0/docs/examples/postgres/initialization/replay-postgres-azure.yaml +$ kubectl create -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/postgres/initialization/replay-postgres-azure.yaml postgres.kubedb.com/replay-postgres created ``` diff --git a/docs/guides/postgres/initialization/replay_from_gcs.md b/docs/guides/postgres/initialization/replay_from_gcs.md index 7ec5402617..039c665ad4 100644 --- a/docs/guides/postgres/initialization/replay_from_gcs.md +++ b/docs/guides/postgres/initialization/replay_from_gcs.md @@ -1,12 +1,12 @@ --- title: Initialize Postgres from GCS menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: pg-wal-source-initialization-gcs name: From WAL(GCS) parent: pg-initialization-postgres weight: 40 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- @@ -90,7 +90,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/docs/tree/0.12.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Create Postgres with WAL source @@ -141,7 +141,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://github.com/kubedb/docs/raw/0.12.0/docs/examples/postgres/initialization/replay-postgres-gcs.yaml +$ kubectl create -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/postgres/initialization/replay-postgres-gcs.yaml postgres.kubedb.com/replay-postgres created ``` diff --git a/docs/guides/postgres/initialization/replay_from_local.md b/docs/guides/postgres/initialization/replay_from_local.md index 18c75a3418..921114371d 100644 --- a/docs/guides/postgres/initialization/replay_from_local.md +++ b/docs/guides/postgres/initialization/replay_from_local.md @@ -1,12 +1,12 @@ --- title: Initialize Postgres from WAL (Local Storage) menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: pg-wal-source-initialization-local name: From WAL(Local Storage) parent: pg-initialization-postgres weight: 50 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- @@ -90,7 +90,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/docs/tree/0.12.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Create Postgres with WAL source @@ -141,7 +141,7 @@ Here, Now, let's create the Postgres object that's YAML has shown above, ```console -$ kubectl create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/postgres/initialization/replay-postgres-local.yaml +$ kubectl create -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/postgres/initialization/replay-postgres-local.yaml postgres.kubedb.com/replay-postgres created ``` diff --git a/docs/guides/postgres/initialization/replay_from_minio.md b/docs/guides/postgres/initialization/replay_from_minio.md index 10fdc4c0c8..2641b02ecf 100644 --- a/docs/guides/postgres/initialization/replay_from_minio.md +++ b/docs/guides/postgres/initialization/replay_from_minio.md @@ -1,12 +1,12 @@ --- title: Initialize Postgres from MinIO menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: pg-wal-source-initialization-minio name: From WAL(MiniIO) parent: pg-initialization-postgres weight: 55 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- @@ -91,7 +91,7 @@ postgres=# \q Now, we are ready to proceed to the rest of the tutorial. -> Note: YAML files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/docs/tree/0.12.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Create Postgres with WAL source @@ -148,7 +148,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://github.com/kubedb/docs/raw/0.12.0/docs/examples/postgres/initialization/replay-postgres-minio.yaml +$ kubectl create -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/postgres/initialization/replay-postgres-minio.yaml postgres.kubedb.com/replay-postgres created ``` diff --git a/docs/guides/postgres/initialization/replay_from_s3.md b/docs/guides/postgres/initialization/replay_from_s3.md index 26fc1845fe..1427399063 100644 --- a/docs/guides/postgres/initialization/replay_from_s3.md +++ b/docs/guides/postgres/initialization/replay_from_s3.md @@ -1,12 +1,12 @@ --- title: Initialize Postgres from S3 menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: pg-wal-source-initialization-s3 name: From WAL(S3) parent: pg-initialization-postgres weight: 30 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- @@ -90,7 +90,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/docs/tree/0.12.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Create Postgres with WAL source @@ -141,7 +141,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://github.com/kubedb/docs/raw/0.12.0/docs/examples/postgres/initialization/replay-postgres-s3.yaml +$ kubectl create -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/postgres/initialization/replay-postgres-s3.yaml postgres.kubedb.com/replay-postgres created ``` diff --git a/docs/guides/postgres/initialization/replay_from_swift.md b/docs/guides/postgres/initialization/replay_from_swift.md index 50ea619e78..b527cc646e 100644 --- a/docs/guides/postgres/initialization/replay_from_swift.md +++ b/docs/guides/postgres/initialization/replay_from_swift.md @@ -1,12 +1,12 @@ --- title: Initialize Postgres from Swift menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: pg-wal-source-initialization-swift name: From WAL(Swift) parent: pg-initialization-postgres weight: 45 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- @@ -90,7 +90,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/docs/tree/0.12.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Create Postgres with WAL source @@ -141,7 +141,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://github.com/kubedb/docs/raw/0.12.0/docs/examples/postgres/initialization/replay-postgres-swift.yaml +$ kubectl create -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/postgres/initialization/replay-postgres-swift.yaml postgres.kubedb.com/replay-postgres created ``` diff --git a/docs/guides/postgres/initialization/script_source.md b/docs/guides/postgres/initialization/script_source.md index 0d5db54f22..3407b02ef9 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.12.0: + docs_v0.13.0-rc.0: identifier: pg-script-source-initialization name: Using Script parent: pg-initialization-postgres weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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/docs/tree/0.12.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## 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://github.com/kubedb/docs/raw/0.12.0/docs/examples/postgres/initialization/script-postgres.yaml +$ kubectl create -f https://github.com/kubedb/docs/raw/v0.13.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 6752266ef4..b0f25ce1d3 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.12.0: + docs_v0.13.0-rc.0: identifier: pg-snapshot-source-initialization name: From Snapshot parent: pg-initialization-postgres weight: 15 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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/docs/tree/0.12.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## 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://github.com/kubedb/docs/raw/0.12.0/docs/examples/postgres/initialization/recovered-postgres.yaml +$ kubedb create -f https://github.com/kubedb/docs/raw/v0.13.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 d35e912505..e059d61b7d 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.12.0: + docs_v0.13.0-rc.0: identifier: pg-wal-source-initialization name: From WAL parent: pg-initialization-postgres weight: 25 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- diff --git a/docs/guides/postgres/monitoring/_index.md b/docs/guides/postgres/monitoring/_index.md index baa08a44d3..2076247ced 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.12.0: + docs_v0.13.0-rc.0: identifier: pg-monitoring-postgres name: Monitoring parent: pg-postgres-guides weight: 50 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/postgres/monitoring/using-builtin-prometheus.md b/docs/guides/postgres/monitoring/using-builtin-prometheus.md index 49fe5f9d3d..e4a01963e9 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.12.0: + docs_v0.13.0-rc.0: identifier: pg-using-builtin-prometheus-monitoring name: Builtin Prometheus Discovery parent: pg-monitoring-postgres weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- @@ -36,7 +36,7 @@ This tutorial will show you how to monitor PostgreSQL database using builtin [Pr namespace/demo created ``` -> Note: YAML files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/docs/tree/0.12.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Deploy PostgreSQL with Monitoring Enabled @@ -69,7 +69,7 @@ Here, Let's create the PostgreSQL crd we have shown above. ```console -$ kubectl apply -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/postgres/monitoring/builtin-prom-postgres.yaml +$ kubectl apply -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/postgres/monitoring/builtin-prom-postgres.yaml postgres.kubedb.com/builtin-prom-postgres created ``` @@ -275,7 +275,7 @@ data: Let's create above `ConfigMap`, ```console -$ kubectl apply -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/monitoring/builtin-prometheus/prom-config.yaml +$ kubectl apply -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/monitoring/builtin-prometheus/prom-config.yaml configmap/prometheus-config created ``` diff --git a/docs/guides/postgres/monitoring/using-coreos-prometheus-operator.md b/docs/guides/postgres/monitoring/using-coreos-prometheus-operator.md index 13521e2d43..685789508b 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.12.0: + docs_v0.13.0-rc.0: identifier: pg-using-coreos-prometheus-operator-monitoring name: Coreos Prometheus Operator parent: pg-monitoring-postgres weight: 15 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -35,7 +35,7 @@ CoreOS [prometheus-operator](https://github.com/coreos/prometheus-operator) prov - If you already don't have a Prometheus server running, deploy one following tutorial from [here](https://github.com/appscode/third-party-tools/blob/master/monitoring/prometheus/coreos-operator/README.md#deploy-prometheus-server). -> Note: YAML files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/docs/tree/0.12.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Find out required labels for ServiceMonitor @@ -124,7 +124,7 @@ Here, Let's create the PostgreSQL object that we have shown above, ```console -$ kubectl create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/postgres/monitoring/coreos-prom-postgres.yaml +$ kubectl create -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/postgres/monitoring/coreos-prom-postgres.yaml postgresql.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 bf127e4ce4..bbb7beeeca 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.12.0: + docs_v0.13.0-rc.0: identifier: pg-private-registry-postgres name: Private Registry parent: pg-postgres-guides weight: 35 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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 a1b2511a5a..c0341b5933 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.12.0: + docs_v0.13.0-rc.0: identifier: pg-using-private-registry-private-registry name: Quickstart parent: pg-private-registry-postgres weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- @@ -27,7 +27,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/docs/tree/0.12.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Prepare Private Docker Registry @@ -145,7 +145,7 @@ spec: Now run the command to create this Postgres object: ```console -$ kubectl create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/postgres/private-registry/pvt-reg-postgres.yaml +$ kubectl create -f https://github.com/kubedb/docs/raw/v0.13.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 5cd52e96a2..4e1d83aef7 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.12.0: + docs_v0.13.0-rc.0: identifier: pg-quickstart-postgres name: Quickstart parent: pg-postgres-guides weight: 15 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/postgres/quickstart/quickstart.md b/docs/guides/postgres/quickstart/quickstart.md index 63b29c57d9..1f64d42d9a 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.12.0: + docs_v0.13.0-rc.0: identifier: pg-quickstart-quickstart name: Overview parent: pg-quickstart-postgres weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -32,7 +32,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/docs/tree/0.12.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). >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). @@ -43,7 +43,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://github.com/kubedb/docs/raw/0.12.0/docs/examples/postgres/quickstart/pgadmin.yaml +$ kubectl create -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/postgres/quickstart/pgadmin.yaml deployment.apps/pgadmin created service/pgadmin created @@ -138,7 +138,7 @@ Here, Let's create Postgres crd, ```console -$ kubectl create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/postgres/quickstart/quick-postgres.yaml +$ kubectl create -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/postgres/quickstart/quick-postgres.yaml postgres.kubedb.com/quick-postgres created ``` @@ -427,7 +427,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://github.com/kubedb/docs/raw/0.12.0/docs/examples/postgres/quickstart/quick-postgres.yaml +$ kubectl create -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/postgres/quickstart/quick-postgres.yaml postgres.kubedb.com/quick-postgres created ``` diff --git a/docs/guides/postgres/quickstart/rbac.md b/docs/guides/postgres/quickstart/rbac.md index 494852ba50..138598fdf1 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.12.0: + docs_v0.13.0-rc.0: identifier: pg-rbac-quickstart name: RBAC parent: pg-quickstart-postgres weight: 15 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -37,7 +37,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/docs/tree/0.12.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Create a PostgreSQL database @@ -65,7 +65,7 @@ spec: Create above Postgres object with following command ```console -$ kubectl create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/postgres/quickstart/quick-postgres.yaml +$ kubectl create -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/postgres/quickstart/quick-postgres.yaml postgres.kubedb.com/quick-postgres created ``` diff --git a/docs/guides/postgres/snapshot/_index.md b/docs/guides/postgres/snapshot/_index.md index 7d73334d7b..0bc692f932 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.12.0: + docs_v0.13.0-rc.0: identifier: pg-snapshot-postgres name: Snapshotting parent: pg-postgres-guides weight: 25 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/postgres/snapshot/archiving_to_azure.md b/docs/guides/postgres/snapshot/archiving_to_azure.md index 9d594ca057..2df0b414fd 100644 --- a/docs/guides/postgres/snapshot/archiving_to_azure.md +++ b/docs/guides/postgres/snapshot/archiving_to_azure.md @@ -1,12 +1,12 @@ --- title: Continuous Archiving to Azure menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: pg-continuous-archiving-azure name: WAL Archiving to Azure parent: pg-snapshot-postgres weight: 30 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- @@ -22,7 +22,7 @@ At first, you need to have a Kubernetes cluster, and the kubectl command-line to Now, install KubeDB cli on your workstation and KubeDB operator in your cluster following the steps [here](/docs/setup/install.md). -> Note: YAML files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/docs/tree/0.12.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). To keep things isolated, this tutorial uses a separate namespace called `demo` throughout this tutorial. @@ -114,7 +114,7 @@ To configure Azure backend, following parameters are available: Now create this Postgres object with continuous archiving support. ```console -$ kubectl create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/postgres/snapshot/wal-postgres-azure.yaml +$ kubectl create -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/postgres/snapshot/wal-postgres-azure.yaml postgres.kubedb.com/wal-postgres created ``` diff --git a/docs/guides/postgres/snapshot/archiving_to_gcs.md b/docs/guides/postgres/snapshot/archiving_to_gcs.md index 5d065248f3..2fb928347c 100644 --- a/docs/guides/postgres/snapshot/archiving_to_gcs.md +++ b/docs/guides/postgres/snapshot/archiving_to_gcs.md @@ -1,12 +1,12 @@ --- title: Continuous Archiving to GCS menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: pg-continuous-archiving-gcs name: WAL Archiving to GCS parent: pg-snapshot-postgres weight: 35 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- @@ -22,7 +22,7 @@ At first, you need to have a Kubernetes cluster, and the kubectl command-line to Now, install KubeDB cli on your workstation and KubeDB operator in your cluster following the steps [here](/docs/setup/install.md). -> Note: YAML files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/docs/tree/0.12.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). To keep things isolated, this tutorial uses a separate namespace called `demo` throughout this tutorial. @@ -114,7 +114,7 @@ To configure GCS backend, following parameters are available: Now create this Postgres object with continuous archiving support. ```console -$ kubectl create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/postgres/snapshot/wal-postgres-gcs.yaml +$ kubectl create -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/postgres/snapshot/wal-postgres-gcs.yaml postgres.kubedb.com/wal-postgres created ``` diff --git a/docs/guides/postgres/snapshot/archiving_to_local.md b/docs/guides/postgres/snapshot/archiving_to_local.md index 53cb395816..8d59a1dbcc 100644 --- a/docs/guides/postgres/snapshot/archiving_to_local.md +++ b/docs/guides/postgres/snapshot/archiving_to_local.md @@ -1,12 +1,12 @@ --- title: Continuous Archiving to Local Storage menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: pg-continuous-archiving-local name: WAL Archiving to Local Storage parent: pg-snapshot-postgres weight: 45 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- @@ -22,7 +22,7 @@ At first, you need to have a Kubernetes cluster, and the kubectl command-line to Now, install KubeDB cli on your workstation and KubeDB operator in your cluster following the steps [here](/docs/setup/install.md). -> Note: YAML files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/docs/tree/0.12.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). To keep things isolated, this tutorial uses a separate namespace called `demo` throughout this tutorial. @@ -142,7 +142,7 @@ To configure Local backend, following parameters are available: Now create this Postgres object with continuous archiving support. ```console -$ kubectl create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/postgres/snapshot/wal-postgres-local.yaml +$ kubectl create -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/postgres/snapshot/wal-postgres-local.yaml postgres.kubedb.com/wal-postgres created ``` diff --git a/docs/guides/postgres/snapshot/archiving_to_minio.md b/docs/guides/postgres/snapshot/archiving_to_minio.md index bd36c1aaef..edfc3d882b 100644 --- a/docs/guides/postgres/snapshot/archiving_to_minio.md +++ b/docs/guides/postgres/snapshot/archiving_to_minio.md @@ -1,12 +1,12 @@ --- title: Continuous Archiving to MinIO menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: pg-continuous-archiving-minio name: WAL Archiving to MinIO parent: pg-snapshot-postgres weight: 50 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- @@ -22,7 +22,7 @@ At first, you need to have a Kubernetes cluster, and the kubectl command-line to Now, install KubeDB cli on your workstation and KubeDB operator in your cluster following the steps [here](/docs/setup/install.md). -> Note: YAML files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/docs/tree/0.12.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). To keep things isolated, this tutorial uses a separate namespace called `demo` throughout this tutorial. @@ -154,7 +154,7 @@ To configure s3 backend, following parameters are available: Now create this Postgres object with continuous archiving support. ```console -$ kubectl create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/postgres/snapshot/wal-postgres-minio.yaml +$ kubectl create -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/postgres/snapshot/wal-postgres-minio.yaml postgres.kubedb.com/wal-postgres created ``` diff --git a/docs/guides/postgres/snapshot/archiving_to_s3.md b/docs/guides/postgres/snapshot/archiving_to_s3.md index 6610342672..76a1d5a2c8 100644 --- a/docs/guides/postgres/snapshot/archiving_to_s3.md +++ b/docs/guides/postgres/snapshot/archiving_to_s3.md @@ -1,12 +1,12 @@ --- title: Continuous Archiving to S3 menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: pg-continuous-archiving-s3 name: WAL Archiving to S3 parent: pg-snapshot-postgres weight: 25 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- @@ -22,7 +22,7 @@ At first, you need to have a Kubernetes cluster, and the kubectl command-line to Now, install KubeDB cli on your workstation and KubeDB operator in your cluster following the steps [here](/docs/setup/install.md). -> Note: YAML files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/docs/tree/0.12.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). To keep things isolated, this tutorial uses a separate namespace called `demo` throughout this tutorial. @@ -115,7 +115,7 @@ To configure s3 backend, following parameters are available: Now create this Postgres object with continuous archiving support. ```console -$ kubectl create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/postgres/snapshot/wal-postgres-s3.yaml +$ kubectl create -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/postgres/snapshot/wal-postgres-s3.yaml postgres.kubedb.com/wal-postgres created ``` diff --git a/docs/guides/postgres/snapshot/archiving_to_swift.md b/docs/guides/postgres/snapshot/archiving_to_swift.md index 9f9ed6d9a3..0cf06bd47c 100644 --- a/docs/guides/postgres/snapshot/archiving_to_swift.md +++ b/docs/guides/postgres/snapshot/archiving_to_swift.md @@ -1,12 +1,12 @@ --- title: Continuous Archiving to Swift menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: pg-continuous-archiving-swift name: WAL Archiving to Swift parent: pg-snapshot-postgres weight: 40 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- @@ -22,7 +22,7 @@ At first, you need to have a Kubernetes cluster, and the kubectl command-line to Now, install KubeDB cli on your workstation and KubeDB operator in your cluster following the steps [here](/docs/setup/install.md). -> Note: YAML files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/docs/tree/0.12.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). To keep things isolated, this tutorial uses a separate namespace called `demo` throughout this tutorial. @@ -142,7 +142,7 @@ To configure Swift backend, following parameters are available: Now create this Postgres object with continuous archiving support. ```console -$ kubectl create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/postgres/snapshot/wal-postgres-swift.yaml +$ kubectl create -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/postgres/snapshot/wal-postgres-swift.yaml postgres.kubedb.com/wal-postgres created ``` diff --git a/docs/guides/postgres/snapshot/continuous_archiving.md b/docs/guides/postgres/snapshot/continuous_archiving.md index c27c79a82f..adaab68cb2 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.12.0: + docs_v0.13.0-rc.0: identifier: pg-continuous-archiving-snapshot name: WAL Archiving parent: pg-snapshot-postgres weight: 20 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- diff --git a/docs/guides/postgres/snapshot/instant_backup.md b/docs/guides/postgres/snapshot/instant_backup.md index 4f0174ae0f..9064732c07 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.12.0: + docs_v0.13.0-rc.0: identifier: pg-instant-backup-snapshot name: Instant Backup parent: pg-snapshot-postgres weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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/docs/tree/0.12.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## 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://github.com/kubedb/docs/raw/0.12.0/docs/examples/postgres/snapshot/instant-snapshot.yaml +$ kubectl create -f https://github.com/kubedb/docs/raw/v0.13.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 d7db9ad4b0..42c10e44bf 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.12.0: + docs_v0.13.0-rc.0: identifier: pg-scheduled-backup-snapshot name: Scheduled Backup parent: pg-snapshot-postgres weight: 15 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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. @@ -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/docs/tree/0.12.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/postgres) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Create Postgres with BackupSchedule @@ -89,7 +89,7 @@ Here, Let's create a Postgres crd with backupSchedule, ```console -$ kubectl create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/postgres/snapshot/scheduled-pg.yaml +$ kubectl create -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/postgres/snapshot/scheduled-pg.yaml postgres.kubedb.com/scheduled-pg created ``` diff --git a/docs/guides/postgres/upgrading/_index.md b/docs/guides/postgres/upgrading/_index.md index 9460f98227..f3f9c5818f 100644 --- a/docs/guides/postgres/upgrading/_index.md +++ b/docs/guides/postgres/upgrading/_index.md @@ -1,10 +1,10 @@ --- title: Upgrading PostgreSQL menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: pg-upgrading-postgres name: Upgrading PostgreSQL parent: pg-postgres-guides weight: 60 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/postgres/upgrading/manual.md b/docs/guides/postgres/upgrading/manual.md index bc0fe0f60b..67c45371f0 100644 --- a/docs/guides/postgres/upgrading/manual.md +++ b/docs/guides/postgres/upgrading/manual.md @@ -1,12 +1,12 @@ --- title: Upgrading Operator menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: pg-upgrade-manual name: Manual parent: pg-upgrading-postgres weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- > New to KubeDB? Please start [here](/docs/concepts/README.md). diff --git a/docs/guides/redis/README.md b/docs/guides/redis/README.md index 26fb507f4e..221aaa5a2f 100644 --- a/docs/guides/redis/README.md +++ b/docs/guides/redis/README.md @@ -1,16 +1,16 @@ --- title: Redis menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: rd-readme-redis name: Redis parent: rd-redis-guides weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides -url: /docs/0.12.0/guides/redis/ +url: /docs/v0.13.0-rc.0/guides/redis/ aliases: - - /docs/0.12.0/guides/redis/README/ + - /docs/v0.13.0-rc.0/guides/redis/README/ --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -30,16 +30,12 @@ aliases: | Builtin Prometheus Discovery | ✓ | | Using CoreOS Prometheus Operator | ✓ | -
- ## Life Cycle of a Redis Object

  lifecycle

-
- ## Supported Redis Versions | KubeDB Version | Redis:4.0.6 | Redis:5.0.3 | @@ -50,26 +46,27 @@ aliases: | 0.10.0 | ✓ | ✓ | | 0.11.0 | ✓ | ✓ | | 0.12.0 | ✓ | ✓ | +| v0.13.0-rc.0 | ✓ | ✓ | ## Supported RedisVersion CRD Here, ✓ means supported and ✗ means deprecated. -| NAME | VERSION | KubeDB: 0.9.0 | KubeDB: 0.10.0 | KubeDB: 0.11.0 | KubeDB: 0.12.0 | -| :------: | :------: | :-----------: | :------------: | :------------: | :------------: | -| 4 | 4 | ✗ | ✗ | ✗ | ✗ | -| 4-v1 | 4 | ✓ | ✗ | ✗ | ✗ | -| 4.0 | 4.0 | ✗ | ✗ | ✗ | ✗ | -| 4.0-v1 | 4.0 | ✓ | ✓ | ✓ | ✓ | -| 4.0-v2 | 4.0 | ✗ | ✓ | ✓ | ✓ | -| 4.0.6 | 4.0.6 | ✗ | ✗ | ✗ | ✗ | -| 4.0.6-v1 | 4.0.6 | ✓ | ✓ | ✓ | ✓ | -| 4.0.6-v2 | 4.0.6 | ✗ | ✓ | ✓ | ✓ | -| 4.0.11 | 4.0.11 | ✗ | ✓ | ✓ | ✓ | -| 5.0 | 5.0 | ✓ | ✓ | ✓ | ✓ | -| 5.0-v1 | 5.0-v1 | ✗ | ✗ | ✓ | ✓ | -| 5.0.3 | 5.0.3 | ✓ | ✓ | ✓ | ✓ | -| 5.0.3-v1 | 5.0.3-v1 | ✗ | ✗ | ✓ | ✓ | +| NAME | VERSION | KubeDB: 0.9.0 | KubeDB: 0.10.0 | KubeDB: 0.11.0 | KubeDB: 0.12.0 | KubeDB: v0.13.0-rc.0 | +| :------: | :------: | :-----------: | :------------: | :------------: | :------------: | :------------------: | +| 4 | 4 | ✗ | ✗ | ✗ | ✗ | ✗ | +| 4-v1 | 4 | ✓ | ✗ | ✗ | ✗ | ✗ | +| 4.0 | 4.0 | ✗ | ✗ | ✗ | ✗ | ✗ | +| 4.0-v1 | 4.0 | ✓ | ✓ | ✓ | ✓ | ✓ | +| 4.0-v2 | 4.0 | ✗ | ✓ | ✓ | ✓ | ✓ | +| 4.0.6 | 4.0.6 | ✗ | ✗ | ✗ | ✗ | ✗ | +| 4.0.6-v1 | 4.0.6 | ✓ | ✓ | ✓ | ✓ | ✓ | +| 4.0.6-v2 | 4.0.6 | ✗ | ✓ | ✓ | ✓ | ✓ | +| 4.0.11 | 4.0.11 | ✗ | ✓ | ✓ | ✓ | ✓ | +| 5.0 | 5.0 | ✓ | ✓ | ✓ | ✓ | ✓ | +| 5.0-v1 | 5.0-v1 | ✗ | ✗ | ✓ | ✓ | ✓ | +| 5.0.3 | 5.0.3 | ✓ | ✓ | ✓ | ✓ | ✓ | +| 5.0.3-v1 | 5.0.3-v1 | ✗ | ✗ | ✓ | ✓ | ✓ | ## User Guide diff --git a/docs/guides/redis/_index.md b/docs/guides/redis/_index.md index 296002dcb8..e383ad7a90 100644 --- a/docs/guides/redis/_index.md +++ b/docs/guides/redis/_index.md @@ -1,10 +1,10 @@ --- title: Redis menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: rd-redis-guides name: Redis parent: guides weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/redis/cli/_index.md b/docs/guides/redis/cli/_index.md index 2399e7ec2a..298e3597ec 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.12.0: + docs_v0.13.0-rc.0: identifier: rd-cli-redis name: Cli parent: rd-redis-guides weight: 45 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/redis/cli/cli.md b/docs/guides/redis/cli/cli.md index 95870b04d6..be03fa8483 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.12.0: + docs_v0.13.0-rc.0: identifier: rd-cli-cli name: Quickstart parent: rd-cli-redis weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- diff --git a/docs/guides/redis/clustering/_index.md b/docs/guides/redis/clustering/_index.md index 17cbd13058..188941bab9 100755 --- a/docs/guides/redis/clustering/_index.md +++ b/docs/guides/redis/clustering/_index.md @@ -1,10 +1,10 @@ --- title: Redis Clustering menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: rd-clustering-redis name: Clustering parent: rd-redis-guides weight: 17 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/redis/clustering/overview.md b/docs/guides/redis/clustering/overview.md index 8ff326aa11..691e4e9e8c 100644 --- a/docs/guides/redis/clustering/overview.md +++ b/docs/guides/redis/clustering/overview.md @@ -1,12 +1,12 @@ --- title: Redis Cluster Overview menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: rd-clustering-overview name: Overview parent: rd-clustering-redis weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- diff --git a/docs/guides/redis/clustering/redis-cluster.md b/docs/guides/redis/clustering/redis-cluster.md index 68493f9017..b7bc1980f1 100644 --- a/docs/guides/redis/clustering/redis-cluster.md +++ b/docs/guides/redis/clustering/redis-cluster.md @@ -1,12 +1,12 @@ --- title: Redis Cluster Guide menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: rd-cluster name: Clustering Guide parent: rd-clustering-redis weight: 15 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- @@ -33,7 +33,7 @@ Before proceeding: namespace/demo created ``` -> Note: The yaml files used in this tutorial are stored in [docs/examples/redis](https://github.com/kubedb/docs/tree/0.12.0/docs/examples/redis) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: The yaml files used in this tutorial are stored in [docs/examples/redis](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/redis) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Deploy Redis Cluster @@ -67,7 +67,7 @@ spec: ``` ```console -$ kubedb create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/redis/clustering/demo-1.yaml +$ kubedb create -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/redis/clustering/demo-1.yaml redis.kubedb.com/redis-cluster created ``` diff --git a/docs/guides/redis/custom-config/_index.md b/docs/guides/redis/custom-config/_index.md index 095bf46c65..06758eb3ec 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.12.0: + docs_v0.13.0-rc.0: identifier: rd-custom-config name: Custom Configuration parent: rd-redis-guides weight: 50 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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 72b3ea5518..857975f0e4 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.12.0: + docs_v0.13.0-rc.0: identifier: rd-custom-config-quickstart name: Quickstart parent: rd-custom-config weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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/docs/tree/0.12.0/docs/examples/redis) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/redis](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/redis) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Overview @@ -84,7 +84,7 @@ metadata: Now, create Redis crd specifying `spec.configSource` field. ```console -$ kubectl apply -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/redis/custom-config/redis-custom.yaml +$ kubectl apply -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/redis/custom-config/redis-custom.yaml redis.kubedb.com "custom-redis" created ``` diff --git a/docs/guides/redis/custom-rbac/_index.md b/docs/guides/redis/custom-rbac/_index.md index 9877832681..9f3c576c7c 100755 --- a/docs/guides/redis/custom-rbac/_index.md +++ b/docs/guides/redis/custom-rbac/_index.md @@ -1,10 +1,10 @@ --- title: Run Redis with Custom RBAC resources menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: rd-custom-rbac name: Custom RBAC parent: rd-redis-guides weight: 85 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/redis/custom-rbac/using-custom-rbac.md b/docs/guides/redis/custom-rbac/using-custom-rbac.md index 6cced2713c..a59bb1ca7f 100644 --- a/docs/guides/redis/custom-rbac/using-custom-rbac.md +++ b/docs/guides/redis/custom-rbac/using-custom-rbac.md @@ -1,12 +1,12 @@ --- title: Run Redis with Custom RBAC resources menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: rd-custom-rbac-quickstart name: Custom RBAC parent: rd-custom-rbac weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- @@ -29,7 +29,7 @@ $ kubectl create ns demo namespace/demo created ``` -> Note: YAML files used in this tutorial are stored in [docs/examples/redis](https://github.com/kubedb/docs/tree/0.12.0/docs/examples/redis) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/redis](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/redis) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Overview @@ -70,7 +70,7 @@ secrets: Now, we need to create a role that has necessary access permissions for the Redis instance named `quick-redis`. ```console -$ kubectl apply -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/redis/custom-rbac/rd-custom-role.yaml +$ kubectl apply -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/redis/custom-rbac/rd-custom-role.yaml role.rbac.authorization.k8s.io/my-custom-role created ``` @@ -129,7 +129,7 @@ subjects: Now, create a Redis crd specifying `spec.podTemplate.spec.serviceAccountName` field to `my-custom-serviceaccount`. ```console -$ kubectl apply -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/redis/custom-rbac/rd-custom-db.yaml +$ kubectl apply -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/redis/custom-rbac/rd-custom-db.yaml redis.kubedb.com/quick-redis created ``` @@ -190,7 +190,7 @@ An existing service account can be reused in another Redis instance. No new acce Now, create Redis crd `minute-redis` using the existing service account name `my-custom-serviceaccount` in the `spec.podTemplate.spec.serviceAccountName` field. ```console -$ kubectl apply -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/redis/custom-rbac/rd-custom-db-two.yaml +$ kubectl apply -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/redis/custom-rbac/rd-custom-db-two.yaml redis.kubedb.com/quick-redis created ``` diff --git a/docs/guides/redis/monitoring/_index.md b/docs/guides/redis/monitoring/_index.md index d621e81d0a..b25c1b38c1 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.12.0: + docs_v0.13.0-rc.0: identifier: rd-monitoring-redis name: Monitoring parent: rd-redis-guides weight: 25 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/redis/monitoring/using-builtin-prometheus.md b/docs/guides/redis/monitoring/using-builtin-prometheus.md index 2d8f0a2930..0b1b3dd39f 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.12.0: + docs_v0.13.0-rc.0: identifier: rd-using-builtin-prometheus-monitoring name: Builtin Prometheus Discovery parent: rd-monitoring-redis weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- @@ -36,7 +36,7 @@ This tutorial will show you how to monitor Redis server using builtin [Prometheu namespace/demo created ``` -> Note: YAML files used in this tutorial are stored in [docs/examples/redis](https://github.com/kubedb/docs/tree/0.12.0/docs/examples/redis) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/redis](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/redis) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Deploy Redis with Monitoring Enabled @@ -69,7 +69,7 @@ Here, Let's create the Redis crd we have shown above. ```console -$ kubectl apply -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/redis/monitoring/builtin-prom-redis.yaml +$ kubectl apply -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/redis/monitoring/builtin-prom-redis.yaml redis.kubedb.com/builtin-prom-redis created ``` @@ -274,7 +274,7 @@ data: Let's create above `ConfigMap`, ```console -$ kubectl apply -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/monitoring/builtin-prometheus/prom-config.yaml +$ kubectl apply -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/monitoring/builtin-prometheus/prom-config.yaml configmap/prometheus-config created ``` diff --git a/docs/guides/redis/monitoring/using-coreos-prometheus-operator.md b/docs/guides/redis/monitoring/using-coreos-prometheus-operator.md index 399813cb13..20b486842f 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.12.0: + docs_v0.13.0-rc.0: identifier: rd-using-coreos-prometheus-operator-monitoring name: Coreos Prometheus Operator parent: rd-monitoring-redis weight: 15 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- > New to KubeDB? Please start [here](/docs/concepts/README.md). @@ -35,7 +35,7 @@ CoreOS [prometheus-operator](https://github.com/coreos/prometheus-operator) prov - If you already don't have a Prometheus server running, deploy one following tutorial from [here](https://github.com/appscode/third-party-tools/blob/master/monitoring/prometheus/coreos-operator/README.md#deploy-prometheus-server). -> Note: YAML files used in this tutorial are stored in [docs/examples/redis](https://github.com/kubedb/docs/tree/0.12.0/docs/examples/redis) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: YAML files used in this tutorial are stored in [docs/examples/redis](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples/redis) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Find out required labels for ServiceMonitor @@ -124,7 +124,7 @@ Here, Let's create the Redis object that we have shown above, ```console -$ kubectl create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/redis/monitoring/coreos-prom-redis.yaml +$ kubectl create -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/redis/monitoring/coreos-prom-redis.yaml redis.kubedb.com/coreos-prom-redis created ``` diff --git a/docs/guides/redis/private-registry/_index.md b/docs/guides/redis/private-registry/_index.md index 598018ea29..9fabd530f8 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.12.0: + docs_v0.13.0-rc.0: identifier: rd-private-registry-redis name: Private Registry parent: rd-redis-guides weight: 20 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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 15acc48cbc..6fad708d4f 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.12.0: + docs_v0.13.0-rc.0: identifier: rd-using-private-registry-private-registry name: Quickstart parent: rd-private-registry-redis weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: guides --- @@ -126,7 +126,7 @@ spec: Now run the command to deploy this `Redis` object: ```console -$ kubedb create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/redis/private-registry/demo-2.yaml +$ kubedb create -f https://github.com/kubedb/docs/raw/v0.13.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 20d8334c9b..04d72b2305 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.12.0: + docs_v0.13.0-rc.0: identifier: rd-quickstart-redis name: Quickstart parent: rd-redis-guides weight: 15 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/guides/redis/quickstart/quickstart.md b/docs/guides/redis/quickstart/quickstart.md index 4314d41b0f..7ba7069648 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.12.0: + docs_v0.13.0-rc.0: identifier: rd-quickstart-quickstart name: Overview parent: rd-quickstart-redis weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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 Redis server. demo Active 10s ``` -> Note: The yaml files used in this tutorial are stored in [docs/examples](https://github.com/kubedb/docs/tree/0.12.0/docs/examples) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). +> Note: The yaml files used in this tutorial are stored in [docs/examples](https://github.com/kubedb/docs/tree/v0.13.0-rc.0/docs/examples) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs). ## Find Available RedisVersion @@ -91,7 +91,7 @@ spec: ``` ```console -$ kubedb create -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/redis/quickstart/demo-1.yaml +$ kubedb create -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/redis/quickstart/demo-1.yaml redis.kubedb.com/redis-quickstart created ``` @@ -335,7 +335,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://github.com/kubedb/docs/raw/0.12.0/docs/examples/redis/quickstart/demo-1.yaml +$ kubedb create -f https://github.com/kubedb/docs/raw/v0.13.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 09a920e124..b9cee29326 100644 --- a/docs/reference/_index.md +++ b/docs/reference/_index.md @@ -2,9 +2,9 @@ title: Reference description: KubeDB CLI Reference menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: reference name: Reference weight: 1000 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/reference/kubedb.md b/docs/reference/kubedb.md index 274fb1e676..037ce707df 100644 --- a/docs/reference/kubedb.md +++ b/docs/reference/kubedb.md @@ -1,16 +1,16 @@ --- title: Kubedb menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: kubedb name: Kubedb parent: reference weight: 0 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: reference aliases: - - /docs/0.12.0/reference/ + - /docs/v0.13.0-rc.0/reference/ --- ## kubedb diff --git a/docs/reference/kubedb_api-resources.md b/docs/reference/kubedb_api-resources.md index c665403a42..05f3375fc4 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.12.0: + docs_v0.13.0-rc.0: identifier: kubedb-api-resources name: Kubedb Api-Resources parent: reference -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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 4547c05823..a50c13e92e 100644 --- a/docs/reference/kubedb_create.md +++ b/docs/reference/kubedb_create.md @@ -1,11 +1,11 @@ --- title: Kubedb Create menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: kubedb-create name: Kubedb Create parent: reference -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: reference --- ## kubedb create diff --git a/docs/reference/kubedb_delete.md b/docs/reference/kubedb_delete.md index 10062a0fb0..3b7f223fdd 100644 --- a/docs/reference/kubedb_delete.md +++ b/docs/reference/kubedb_delete.md @@ -1,11 +1,11 @@ --- title: Kubedb Delete menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: kubedb-delete name: Kubedb Delete parent: reference -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: reference --- ## kubedb delete diff --git a/docs/reference/kubedb_describe.md b/docs/reference/kubedb_describe.md index 17bf645a24..c942bb7370 100644 --- a/docs/reference/kubedb_describe.md +++ b/docs/reference/kubedb_describe.md @@ -1,11 +1,11 @@ --- title: Kubedb Describe menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: kubedb-describe name: Kubedb Describe parent: reference -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: reference --- ## kubedb describe diff --git a/docs/reference/kubedb_edit.md b/docs/reference/kubedb_edit.md index f057a72077..ca6210b2a7 100644 --- a/docs/reference/kubedb_edit.md +++ b/docs/reference/kubedb_edit.md @@ -1,11 +1,11 @@ --- title: Kubedb Edit menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: kubedb-edit name: Kubedb Edit parent: reference -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: reference --- ## kubedb edit diff --git a/docs/reference/kubedb_get.md b/docs/reference/kubedb_get.md index 0fa0f92bfd..9a402bf0bf 100644 --- a/docs/reference/kubedb_get.md +++ b/docs/reference/kubedb_get.md @@ -1,11 +1,11 @@ --- title: Kubedb Get menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: kubedb-get name: Kubedb Get parent: reference -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: reference --- ## kubedb get diff --git a/docs/reference/kubedb_version.md b/docs/reference/kubedb_version.md index edb89883a0..c71545e0ba 100644 --- a/docs/reference/kubedb_version.md +++ b/docs/reference/kubedb_version.md @@ -1,11 +1,11 @@ --- title: Kubedb Version menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: kubedb-version name: Kubedb Version parent: reference -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: reference --- ## kubedb version diff --git a/docs/setup/README.md b/docs/setup/README.md index d2bc899f7f..ea82b12bb6 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.12.0: + docs_v0.13.0-rc.0: identifier: setup-readme name: Readme parent: setup weight: -1 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: setup -url: /docs/0.12.0/setup/ +url: /docs/v0.13.0-rc.0/setup/ aliases: - - /docs/0.12.0/setup/README/ + - /docs/v0.13.0-rc.0/setup/README/ --- # Setup diff --git a/docs/setup/_index.md b/docs/setup/_index.md index f7508ba3b0..e1c29b82ee 100644 --- a/docs/setup/_index.md +++ b/docs/setup/_index.md @@ -1,9 +1,9 @@ --- title: Setup | KubeDB menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: setup name: Setup weight: 30 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/setup/developer-guide/_index.md b/docs/setup/developer-guide/_index.md index de1be4bf8c..6dde37ae7b 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.12.0: + docs_v0.13.0-rc.0: identifier: developer-guide name: Developer Guide parent: setup weight: 50 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/setup/developer-guide/overview.md b/docs/setup/developer-guide/overview.md index 43d8f64649..594968c671 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.12.0: + docs_v0.13.0-rc.0: identifier: developer-guide-readme name: Overview parent: developer-guide weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: setup aliases: - - /docs/0.12.0/setup/developer-guide/ + - /docs/v0.13.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 35b12b1221..fb8c460fa3 100644 --- a/docs/setup/developer-guide/release.md +++ b/docs/setup/developer-guide/release.md @@ -1,12 +1,12 @@ --- title: Release menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: developer-guide-release name: Release Process parent: developer-guide weight: 20 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: setup --- diff --git a/docs/setup/install.md b/docs/setup/install.md index 8bf9a5b0ca..8928c5cb14 100644 --- a/docs/setup/install.md +++ b/docs/setup/install.md @@ -1,12 +1,12 @@ --- title: Install menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: install-kubedb name: Install parent: setup weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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://github.com/kubedb/installer/raw/0.12.0/deploy/kubedb.sh | bash +$ curl -fsSL https://github.com/kubedb/installer/raw/v0.13.0-rc.0/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/installer/tree/0.12.0/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/installer/tree/v0.13.0-rc.0/deploy) folder. You can see the full list of flags available to installer using `-h` flag. ```console -$ curl -fsSL https://github.com/kubedb/installer/raw/0.12.0/deploy/kubedb.sh | bash -s -- -h +$ curl -fsSL https://github.com/kubedb/installer/raw/v0.13.0-rc.0/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://github.com/kubedb/installer/raw/0.12.0/deploy/kubedb.sh \ +$ curl -fsSL https://github.com/kubedb/installer/raw/v0.13.0-rc.0/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://github.com/kubedb/installer/raw/0.12.0/deploy/kubedb.sh \ +$ curl -fsSL https://github.com/kubedb/installer/raw/v0.13.0-rc.0/deploy/kubedb.sh \ | bash -s -- --namespace=kubedb [--run-on-master] [--rbac] ``` @@ -97,14 +97,14 @@ To pass the address of your private registry and optionally a image pull secret ```console $ kubectl create namespace kubedb -$ curl -fsSL https://github.com/kubedb/installer/raw/0.12.0/deploy/kubedb.sh \ +$ curl -fsSL https://github.com/kubedb/installer/raw/v0.13.0-rc.0/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://github.com/kubedb/installer/raw/0.12.0/deploy/kubedb.sh \ +$ curl -fsSL https://github.com/kubedb/installer/raw/v0.13.0-rc.0/deploy/kubedb.sh \ | bash -s -- --enable-validating-webhook=false --enable-mutating-webhook=false [--rbac] ``` @@ -113,7 +113,7 @@ KubeDB 0.11.0 or later releases can use status sub resource for CustomResourceDe KubeDB 0.11.0 or later installs a catalog of database versions. To disable this pass the `--install-catalog=false` flag. ```console -$ curl -fsSL https://github.com/kubedb/installer/raw/0.12.0/deploy/kubedb.sh \ +$ curl -fsSL https://github.com/kubedb/installer/raw/v0.13.0-rc.0/deploy/kubedb.sh \ | bash -s -- --install-catalog=false [--rbac] ``` @@ -122,18 +122,18 @@ $ curl -fsSL https://github.com/kubedb/installer/raw/0.12.0/deploy/kubedb.sh \ ## Using Helm -KubeDB can be installed via [Helm](https://helm.sh/) using the [chart](https://github.com/kubedb/installer/tree/0.12.0/chart/kubedb) from [AppsCode Charts Repository](https://github.com/appscode/charts). To install the chart with the release name `my-release`: +KubeDB can be installed via [Helm](https://helm.sh/) using the [chart](https://github.com/kubedb/installer/tree/v0.13.0-rc.0/chart/kubedb) from [AppsCode Charts Repository](https://github.com/appscode/charts). To install the chart with the release name `my-release`: ```console $ 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.12.0 0.12.0 KubeDB by AppsCode - Production ready databases on Kubern... -appscode/kubedb-catalog 0.12.0 0.12.0 KubeDB Catalog by AppsCode - Catalog for database versions +appscode/kubedb v0.13.0-rc.0 v0.13.0-rc.0 KubeDB by AppsCode - Production ready databases on Kubern... +appscode/kubedb-catalog v0.13.0-rc.0 v0.13.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.12.0 \ +$ helm install appscode/kubedb --name kubedb-operator --version v0.13.0-rc.0 \ --namespace kube-system # Step 2: wait until crds are registered @@ -157,15 +157,15 @@ 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.12.0 \ +$ helm install appscode/kubedb-catalog --name kubedb-catalog --version v0.13.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.12.0 \ +$ helm upgrade kubedb-catalog appscode/kubedb-catalog --version v0.13.0-rc.0 \ --namespace kube-system ``` -To see the detailed configuration options, visit [here](https://github.com/kubedb/installer/tree/0.12.0/chart/kubedb). +To see the detailed configuration options, visit [here](https://github.com/kubedb/installer/tree/v0.13.0-rc.0/chart/kubedb). @@ -206,12 +206,12 @@ KubeDB provides a CLI to work with database objects. Download pre-built binaries ```console # Linux amd 64-bit -wget -O kubedb https://github.com/kubedb/cli/releases/download/0.12.0/kubedb-linux-amd64 \ +wget -O kubedb https://github.com/kubedb/cli/releases/download/v0.13.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.12.0/kubedb-darwin-amd64 \ +wget -O kubedb https://github.com/kubedb/cli/releases/download/v0.13.0-rc.0/kubedb-darwin-amd64 \ && chmod +x kubedb \ && sudo mv kubedb /usr/local/bin/ ``` diff --git a/docs/setup/monitoring/_index.md b/docs/setup/monitoring/_index.md index 0b25ba2037..c25720dab2 100644 --- a/docs/setup/monitoring/_index.md +++ b/docs/setup/monitoring/_index.md @@ -1,10 +1,10 @@ --- title: Monitoring KubeDB operator menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: operator-monitoring name: Operator Monitoring parent: setup weight: 40 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 --- diff --git a/docs/setup/monitoring/builtin.md b/docs/setup/monitoring/builtin.md index 6bdb997604..30efe109f1 100644 --- a/docs/setup/monitoring/builtin.md +++ b/docs/setup/monitoring/builtin.md @@ -1,15 +1,15 @@ --- title: Monitoring KubeDB Operator with builtin Prometheus menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: operator-monitoring-builtin name: Builtin Prometheus parent: operator-monitoring weight: 20 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: setup aliases: - - /docs/0.12.0/setup/operator-monitoring/ + - /docs/v0.13.0-rc.0/setup/operator-monitoring/ --- # Monitoring KubeDB Operator with builtin Prometheus @@ -38,7 +38,7 @@ Let's install KubeDB with operator monitoring enabled. **Script:** ```console -$ curl -fsSL https://github.com/kubedb/installer/raw/0.12.0/deploy/kubedb.sh | bash -s -- \ +$ curl -fsSL https://github.com/kubedb/installer/raw/v0.13.0-rc.0/deploy/kubedb.sh | bash -s -- \ --monitoring-enable=true \ --monitoring-agent=prometheus.io/builtin \ --prometheus-namespace=monitoring \ @@ -48,7 +48,7 @@ $ curl -fsSL https://github.com/kubedb/installer/raw/0.12.0/deploy/kubedb.sh | b **Helm:** ```console -$ helm install appscode/kubedb --name kubedb-operator --version 0.12.0 --namespace kube-system \ +$ helm install appscode/kubedb --name kubedb-operator --version v0.13.0-rc.0 --namespace kube-system \ --set monitoring.enabled=true \ --set monitoring.agent=prometheus.io/builtin \ --set monitoring.prometheus.namespace=monitoring \ @@ -296,7 +296,7 @@ data: Let's create the ConfigMap we have shown above, ```console -$ kubectl apply -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/monitoring/operator/prom-config.yaml +$ kubectl apply -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/monitoring/operator/prom-config.yaml configmap/kubedb-operator-prom-config created ``` @@ -372,7 +372,7 @@ Notice that, we have mounted `kubedb-operator-apiserver-cert` secret as a volume Now, let's create the deployment, ```console -$ kubectl apply -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/monitoring/operator/prom-deploy.yaml +$ kubectl apply -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/monitoring/operator/prom-deploy.yaml deployment.apps/prometheus created ``` diff --git a/docs/setup/monitoring/coreos.md b/docs/setup/monitoring/coreos.md index 0a14048016..9a88342403 100644 --- a/docs/setup/monitoring/coreos.md +++ b/docs/setup/monitoring/coreos.md @@ -1,15 +1,15 @@ --- title: Monitoring KubeDB Operator Using CoreOS Prometheus Operator menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: operator-monitoring-coreos name: Prometheus Operator parent: operator-monitoring weight: 30 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: setup aliases: - - /docs/0.12.0/setup/operator-monitoring/ + - /docs/v0.13.0-rc.0/setup/operator-monitoring/ --- # Monitoring KubeDB Operator Using CoreOS Prometheus Operator @@ -38,7 +38,7 @@ Let's install KubeDB operator with monitoring enabled. **Script:** ```console -$ curl -fsSL https://github.com/kubedb/installer/raw/0.12.0/deploy/kubedb.sh | bash -s -- \ +$ curl -fsSL https://github.com/kubedb/installer/raw/v0.13.0-rc.0/deploy/kubedb.sh | bash -s -- \ --monitoring-enable=true \ --monitoring-agent=prometheus.io/coreos-operator \ --prometheus-namespace=monitoring \ @@ -48,7 +48,7 @@ $ curl -fsSL https://github.com/kubedb/installer/raw/0.12.0/deploy/kubedb.sh | b **Helm:** ```console -$ helm install appscode/kubedb --name kubedb-operator --version 0.12.0 --namespace kube-system \ +$ helm install appscode/kubedb --name kubedb-operator --version v0.13.0-rc.0 --namespace kube-system \ --set monitoring.enabled=true \ --set monitoring.agent=prometheus.io/coreos-operator \ --set monitoring.prometheus.namespace=monitoring \ @@ -184,7 +184,7 @@ Here, `spec.serviceMonitorSelector` is used to select the `ServiceMonitor` crd t Let's create the `Prometheus` object we have shown above, ```console -$ kubectl apply -f https://github.com/kubedb/docs/raw/0.12.0/docs/examples/monitoring/operator/prometheus.yaml +$ kubectl apply -f https://github.com/kubedb/docs/raw/v0.13.0-rc.0/docs/examples/monitoring/operator/prometheus.yaml prometheus.monitoring.coreos.com/prometheus created ``` diff --git a/docs/setup/monitoring/overview.md b/docs/setup/monitoring/overview.md index 38f8113ebe..ed97793043 100644 --- a/docs/setup/monitoring/overview.md +++ b/docs/setup/monitoring/overview.md @@ -1,15 +1,15 @@ --- title: Monitoring KubeDB Operator menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: operator-monitoring-overview name: Overview parent: operator-monitoring weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: setup aliases: - - /docs/0.12.0/setup/operator-monitoring/ + - /docs/v0.13.0-rc.0/setup/operator-monitoring/ --- # Monitoring KubeDB Operator @@ -102,7 +102,7 @@ You have to provides these flags while installing or upgrading or updating KubeD **Helm:** ```console -$ helm install appscode/kubedb --name kubedb-operator --version 0.12.0 --namespace kube-system \ +$ helm install appscode/kubedb --name kubedb-operator --version v0.13.0-rc.0 --namespace kube-system \ --set monitoring.enabled=true \ --set monitoring.agent=prometheus.io/coreos-operator \ --set monitoring.prometheus.namespace=monitoring \ @@ -112,7 +112,7 @@ $ helm install appscode/kubedb --name kubedb-operator --version 0.12.0 --namespa **Script:** ```console -$ curl -fsSL https://github.com/kubedb/installer/raw/0.12.0/deploy/kubedb.sh | bash -s -- \ +$ curl -fsSL https://github.com/kubedb/installer/raw/v0.13.0-rc.0/deploy/kubedb.sh | bash -s -- \ --monitoring-enable=true \ --monitoring-agent=prometheus.io/coreos-operator \ --prometheus-namespace=monitoring \ diff --git a/docs/setup/uninstall.md b/docs/setup/uninstall.md index 44abce24ec..57583db7ec 100644 --- a/docs/setup/uninstall.md +++ b/docs/setup/uninstall.md @@ -1,12 +1,12 @@ --- title: KubeDB Uninstall menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: uninstall-kubedb name: Uninstall parent: setup weight: 20 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.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://github.com/kubedb/installer/raw/0.12.0/deploy/kubedb.sh \ +$ curl -fsSL https://github.com/kubedb/installer/raw/v0.13.0-rc.0/deploy/kubedb.sh \ | bash -s -- --uninstall [--namespace=NAMESPACE] + kubectl delete deployment -l app=kubedb -n kube-system diff --git a/docs/status.md b/docs/status.md index 3156119681..2c9036393e 100644 --- a/docs/status.md +++ b/docs/status.md @@ -2,16 +2,16 @@ title: Project Status | KubeDB description: KubeDB Project Status menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: roadmap-cli name: Status parent: welcome weight: 15 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: welcome -url: /docs/0.12.0/welcome/status/ +url: /docs/v0.13.0-rc.0/welcome/status/ aliases: - - /docs/0.12.0/status/ + - /docs/v0.13.0-rc.0/status/ --- # Project Status diff --git a/docs/support.md b/docs/support.md index 95c5a70dbc..eaba971d0a 100644 --- a/docs/support.md +++ b/docs/support.md @@ -2,16 +2,16 @@ title: Support | KubeDB description: Support menu: - docs_0.12.0: + docs_v0.13.0-rc.0: identifier: support-cli name: Support parent: welcome weight: 10 -menu_name: docs_0.12.0 +menu_name: docs_v0.13.0-rc.0 section_menu_id: welcome -url: /docs/0.12.0/welcome/support/ +url: /docs/v0.13.0-rc.0/welcome/support/ aliases: - - /docs/0.12.0/support/ + - /docs/v0.13.0-rc.0/support/ --- # Support