```yaml cat < * By running `helm install victoria-metrics vm/victoria-metrics-single` we will install `VictoriaMetrics Single` to default namespace inside your cluster * By adding `scrape: enable: true` we add and enable autodiscovery scraping from kubernetes cluster to `VictoriaMetrics Single` As a result of the command you will see the following output: ```bash NAME: victoria-metrics LAST DEPLOYED: Fri Jun 25 12:06:13 2021 NAMESPACE: default STATUS: deployed REVISION: 1 TEST SUITE: None NOTES: The VictoriaMetrics write api can be accessed via port 8428 on the following DNS name from within your cluster: victoria-metrics-victoria-metrics-single-server.default.svc.cluster.local Metrics Ingestion: Get the Victoria Metrics service URL by running these commands in the same shell: export POD_NAME=$(kubectl get pods --namespace default -l "app=server" -o jsonpath="{.items[0].metadata.name}") kubectl --namespace default port-forward $POD_NAME 8428 Write url inside the kubernetes cluster: http://victoria-metrics-victoria-metrics-single-server.default.svc.cluster.local:8428/api/v1/write Metrics Scrape: Pull-based scrapes are enabled Scrape config can be displayed by running this command: kubectl get cm victoria-metrics-victoria-metrics-single-server-scrapeconfig -n default The target’s information is accessible via api: Inside cluster: http://victoria-metrics-victoria-metrics-single-server.default.svc.cluster.local:8428/atargets Outside cluster: You need to port-forward service (see instructions above) and call http:///targets Read Data: The following url can be used as the datasource url in Grafana: http://victoria-metrics-victoria-metrics-single-server.default.svc.cluster.local:8428 ``` For us it’s important to remember the url for the datasource (copy lines from output). Verify that VictoriaMetrics pod is up and running by executing the following command:

```bash kubectl get pods ```

The expected output is: ```bash NAME READY STATUS RESTARTS AGE victoria-metrics-victoria-metrics-single-server-0 1/1 Running 0 22s ``` **3. Install and connect Grafana to VictoriaMetrics with helm** Add the Grafana helm repository.

```bash helm repo add grafana https://grafana.github.io/helm-charts helm repo update ```

See more info on Grafana ArtifactHUB [https://artifacthub.io/packages/helm/grafana/grafana](https://artifacthub.io/packages/helm/grafana/grafana) By installing the Chart with the release name `my-grafana`, you add the VictoriaMetrics datasource with official dashboard and kubernetes dashboard:

```yaml cat < By running this command we: * Install Grafana from helm repository. * Provision VictoriaMetrics datasource with the url from the output above which we copied before. * Add this [https://grafana.com/grafana/dashboards/10229](https://grafana.com/grafana/dashboards/10229) dashboard for VictoriaMetrics. * Add this [https://grafana.com/grafana/dashboards/14205](https://grafana.com/grafana/dashboards/14205) dashboard to see Kubernetes cluster metrics. Check the output log in your terminal. To see the password for Grafana `admin` user use the following command:

```bash kubectl get secret --namespace default my-grafana -o jsonpath="{.data.admin-password}" | base64 --decode ; echo ```

Expose Grafana service on `127.0.0.1:3000`:

```bash export POD_NAME=$(kubectl get pods --namespace default -l "app.kubernetes.io/name=grafana,app.kubernetes.io/instance=my-grafana" -o jsonpath="{.items[0].metadata.name}") kubectl --namespace default port-forward $POD_NAME 3000 ```

Now Grafana should be accessible on the [http://127.0.0.1:3000](http://127.0.0.1:3000) address. **4. Check the obtained result in your browser** To check that VictoriaMetrics has collected metrics from the k8s cluster open in browser [http://127.0.0.1:3000/dashboards](http://127.0.0.1:3000/dashboards) and choose `Kubernetes Cluster Monitoring (via Prometheus)` dashboard. Use `admin` for login and `password` that you previously obtained from kubectl.

You will see something like this:

VictoriaMetrics dashboard also available to use:

**5. Final thoughts** * We have set up TimeSeries Database for your k8s cluster. * We collected metrics from all running pods, nodes, … and stored them in VictoriaMetrics database. * We can visualize the resources used in your Kubernetes cluster by using Grafana dashboards.