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

Fixed spelling & grammar stuff in docs re MDB StatefulSet

Browse Source
This commit is contained in:
Troy McConaghy 2017-06-29 16:02:34 +02:00
parent 1034db1ce5
commit 92ec8f613e
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/server/source/production-deployment-template/node-on-kubernetes.rst
View File

@ -453,11 +453,11 @@ Step 11: Start a Kubernetes StatefulSet for MongoDB
* Note how the MongoDB container uses the ``mongo-db-claim`` and the * Note how the MongoDB container uses the ``mongo-db-claim`` and the
``mongo-configdb-claim`` PersistentVolumeClaims for its ``/data/db`` and ``mongo-configdb-claim`` PersistentVolumeClaims for its ``/data/db`` and
``/data/configdb`` diretories (mount path). ``/data/configdb`` directories (mount paths).
* Note also that we use the pod's ``securityContext.capabilities.add`` * Note also that we use the pod's ``securityContext.capabilities.add``
specification to add the ``FOWNER`` capability to the container. That is specification to add the ``FOWNER`` capability to the container. That is
because MongoDB container has the user ``mongodb``, with uid ``999`` and because the MongoDB container has the user ``mongodb``, with uid ``999`` and
group ``mongodb``, with gid ``999``. group ``mongodb``, with gid ``999``.
When this container runs on a host with a mounted disk, the writes fail When this container runs on a host with a mounted disk, the writes fail
when there is no user with uid ``999``. To avoid this, we use the Docker when there is no user with uid ``999``. To avoid this, we use the Docker