Mirroristas/bigchaindb
2
0
Fork 0
mirror of https://github.com/bigchaindb/bigchaindb.git synced 2024-10-13 13:34:05 +00:00
Code Issues Packages Projects Releases Wiki Activity

repaired problematic kubernetes hyperlinks

Browse Source
This commit is contained in:
Troy McConaghy 2017-04-13 12:29:53 +02:00
parent 24f7e2662b
commit 7f8ab60d3b
2 changed files with 9 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/server/source/cloud-deployment-templates/node-on-kubernetes.rst
View File

@ -157,7 +157,7 @@ Step 5: Create the Config Map - Optional
This step is required only if you are planning to set up multiple This step is required only if you are planning to set up multiple
`BigchainDB nodes `BigchainDB nodes
<https://docs.bigchaindb.com/en/latest/terminology.html#node>`_. <https://docs.bigchaindb.com/en/latest/terminology.html>`_.
MongoDB reads the local ``/etc/hosts`` file while bootstrapping a replica set MongoDB reads the local ``/etc/hosts`` file while bootstrapping a replica set
to resolve the hostname provided to the ``rs.initiate()`` command. It needs to to resolve the hostname provided to the ``rs.initiate()`` command. It needs to
@ -268,7 +268,7 @@ Step 7: Initialize a MongoDB Replica Set - Optional
This step is required only if you are planning to set up multiple This step is required only if you are planning to set up multiple
`BigchainDB nodes `BigchainDB nodes
<https://docs.bigchaindb.com/en/latest/terminology.html#node>`_. <https://docs.bigchaindb.com/en/latest/terminology.html>`_.
Login to the running MongoDB instance and access the mongo shell using: Login to the running MongoDB instance and access the mongo shell using:
@ -315,7 +315,7 @@ Step 8: Create a DNS record - Optional
This step is required only if you are planning to set up multiple This step is required only if you are planning to set up multiple
`BigchainDB nodes `BigchainDB nodes
<https://docs.bigchaindb.com/en/latest/terminology.html#node>`_. <https://docs.bigchaindb.com/en/latest/terminology.html>`_.
**Azure.** Select the current Azure resource group and look for the ``Public IP`` **Azure.** Select the current Azure resource group and look for the ``Public IP``
resource. You should see at least 2 entries there - one for the Kubernetes resource. You should see at least 2 entries there - one for the Kubernetes
@ -426,9 +426,8 @@ on the cluster and query the internal DNS and IP endpoints.
$ kubectl run -it toolbox -- image <docker image to run> --restart=Never --rm $ kubectl run -it toolbox -- image <docker image to run> --restart=Never --rm
There is a generic image based on alpine:3.5 with the required utilities There is a generic image based on alpine:3.5 with the required utilities
hosted at Docker Hub under ``bigchaindb/toolbox``. hosted at Docker Hub under `bigchaindb/toolbox <https://hub.docker.com/r/bigchaindb/toolbox/>`_.
The corresponding Dockerfile is `here The corresponding Dockerfile is in the bigchaindb/bigchaindb repository on GitHub, at `https://github.com/bigchaindb/bigchaindb/blob/master/k8s/toolbox/Dockerfile <https://github.com/bigchaindb/bigchaindb/blob/master/k8s/toolbox/Dockerfile>`_.
<https://github.com/bigchaindb/bigchaindb/k8s/toolbox/Dockerfile>`_.
You can use it as below to get started immediately: You can use it as below to get started immediately:

8
docs/server/source/cloud-deployment-templates/upgrade-on-kubernetes.rst
View File

@ -53,7 +53,7 @@ on the node and mark it as unscheduleable
kubectl drain $NODENAME kubectl drain $NODENAME
There are `more details in the Kubernetes docs <https://kubernetes.io/docs/admin/cluster-management/#maintenance-on-a-node>`_, There are `more details in the Kubernetes docs <https://kubernetes.io/docs/concepts/cluster-administration/cluster-management/#maintenance-on-a-node>`_,
including instructions to make the node scheduleable again. including instructions to make the node scheduleable again.
To manually upgrade the host OS, To manually upgrade the host OS,
@ -82,13 +82,13 @@ A typical upgrade workflow for a single Deployment would be:
$ KUBE_EDITOR=nano kubectl edit deployment/<name of Deployment> $ KUBE_EDITOR=nano kubectl edit deployment/<name of Deployment>
The `kubectl edit <https://kubernetes.io/docs/user-guide/kubectl/kubectl_edit/>`_ The ``kubectl edit`` command
command opens the specified editor (nano in the above example), opens the specified editor (nano in the above example),
allowing you to edit the specified Deployment *in the Kubernetes cluster*. allowing you to edit the specified Deployment *in the Kubernetes cluster*.
You can change the version tag on the Docker image, for example. You can change the version tag on the Docker image, for example.
Don't forget to save your edits before exiting the editor. Don't forget to save your edits before exiting the editor.
The Kubernetes docs have more information about The Kubernetes docs have more information about
`updating a Deployment <https://kubernetes.io/docs/user-guide/deployments/#updating-a-deployment>`_. `Deployments <https://kubernetes.io/docs/concepts/workloads/controllers/deployment/>`_ (including updating them).
The upgrade story for the MongoDB StatefulSet is *different*. The upgrade story for the MongoDB StatefulSet is *different*.