Connecting a Kubernetes cluster
Kubernetes
Kubernetes clusters require installation of Prometheus which is a pull-based monitoring tool used for collecting metadata on pods and nodes, resources discovery, and hardware utilization on nodes. This consumption details are recalculated into Expenses based on the detected / user-defined cost model.
Both cloud-based and isolated Kubernetes clusters are supported and can be tracked in DigiUsher. The main pre-requisite for adding such clusters as a data source is the correctly configured Prometheus service needed for collecting metrics from pods, nodes and namespaces on their CPU, GPU and memory usage for different time spans.
Helm install configurations
Helm 3 version must be used
Resources can be deployed with the following commands: NodePort example
helm install --namespace digiusher \
--create-namespace \
--set nginx.service.type=NodePort \
--set nginx.service.enabledExternalPort=true \
--set nginx.service.externalPort=31222 \
--set nginx.passwd=$(htpasswd -nbm "digiusher" "<SOME_PASSWORD>") monitoring
LoadBalancer example (recommended for cloud-based clusters):
helm install --namespace digiusher \
--create-namespace \
--set nginx.service.internalPort=4433 \
--set nginx.passwd=$(htpasswd -nbm "digiusher" "<SOME_PASSWORD>") monitoring
Helm chart parameters The table below lists the commonly used configurable parameters of the Helm chart and their default values.
| Parameter | Description | Default |
|---|---|---|
| nginx.enabled | if false, use another way to expose the Prometheus port | true |
| nginx.service.type | NodePort or LoadBalancer | LoadBalancer |
| nginx.service.internalPort | Internal NGINX Server Port Number | 4433 |
| nginx.passwd | MD5 hash of the username and password to login to the Agent metrics | digiusher: |
| nginx.service.enabledExternalPort | use true for NodePort and false for LoadBalancer | false |
| nginx.service.externalPort | Agent external Node port number | 31222 |
Specifying the externalPort value will set the port at which Prometheus will become accessible.
Kubernetes cluster as Data Source
To track a Kubernetes cluster as a data source in your DigiUsher account, please select the Kubernetes tab at the Data Source Connection step during the initial configuration or later on in the Settings section of the main page.
Name - any preferred name to be used for this data source in DigiUsher.
URL - Kubernetes metrics collector URL (Prometheus).
Port - port on which the collector is listening.
User - user to authenticate to the Kubernetes collector, digiusher by default.
Password - password to authenticate to the Kubernetes collector.
Press “Connect” to validate the provided parameters. Your Kubernetes data source should now be ready for integration with DigiUsher! Please contact our Support Team at support@digiusher.com if you have any questions or face any issues.