From adf34cc51be366d04eb7ddd45412af0478cb4cfe Mon Sep 17 00:00:00 2001 From: Cedric Verstraeten Date: Sun, 11 Aug 2024 09:13:34 +0200 Subject: [PATCH] Update README.microk8s.md --- README.microk8s.md | 33 ++------------------------------- 1 file changed, 2 insertions(+), 31 deletions(-) diff --git a/README.microk8s.md b/README.microk8s.md index 7a2d00a..7048738 100644 --- a/README.microk8s.md +++ b/README.microk8s.md @@ -85,40 +85,11 @@ Or view the pod status with: kubectl get po -w -A ``` -## Kerberos Vault - -### OpenEBS - -Some of the services we'll leverage such as MongoDB or Minio require storage, to persist their data safely. In a managed Kubernetes cluster, the relevant cloud provider will allocate storage automatically for you, as you might expect this is not the case for a self-hosted cluster. - -Therefore we will need to prepare some storage or persistent volume. To simplify this we can leverage the OpenEBS storage solution, which can automatically provision PV (Persistent volumes) for us. - -Let us start with installing the OpenEBS operator. Please note that you might need to change the mount folder. Download the `openebs-operator.yaml`. - - wget https://openebs.github.io/charts/openebs-operator.yaml - -Scroll to the bottom, until you hit the `StorageClass` section. Modify the `BasePath` value to the destination (external mount) you prefer. - - #Specify the location (directory) where - # where PV(volume) data will be saved. - # A sub-directory with pv-name will be - # created. When the volume is deleted, - # the PV sub-directory will be deleted. - #Default value is /var/openebs/local - - name: BasePath - value: "/var/openebs/local/" - -Once you are ok with the `BasePath` go ahead and apply the operator. - - kubectl apply -f openebs-operator.yaml - -Once done it should start installing several resources in the `openebs` namespace. If all resources are created successfully we can launch the `helm install` for MongoDB. - -### MongoDB +### Database: MongoDB When using Kerberos Vault, it will persist references to the recordings stored in your storage provider in a MongoDB database. As used before, we are using `helm` to install MongoDB in our Kubernetes cluster. Within the Kerberos Vault project we are using the latest official mongodb driver, so we support all major MongoDB versions (4.x, 5.x, 6.x, 7.x). -Have a look into the `./mongodb/values.yaml` file, you will find plenty of configurations for the MongoDB helm chart. To change the username and password of the MongoDB instance, go ahead and [find the attribute where](https://github.com/kerberos-io/vault/blob/master/kubernetes/mongodb/values.yaml#L148) you can change the root password. Please note that we are using the official [Bitnami Mongodb helm chart](https://github.com/bitnami/charts/tree/main/bitnami/mongodb), so please use their repository for more indepth configuration. +Have a look into the `./mongodb-values.yaml` file, you will find plenty of configurations for the MongoDB helm chart. To change the username and password of the MongoDB instance, go ahead and [find the attribute where](https://github.com/kerberos-io/vault/blob/master/kubernetes/mongodb/values.yaml#L148) you can change the root password. Please note that we are using the official [Bitnami Mongodb helm chart](https://github.com/bitnami/charts/tree/main/bitnami/mongodb), so please use their repository for more indepth configuration. Next to that you might also consider a SaaS MongoDB deployment using MongoDB Atlas or using a managed cloud like AWS, GCP, Azure or Alibaba cloud. A managed service takes away a lot of management and maintenance from your side (backups, security, sharing, etc). If you do want to install MongoDB in your own cluster then please continue with this tutorial.