Commit abd6db4b authored by garciadeblas's avatar garciadeblas
Browse files

Update 15-k8s-installation.md to fix Markdown format 



Signed-off-by: default avatargarciadeblas <gerardo.garciadeblas@telefonica.com>
parent 4a5e9fb0

15-k8s-installation.md

+25 −19
Original line number Diff line number Diff line
@@ -323,7 +323,7 @@ Other configuration you need for your kubernetes cluster is the creation of the 
A kubernetes persistent volume storage can be installed to your kubernetes cluster applying the following manifest.



```bash

kubectl apply -f https://openebs.github.io/charts/openebs-operator.yaml

kubectl apply -f https://openebs.github.io/charts/openebs-operator-1.6.0.yaml

```



After the installation, you need to check if there is a default `storageclass` in your kubernetes:
@@ -333,6 +333,8 @@ kubectl get storageclass 
NAME                         PROVISIONER                                                RECLAIMPOLICY   VOLUMEBINDINGMODE      ALLOWVOLUMEEXPANSION   AGE

openebs-device               openebs.io/local                                           Delete          WaitForFirstConsumer   false                  5m47s

openebs-hostpath             openebs.io/local                                           Delete          WaitForFirstConsumer   false                  5m47s

openebs-jiva-default         openebs.io/provisioner-iscsi                               Delete          Immediate              false                  5m48s

openebs-snapshot-promoter    volumesnapshot.external-storage.k8s.io/snapshot-promoter   Delete          Immediate              false                  5m47s

```



Until now, there is not default `storageclass` defined. With the command below we will define `openebs-hostpath` as default storageclass:
@@ -348,6 +350,8 @@ kubectl get storageclass 
NAME                         PROVISIONER                                                RECLAIMPOLICY   VOLUMEBINDINGMODE      ALLOWVOLUMEEXPANSION   AGE

openebs-device               openebs.io/local                                           Delete          WaitForFirstConsumer   false                  5m47s

openebs-hostpath (default)   openebs.io/local                                           Delete          WaitForFirstConsumer   false                  5m47s

openebs-jiva-default         openebs.io/provisioner-iscsi                               Delete          Immediate              false                  5m48s

openebs-snapshot-promoter    volumesnapshot.external-storage.k8s.io/snapshot-promoter   Delete          Immediate              false                  5m47s

```



For Kubernetes clusters > 1.15 there is needed special permission of Tiller that can be added by the following command:
@@ -356,7 +360,8 @@ For Kubernetes clusters > 1.15 there is needed special permission of Tiller that 
kubectl create clusterrolebinding tiller-cluster-admin --clusterrole=cluster-admin  --serviceaccount=kube-system:default

```



# Enabling K8s Cluster Monitoring 

## Enabling K8s Cluster Monitoring



After the K8s cluster is deployed using the steps mentioned above, it is also possible to monitor the workloads running in this K8s cluster using OSM. This K8s cluster is where OSM will deploy KNFs and it is the not the K8s cluster on which OSM is installed.



On the K8 cluster to be monitored Prometheus operator is installed. Once this K8s cluster information is registered in OSM. MON creates a dashboard automatically in Grafana. Grafana connects to the Prometheus opertator installed in K8s cluster to fetch the performance data of the K8s workloads.
@@ -365,13 +370,13 @@ The following steps describes the procedure to install prometheus operator on K8 




1. Run the following steps on K8s-cluster machine to install Prometheus operator:

	 -	Install helm



   - Install helm:

     ```bash

     wget https://get.helm.sh/helm-v3.6.2-linux-amd64.tar.gz

     tar -zxvf helm-v3.6.2-linux-amd64.tar.gz

     sudo mv linux-amd64/helm /usr/local/bin/helm

     ```



   - Install prometheus-operator in monitoring namespace

     ```bash

     helm repo add prometheus-community https://prometheus-community.github.io/helm-charts
@@ -383,3 +388,4 @@ The following steps describes the procedure to install prometheus operator on K8 
2. After steps mentioned above are successful, then OSM is ready to monitor K8s cluster. Once the K8s cluster is registered against a OSM project, the corresponding dashboard will be visible in Grafana, as shown below.



   ![K8s-monitoring-dashboard](assets/800px-k8s-monitoring-grafana-dasboard.png)