mirror of
https://github.com/bigchaindb/bigchaindb.git
synced 2024-10-13 13:34:05 +00:00
Addressing comments and removing *-tm* or *-tmt* references
This commit is contained in:
muawiakh
parent
6052043a03
commit
b68c0ccbc0
@ -3,7 +3,7 @@
|
||||
Kubernetes Template: Deploying a BigchainDB network
|
||||
===================================================
|
||||
|
||||
This page describes how to deploy a BigchainDB + Tendermint network.
|
||||
This page describes how to deploy a static BigchainDB + Tendermint network.
|
||||
|
||||
If you want to deploy a stand-alone BigchainDB node in a BigchainDB cluster,
|
||||
or a stand-alone BigchainDB node,
|
||||
@ -48,7 +48,7 @@ cluster is using.
|
||||
`github repository <https://github.com/bigchaindb/bigchaindb/milestones>`_.
|
||||
|
||||
|
||||
.. _pre-reqs-bdb-network-tmt:
|
||||
.. _pre-reqs-bdb-network:
|
||||
|
||||
Prerequisites
|
||||
-------------
|
||||
@ -57,7 +57,7 @@ The deployment methodology is similar to one covered with :doc:`node-on-kubernet
|
||||
we need to tweak some configurations depending on your choice of deployment.
|
||||
|
||||
The operator needs to follow some consistent naming convention for all the components
|
||||
covered :ref:`here <things-each-node-operator-must-do-tmt>`.
|
||||
covered :ref:`here <things-each-node-operator-must-do>`.
|
||||
|
||||
Lets assume we are deploying a 4 node cluster, your naming conventions could look like this:
|
||||
|
||||
@ -109,24 +109,24 @@ Lets assume we are deploying a 4 node cluster, your naming conventions could loo
|
||||
Edit config.yaml and secret.yaml
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
Make N(number of nodes) copies of ``configuration/config-map-tm.yaml`` and ``configuration/secret-tm.yaml``.
|
||||
Make N(number of nodes) copies of ``configuration/config-map.yaml`` and ``configuration/secret.yaml``.
|
||||
|
||||
.. code:: text
|
||||
|
||||
# For config-map-tm.yaml
|
||||
# For config-map.yaml
|
||||
config-map-node-1.yaml
|
||||
config-map-node-2.yaml
|
||||
config-map-node-3.yaml
|
||||
config-map-node-4.yaml
|
||||
|
||||
# For secret-tm.yaml
|
||||
# For secret.yaml
|
||||
secret-node-1.yaml
|
||||
secret-node-2.yaml
|
||||
secret-node-3.yaml
|
||||
secret-node-4.yaml
|
||||
|
||||
Edit the data values as described in :doc:`this document <node-config-map-and-secrets>`, based
|
||||
on the naming convention described :ref:`above <pre-reqs-bdb-network-tmt>`.
|
||||
on the naming convention described :ref:`above <pre-reqs-bdb-network>`.
|
||||
|
||||
**Only for single site deployments**: Since all the configuration files use the
|
||||
same ConfigMap and Secret Keys i.e.
|
||||
@ -136,7 +136,7 @@ same ConfigMap and Secret Keys i.e.
|
||||
will overwrite the configuration of the previously deployed one.
|
||||
We want each node to have its own unique configurations.
|
||||
One way to go about it is that, using the
|
||||
:ref:`naming convention above <pre-reqs-bdb-network-tmt>` we edit the ConfigMap and Secret keys.
|
||||
:ref:`naming convention above <pre-reqs-bdb-network>` we edit the ConfigMap and Secret keys.
|
||||
|
||||
.. code:: text
|
||||
|
||||
@ -208,7 +208,7 @@ Deploy all your configuration maps and secrets.
|
||||
*-node-4-dep.yaml
|
||||
|
||||
|
||||
.. _single-site-network-tmt:
|
||||
.. _single-site-network:
|
||||
|
||||
Single Site: Single Azure Kubernetes Cluster
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
@ -380,12 +380,12 @@ nodes, we need to replicate the :doc:`deployment steps for each node <node-on-ku
|
||||
N being the number of participants in the network.
|
||||
|
||||
The operator needs to follow a consistent naming convention which has :ref:`already
|
||||
discussed in this document <pre-reqs-bdb-network-tmt>`.
|
||||
discussed in this document <pre-reqs-bdb-network>`.
|
||||
|
||||
.. note::
|
||||
|
||||
Assuming we are using independent Kubernetes clusters, the ConfigMap and Secret Keys
|
||||
do not need to be updated unlike :ref:`single-site-network-tmt`, and we also do not
|
||||
do not need to be updated unlike :ref:`single-site-network`, and we also do not
|
||||
need to update corresponding ConfigMap/Secret imports in the Kubernetes components.
|
||||
|
||||
|
||||
@ -393,19 +393,19 @@ Deploy Kubernetes Services
|
||||
--------------------------
|
||||
|
||||
Deploy the following services for each node by following the naming convention
|
||||
described :ref:`above <pre-reqs-bdb-network-tmt>`:
|
||||
described :ref:`above <pre-reqs-bdb-network>`:
|
||||
|
||||
* :ref:`Start the NGINX Service <start-the-nginx-service-tmt>`.
|
||||
* :ref:`Start the NGINX Service <start-the-nginx-service>`.
|
||||
|
||||
* :ref:`Assign DNS Name to the NGINX Public IP <assign-dns-name-to-nginx-public-ip-tmt>`
|
||||
* :ref:`Assign DNS Name to the NGINX Public IP <assign-dns-name-to-nginx-public-ip>`
|
||||
|
||||
* :ref:`Start the MongoDB Kubernetes Service <start-the-mongodb-kubernetes-service-tmt>`.
|
||||
* :ref:`Start the MongoDB Kubernetes Service <start-the-mongodb-kubernetes-service>`.
|
||||
|
||||
* :ref:`Start the BigchainDB Kubernetes Service <start-the-bigchaindb-kubernetes-service-tmt>`.
|
||||
* :ref:`Start the BigchainDB Kubernetes Service <start-the-bigchaindb-kubernetes-service>`.
|
||||
|
||||
* :ref:`Start the OpenResty Kubernetes Service <start-the-openresty-kubernetes-service-tmt>`.
|
||||
* :ref:`Start the OpenResty Kubernetes Service <start-the-openresty-kubernetes-service>`.
|
||||
|
||||
* :ref:`Start the Tendermint Kubernetes Service <start-the-tendermint-kubernetes-service-tmt>`.
|
||||
* :ref:`Start the Tendermint Kubernetes Service <start-the-tendermint-kubernetes-service>`.
|
||||
|
||||
|
||||
Only for multi site deployments
|
||||
@ -439,7 +439,7 @@ We can do this in Kubernetes using a Kubernetes Service of ``type``
|
||||
|
||||
* Set ``spec.externalName`` to the FQDN mapped to NGINX Public IP of the cluster you are trying to connect to.
|
||||
For more information about the FQDN please refer to: :ref:`Assign DNS name to NGINX Public
|
||||
IP <assign-dns-name-to-nginx-public-ip-tmt>`.
|
||||
IP <assign-dns-name-to-nginx-public-ip>`.
|
||||
|
||||
.. note::
|
||||
This operation needs to be replicated ``n-1`` times per node for a ``n`` node cluster, with the respective FQDNs
|
||||
@ -449,47 +449,47 @@ We can do this in Kubernetes using a Kubernetes Service of ``type``
|
||||
touch with the system administrator/s of the other ``n-1`` clusters and
|
||||
share with them your instance name (``tendermint-instance-name`` in the ConfigMap)
|
||||
and the FQDN of the NGINX instance acting as Gateway(set in: :ref:`Assign DNS name to NGINX
|
||||
Public IP <assign-dns-name-to-nginx-public-ip-tmt>`).
|
||||
Public IP <assign-dns-name-to-nginx-public-ip>`).
|
||||
|
||||
|
||||
Start NGINX Kubernetes deployments
|
||||
----------------------------------
|
||||
|
||||
Start the NGINX deployment that serves as a Gateway for each node by following the
|
||||
naming convention described :ref:`above <pre-reqs-bdb-network-tmt>` and referring to the following instructions:
|
||||
naming convention described :ref:`above <pre-reqs-bdb-network>` and referring to the following instructions:
|
||||
|
||||
* :ref:`Start the NGINX Kubernetes Deployment <start-the-nginx-deployment-tmt>`.
|
||||
* :ref:`Start the NGINX Kubernetes Deployment <start-the-nginx-deployment>`.
|
||||
|
||||
|
||||
Deploy Kubernetes StorageClasses for MongoDB and Tendermint
|
||||
-----------------------------------------------------------
|
||||
|
||||
Deploy the following StorageClasses for each node by following the naming convention
|
||||
described :ref:`above <pre-reqs-bdb-network-tmt>`:
|
||||
described :ref:`above <pre-reqs-bdb-network>`:
|
||||
|
||||
* :ref:`Create Kubernetes Storage Classes for MongoDB <create-kubernetes-storage-class-mdb-tmt>`.
|
||||
* :ref:`Create Kubernetes Storage Classes for MongoDB <create-kubernetes-storage-class-mdb>`.
|
||||
|
||||
* :ref:`Create Kubernetes Storage Classes for Tendermint <create-kubernetes-storage-class-tmt>`.
|
||||
* :ref:`Create Kubernetes Storage Classes for Tendermint <create-kubernetes-storage-class>`.
|
||||
|
||||
|
||||
Deploy Kubernetes PersistentVolumeClaims for MongoDB and Tendermint
|
||||
--------------------------------------------------------------------
|
||||
|
||||
Deploy the following services for each node by following the naming convention
|
||||
described :ref:`above <pre-reqs-bdb-network-tmt>`:
|
||||
described :ref:`above <pre-reqs-bdb-network>`:
|
||||
|
||||
* :ref:`Create Kubernetes Persistent Volume Claims for MongoDB <create-kubernetes-persistent-volume-claim-mdb-tmt>`.
|
||||
* :ref:`Create Kubernetes Persistent Volume Claims for MongoDB <create-kubernetes-persistent-volume-claim-mdb>`.
|
||||
|
||||
* :ref:`Create Kubernetes Persistent Volume Claims for Tendermint <create-kubernetes-persistent-volume-claim-tmt>`
|
||||
* :ref:`Create Kubernetes Persistent Volume Claims for Tendermint <create-kubernetes-persistent-volume-claim>`
|
||||
|
||||
|
||||
Deploy MongoDB Kubernetes StatefulSet
|
||||
--------------------------------------
|
||||
|
||||
Deploy the MongoDB StatefulSet (standalone MongoDB) for each node by following the naming convention
|
||||
described :ref:`above <pre-reqs-bdb-network-tmt>`: and referring to the following section:
|
||||
described :ref:`above <pre-reqs-bdb-network>`: and referring to the following section:
|
||||
|
||||
* :ref:`Start a Kubernetes StatefulSet for MongoDB <start-kubernetes-stateful-set-mongodb-tmt>`.
|
||||
* :ref:`Start a Kubernetes StatefulSet for MongoDB <start-kubernetes-stateful-set-mongodb>`.
|
||||
|
||||
|
||||
Configure Users and Access Control for MongoDB
|
||||
@ -498,43 +498,43 @@ Configure Users and Access Control for MongoDB
|
||||
Configure users and access control for each MongoDB instance
|
||||
in the network by referring to the following section:
|
||||
|
||||
* :ref:`Configure Users and Access Control for MongoDB <configure-users-and-access-control-mongodb-tmt>`.
|
||||
* :ref:`Configure Users and Access Control for MongoDB <configure-users-and-access-control-mongodb>`.
|
||||
|
||||
|
||||
Deploy Tendermint Kubernetes StatefulSet
|
||||
----------------------------------------
|
||||
|
||||
Deploy the Tendermint Stateful for each node by following the
|
||||
naming convention described :ref:`above <pre-reqs-bdb-network-tmt>` and referring to the following instructions:
|
||||
naming convention described :ref:`above <pre-reqs-bdb-network>` and referring to the following instructions:
|
||||
|
||||
* :ref:`create-kubernetes-stateful-set-tmt`.
|
||||
* :ref:`create-kubernetes-stateful-set`.
|
||||
|
||||
|
||||
Start Kubernetes Deployment for MongoDB Monitoring Agent
|
||||
---------------------------------------------------------
|
||||
|
||||
Start the MongoDB monitoring agent Kubernetes deployment for each node by following the
|
||||
naming convention described :ref:`above <pre-reqs-bdb-network-tmt>` and referring to the following instructions:
|
||||
naming convention described :ref:`above <pre-reqs-bdb-network>` and referring to the following instructions:
|
||||
|
||||
* :ref:`Start a Kubernetes StatefulSet for Tendermint <start-kubernetes-deployment-for-mdb-mon-agent-tmt>`.
|
||||
* :ref:`Start a Kubernetes StatefulSet for Tendermint <start-kubernetes-deployment-for-mdb-mon-agent>`.
|
||||
|
||||
|
||||
Start Kubernetes Deployment for BigchainDB
|
||||
------------------------------------------
|
||||
|
||||
Start the BigchainDB Kubernetes deployment for each node by following the
|
||||
naming convention described :ref:`above <pre-reqs-bdb-network-tmt>` and referring to the following instructions:
|
||||
naming convention described :ref:`above <pre-reqs-bdb-network>` and referring to the following instructions:
|
||||
|
||||
* :ref:`Start a Kubernetes Deployment for BigchainDB <start-kubernetes-deployment-bdb-tmt>`.
|
||||
* :ref:`Start a Kubernetes Deployment for BigchainDB <start-kubernetes-deployment-bdb>`.
|
||||
|
||||
|
||||
Start Kubernetes Deployment for OpenResty
|
||||
------------------------------------------
|
||||
|
||||
Start the OpenResty Kubernetes deployment for each node by following the
|
||||
naming convention described :ref:`above <pre-reqs-bdb-network-tmt>` and referring to the following instructions:
|
||||
naming convention described :ref:`above <pre-reqs-bdb-network>` and referring to the following instructions:
|
||||
|
||||
* :ref:` Start a Kubernetes Deployment for OpenResty <start-kubernetes-deployment-openresty-tmt>`.
|
||||
* :ref:`Start a Kubernetes Deployment for OpenResty <start-kubernetes-deployment-openresty>`.
|
||||
|
||||
|
||||
Verify and Test
|
||||
@ -542,5 +542,5 @@ Verify and Test
|
||||
|
||||
Verify and test your setup by referring to the following instructions:
|
||||
|
||||
* :ref:`Verify the BigchainDB Node Setup <verify-and-test-bdb-tmt>`.
|
||||
* :ref:`Verify the BigchainDB Node Setup <verify-and-test-bdb>`.
|
||||
|
||||
|
||||
@ -11,7 +11,7 @@ and ``secret.yaml`` (a set of Secrets).
|
||||
They are stored in the Kubernetes cluster's key-value store (etcd).
|
||||
|
||||
Make sure you did all the things listed in the section titled
|
||||
:ref:`things-each-node-operator-must-do-tmt`
|
||||
:ref:`things-each-node-operator-must-do`
|
||||
(including generation of all the SSL certificates needed
|
||||
for MongoDB auth).
|
||||
|
||||
@ -35,7 +35,7 @@ vars.cluster-fqdn
|
||||
~~~~~~~~~~~~~~~~~
|
||||
|
||||
The ``cluster-fqdn`` field specifies the domain you would have
|
||||
:ref:`registered before <register-a-domain-and-get-an-ssl-certificate-for-it-tmt>`.
|
||||
:ref:`registered before <register-a-domain-and-get-an-ssl-certificate-for-it>`.
|
||||
|
||||
|
||||
vars.cluster-frontend-port
|
||||
|
||||
@ -3,13 +3,12 @@
|
||||
Kubernetes Template: Deploy a Single BigchainDB Node
|
||||
====================================================
|
||||
|
||||
This page describes how to deploy a stand-alone BigchainDB + Tendermint node,
|
||||
or a static network of BigchainDB + Tendermint nodes.
|
||||
This page describes how to deploy a stand-alone BigchainDB + Tendermint node
|
||||
using `Kubernetes <https://kubernetes.io/>`_.
|
||||
It assumes you already have a running Kubernetes cluster.
|
||||
|
||||
Below, we refer to many files by their directory and filename,
|
||||
such as ``configuration/config-map-tm.yaml``. Those files are files in the
|
||||
such as ``configuration/config-map.yaml``. Those files are files in the
|
||||
`bigchaindb/bigchaindb repository on GitHub <https://github.com/bigchaindb/bigchaindb/>`_
|
||||
in the ``k8s/`` directory.
|
||||
Make sure you're getting those files from the appropriate Git branch on
|
||||
@ -108,7 +107,7 @@ Step 3: Configure Your BigchainDB Node
|
||||
See the page titled :ref:`how-to-configure-a-bigchaindb-node`.
|
||||
|
||||
|
||||
.. _start-the-nginx-service-tmt:
|
||||
.. _start-the-nginx-service:
|
||||
|
||||
Step 4: Start the NGINX Service
|
||||
-------------------------------
|
||||
@ -125,7 +124,7 @@ Step 4: Start the NGINX Service
|
||||
Step 4.1: Vanilla NGINX
|
||||
^^^^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
* This configuration is located in the file ``nginx-http/nginx-http-svc-tm.yaml``.
|
||||
* This configuration is located in the file ``nginx-http/nginx-http-svc.yaml``.
|
||||
|
||||
* Set the ``metadata.name`` and ``metadata.labels.name`` to the value
|
||||
set in ``ngx-instance-name`` in the ConfigMap above.
|
||||
@ -153,7 +152,7 @@ Step 4.1: Vanilla NGINX
|
||||
|
||||
.. code:: bash
|
||||
|
||||
$ kubectl --context k8s-bdb-test-cluster-0 apply -f nginx-http/nginx-http-svc-tm.yaml
|
||||
$ kubectl --context k8s-bdb-test-cluster-0 apply -f nginx-http/nginx-http-svc.yaml
|
||||
|
||||
|
||||
Step 4.2: NGINX with HTTPS
|
||||
@ -165,7 +164,7 @@ Step 4.2: NGINX with HTTPS
|
||||
* You should have already created the necessary Kubernetes Secrets in the previous
|
||||
step (i.e. ``https-certs``).
|
||||
|
||||
* This configuration is located in the file ``nginx-https/nginx-https-svc-tm.yaml``.
|
||||
* This configuration is located in the file ``nginx-https/nginx-https-svc.yaml``.
|
||||
|
||||
* Set the ``metadata.name`` and ``metadata.labels.name`` to the value
|
||||
set in ``ngx-instance-name`` in the ConfigMap above.
|
||||
@ -199,10 +198,10 @@ Step 4.2: NGINX with HTTPS
|
||||
|
||||
.. code:: bash
|
||||
|
||||
$ kubectl --context k8s-bdb-test-cluster-0 apply -f nginx-https/nginx-https-svc-tm.yaml
|
||||
$ kubectl --context k8s-bdb-test-cluster-0 apply -f nginx-https/nginx-https-svc.yaml
|
||||
|
||||
|
||||
.. _assign-dns-name-to-nginx-public-ip-tmt:
|
||||
.. _assign-dns-name-to-nginx-public-ip:
|
||||
|
||||
Step 5: Assign DNS Name to the NGINX Public IP
|
||||
----------------------------------------------
|
||||
@ -245,12 +244,12 @@ This will ensure that when you scale to different geographical zones, other Tend
|
||||
nodes in the network can reach this instance.
|
||||
|
||||
|
||||
.. _start-the-mongodb-kubernetes-service-tmt:
|
||||
.. _start-the-mongodb-kubernetes-service:
|
||||
|
||||
Step 6: Start the MongoDB Kubernetes Service
|
||||
--------------------------------------------
|
||||
|
||||
* This configuration is located in the file ``mongodb/mongo-svc-tm.yaml``.
|
||||
* This configuration is located in the file ``mongodb/mongo-svc.yaml``.
|
||||
|
||||
* Set the ``metadata.name`` and ``metadata.labels.name`` to the value
|
||||
set in ``mdb-instance-name`` in the ConfigMap above.
|
||||
@ -269,15 +268,15 @@ Step 6: Start the MongoDB Kubernetes Service
|
||||
|
||||
.. code:: bash
|
||||
|
||||
$ kubectl --context k8s-bdb-test-cluster-0 apply -f mongodb/mongo-svc-tm.yaml
|
||||
$ kubectl --context k8s-bdb-test-cluster-0 apply -f mongodb/mongo-svc.yaml
|
||||
|
||||
|
||||
.. _start-the-bigchaindb-kubernetes-service-tmt:
|
||||
.. _start-the-bigchaindb-kubernetes-service:
|
||||
|
||||
Step 7: Start the BigchainDB Kubernetes Service
|
||||
-----------------------------------------------
|
||||
|
||||
* This configuration is located in the file ``bigchaindb/bigchaindb-svc-tm.yaml``.
|
||||
* This configuration is located in the file ``bigchaindb/bigchaindb-svc.yaml``.
|
||||
|
||||
* Set the ``metadata.name`` and ``metadata.labels.name`` to the value
|
||||
set in ``bdb-instance-name`` in the ConfigMap above.
|
||||
@ -306,15 +305,15 @@ Step 7: Start the BigchainDB Kubernetes Service
|
||||
|
||||
.. code:: bash
|
||||
|
||||
$ kubectl --context k8s-bdb-test-cluster-0 apply -f bigchaindb/bigchaindb-svc-tm.yaml
|
||||
$ kubectl --context k8s-bdb-test-cluster-0 apply -f bigchaindb/bigchaindb-svc.yaml
|
||||
|
||||
|
||||
.. _start-the-openresty-kubernetes-service-tmt:
|
||||
.. _start-the-openresty-kubernetes-service:
|
||||
|
||||
Step 8: Start the OpenResty Kubernetes Service
|
||||
----------------------------------------------
|
||||
|
||||
* This configuration is located in the file ``nginx-openresty/nginx-openresty-svc-tm.yaml``.
|
||||
* This configuration is located in the file ``nginx-openresty/nginx-openresty-svc.yaml``.
|
||||
|
||||
* Set the ``metadata.name`` and ``metadata.labels.name`` to the value
|
||||
set in ``openresty-instance-name`` in the ConfigMap above.
|
||||
@ -328,10 +327,10 @@ Step 8: Start the OpenResty Kubernetes Service
|
||||
|
||||
.. code:: bash
|
||||
|
||||
$ kubectl --context k8s-bdb-test-cluster-0 apply -f nginx-openresty/nginx-openresty-svc-tm.yaml
|
||||
$ kubectl --context k8s-bdb-test-cluster-0 apply -f nginx-openresty/nginx-openresty-svc.yaml
|
||||
|
||||
|
||||
.. _start-the-tendermint-kubernetes-service-tmt:
|
||||
.. _start-the-tendermint-kubernetes-service:
|
||||
|
||||
Step 9: Start the Tendermint Kubernetes Service
|
||||
-----------------------------------------------
|
||||
@ -368,7 +367,7 @@ Step 9: Start the Tendermint Kubernetes Service
|
||||
$ kubectl --context k8s-bdb-test-cluster-0 apply -f tendermint/tendermint-svc.yaml
|
||||
|
||||
|
||||
.. _start-the-nginx-deployment-tmt:
|
||||
.. _start-the-nginx-deployment:
|
||||
|
||||
Step 10: Start the NGINX Kubernetes Deployment
|
||||
----------------------------------------------
|
||||
@ -385,7 +384,7 @@ Step 10: Start the NGINX Kubernetes Deployment
|
||||
Step 10.1: Vanilla NGINX
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
* This configuration is located in the file ``nginx-http/nginx-http-dep-tm.yaml``.
|
||||
* This configuration is located in the file ``nginx-http/nginx-http-dep.yaml``.
|
||||
|
||||
* Set the ``metadata.name`` and ``spec.template.metadata.labels.app``
|
||||
to the value set in ``ngx-instance-name`` in the ConfigMap followed by a
|
||||
@ -418,14 +417,14 @@ Step 10.1: Vanilla NGINX
|
||||
|
||||
.. code:: bash
|
||||
|
||||
$ kubectl --context k8s-bdb-test-cluster-0 apply -f nginx-http/nginx-http-dep-tm.yaml
|
||||
$ kubectl --context k8s-bdb-test-cluster-0 apply -f nginx-http/nginx-http-dep.yaml
|
||||
|
||||
|
||||
Step 10.2: NGINX with HTTPS
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
* This configuration is located in the file
|
||||
``nginx-https/nginx-https-dep-tm.yaml``.
|
||||
``nginx-https/nginx-https-dep.yaml``.
|
||||
|
||||
* Set the ``metadata.name`` and ``spec.template.metadata.labels.app``
|
||||
to the value set in ``ngx-instance-name`` in the ConfigMap followed by a
|
||||
@ -465,10 +464,10 @@ Step 10.2: NGINX with HTTPS
|
||||
|
||||
.. code:: bash
|
||||
|
||||
$ kubectl --context k8s-bdb-test-cluster-0 apply -f nginx-https/nginx-https-dep-tm.yaml
|
||||
$ kubectl --context k8s-bdb-test-cluster-0 apply -f nginx-https/nginx-https-dep.yaml
|
||||
|
||||
|
||||
.. _create-kubernetes-storage-class-mdb-tmt:
|
||||
.. _create-kubernetes-storage-class-mdb:
|
||||
|
||||
Step 11: Create Kubernetes Storage Classes for MongoDB
|
||||
------------------------------------------------------
|
||||
@ -539,7 +538,7 @@ Create the required storage classes using:
|
||||
You can check if it worked using ``kubectl get storageclasses``.
|
||||
|
||||
|
||||
.. _create-kubernetes-persistent-volume-claim-mdb-tmt:
|
||||
.. _create-kubernetes-persistent-volume-claim-mdb:
|
||||
|
||||
Step 12: Create Kubernetes Persistent Volume Claims for MongoDB
|
||||
---------------------------------------------------------------
|
||||
@ -594,12 +593,12 @@ but it should become "Bound" fairly quickly.
|
||||
For notes on recreating a private volume form a released Azure disk resource consult
|
||||
:doc:`the page about cluster troubleshooting <../production-deployment-template/troubleshoot>`.
|
||||
|
||||
.. _start-kubernetes-stateful-set-mongodb-tmt:
|
||||
.. _start-kubernetes-stateful-set-mongodb:
|
||||
|
||||
Step 13: Start a Kubernetes StatefulSet for MongoDB
|
||||
---------------------------------------------------
|
||||
|
||||
* This configuration is located in the file ``mongodb/mongo-ss-tm.yaml``.
|
||||
* This configuration is located in the file ``mongodb/mongo-ss.yaml``.
|
||||
|
||||
* Set the ``spec.serviceName`` to the value set in ``mdb-instance-name`` in
|
||||
the ConfigMap.
|
||||
@ -665,7 +664,7 @@ Step 13: Start a Kubernetes StatefulSet for MongoDB
|
||||
|
||||
.. code:: bash
|
||||
|
||||
$ kubectl --context k8s-bdb-test-cluster-0 apply -f mongodb/mongo-ss-tm.yaml
|
||||
$ kubectl --context k8s-bdb-test-cluster-0 apply -f mongodb/mongo-ss.yaml
|
||||
|
||||
* It might take up to 10 minutes for the disks, specified in the Persistent
|
||||
Volume Claims above, to be created and attached to the pod.
|
||||
@ -679,7 +678,7 @@ Step 13: Start a Kubernetes StatefulSet for MongoDB
|
||||
$ kubectl --context k8s-bdb-test-cluster-0 get pods -w
|
||||
|
||||
|
||||
.. _configure-users-and-access-control-mongodb-tmt:
|
||||
.. _configure-users-and-access-control-mongodb:
|
||||
|
||||
Step 14: Configure Users and Access Control for MongoDB
|
||||
-------------------------------------------------------
|
||||
@ -779,7 +778,7 @@ Step 14: Configure Users and Access Control for MongoDB
|
||||
} )
|
||||
|
||||
|
||||
.. _create-kubernetes-storage-class-tmt:
|
||||
.. _create-kubernetes-storage-class:
|
||||
|
||||
Step 15: Create Kubernetes Storage Classes for Tendermint
|
||||
----------------------------------------------------------
|
||||
@ -791,7 +790,7 @@ The Kubernetes template for configuration of Storage Class is located in the
|
||||
file ``tendermint/tendermint-sc.yaml``.
|
||||
|
||||
Details about how to create a Azure Storage account and how Kubernetes Storage Class works
|
||||
are already covered in this document: :ref:`create-kubernetes-storage-class-mdb-tmt`.
|
||||
are already covered in this document: :ref:`create-kubernetes-storage-class-mdb`.
|
||||
|
||||
Create the required storage classes using:
|
||||
|
||||
@ -802,7 +801,7 @@ Create the required storage classes using:
|
||||
|
||||
You can check if it worked using ``kubectl get storageclasses``.
|
||||
|
||||
.. _create-kubernetes-persistent-volume-claim-tmt:
|
||||
.. _create-kubernetes-persistent-volume-claim:
|
||||
|
||||
Step 16: Create Kubernetes Persistent Volume Claims for Tendermint
|
||||
------------------------------------------------------------------
|
||||
@ -814,7 +813,7 @@ This configuration is located in the file ``tendermint/tendermint-pvc.yaml``.
|
||||
|
||||
Details about Kubernetes Persistent Volumes, Persistent Volume Claims
|
||||
and how they work with Azure are already covered in this
|
||||
document: :ref:`create-kubernetes-persistent-volume-claim-mdb-tmt`.
|
||||
document: :ref:`create-kubernetes-persistent-volume-claim-mdb`.
|
||||
|
||||
Create the required Persistent Volume Claims using:
|
||||
|
||||
@ -829,7 +828,7 @@ You can check its status using:
|
||||
kubectl get pvc -w
|
||||
|
||||
|
||||
.. _create-kubernetes-stateful-set-tmt:
|
||||
.. _create-kubernetes-stateful-set:
|
||||
|
||||
Step 17: Start a Kubernetes StatefulSet for Tendermint
|
||||
------------------------------------------------------
|
||||
@ -896,7 +895,7 @@ engine while NGINX is used to serve the public key of the Tendermint instance.
|
||||
|
||||
$ kubectl --context k8s-bdb-test-cluster-0 get pods -w
|
||||
|
||||
.. _start-kubernetes-deployment-for-mdb-mon-agent-tmt:
|
||||
.. _start-kubernetes-deployment-for-mdb-mon-agent:
|
||||
|
||||
Step 18: Start a Kubernetes Deployment for MongoDB Monitoring Agent
|
||||
-------------------------------------------------------------------
|
||||
@ -925,13 +924,13 @@ Step 18: Start a Kubernetes Deployment for MongoDB Monitoring Agent
|
||||
$ kubectl --context k8s-bdb-test-cluster-0 apply -f mongodb-monitoring-agent/mongo-mon-dep.yaml
|
||||
|
||||
|
||||
.. _start-kubernetes-deployment-bdb-tmt:
|
||||
.. _start-kubernetes-deployment-bdb:
|
||||
|
||||
Step 19: Start a Kubernetes Deployment for BigchainDB
|
||||
-----------------------------------------------------
|
||||
|
||||
* This configuration is located in the file
|
||||
``bigchaindb/bigchaindb-dep-tm.yaml``.
|
||||
``bigchaindb/bigchaindb-dep.yaml``.
|
||||
|
||||
* Set ``metadata.name`` and ``spec.template.metadata.labels.app`` to the
|
||||
value set in ``bdb-instance-name`` in the ConfigMap, followed by
|
||||
@ -980,13 +979,13 @@ Step 19: Start a Kubernetes Deployment for BigchainDB
|
||||
|
||||
.. code:: bash
|
||||
|
||||
$ kubectl --context k8s-bdb-test-cluster-0 apply -f bigchaindb/bigchaindb-dep-tm.yaml
|
||||
$ kubectl --context k8s-bdb-test-cluster-0 apply -f bigchaindb/bigchaindb-dep.yaml
|
||||
|
||||
|
||||
* You can check its status using the command ``kubectl get deployments -w``
|
||||
|
||||
|
||||
.. _start-kubernetes-deployment-openresty-tmt:
|
||||
.. _start-kubernetes-deployment-openresty:
|
||||
|
||||
Step 20: Start a Kubernetes Deployment for OpenResty
|
||||
----------------------------------------------------
|
||||
@ -1036,7 +1035,7 @@ for details on how to configure the MongoDB Cloud Manager to enable
|
||||
monitoring and backup.
|
||||
|
||||
|
||||
.. _verify-and-test-bdb-tmt:
|
||||
.. _verify-and-test-bdb:
|
||||
|
||||
Step 22: Verify the BigchainDB Node Setup
|
||||
-----------------------------------------
|
||||
@ -1175,4 +1174,4 @@ verify that your node or cluster works as expected.
|
||||
|
||||
Next, you can set up log analytics and monitoring, by following our templates:
|
||||
|
||||
* :doc:`../production-deployment-template/log-analytics`.
|
||||
* :doc:`../production-deployment-template/log-analytics`.
|
||||
|
||||
@ -10,7 +10,7 @@ You can modify them to suit your needs.
|
||||
We use standalone MongoDB (without Replica Set), BFT replication is handled by Tendermint.
|
||||
|
||||
|
||||
.. _register-a-domain-and-get-an-ssl-certificate-for-it-tmt:
|
||||
.. _register-a-domain-and-get-an-ssl-certificate-for-it:
|
||||
|
||||
1. Register a Domain and Get an SSL Certificate for It
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
@ -63,7 +63,7 @@ the ``genesis_time`` and ``chain_id`` from this example ``genesis.json`` file:
|
||||
"app_hash": ""
|
||||
}
|
||||
|
||||
.. _things-each-node-operator-must-do-tmt:
|
||||
.. _things-each-node-operator-must-do:
|
||||
|
||||
Things Each Node Operator Must Do
|
||||
---------------------------------
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user