79ac1a00e3
```
Updated:
argo/argo-cd:
- 5.42.0
asserts/asserts:
- 1.50.0
bitnami/cassandra:
- 10.4.5
bitnami/postgresql:
- 12.7.1
bitnami/redis:
- 17.14.3
bitnami/spark:
- 7.1.2
bitnami/tomcat:
- 10.9.6
bitnami/wordpress:
- 16.1.34
bitnami/zookeeper:
- 11.4.10
cert-manager/cert-manager:
- v1.12.3
datadog/datadog:
- 3.33.6
datadog/datadog-operator:
- 1.0.8
fairwinds/polaris:
- 5.11.2
harbor/harbor:
- 1.12.3
jenkins/jenkins:
- 4.5.0
jfrog/artifactory-ha:
- 107.63.8
jfrog/artifactory-jcr:
- 107.63.8
kubecost/cost-analyzer:
- 1.105.1
new-relic/nri-bundle:
- 5.0.24
openebs/openebs:
- 3.8.0
redpanda/redpanda:
- 5.0.6
speedscale/speedscale-operator:
- 1.3.23
sysdig/sysdig:
- 1.16.4
traefik/traefik:
- 23.2.0
```
|
||
|---|---|---|
| .. | ||
| charts | ||
| examples | ||
| scripts | ||
| templates | ||
| .helmignore | ||
| Chart.lock | ||
| Chart.yaml | ||
| README.md | ||
| app-readme.md | ||
| large.yaml | ||
| medium.yaml | ||
| small.yaml | ||
| values.yaml | ||
README.md
Asserts
Asserts is a metrics intelligence platform built on Prometheus’s open ecosystem. Asserts scans your metrics to build a dependency graph and then analyzes them using Asserts's SAAFE model.
Introduction
This chart bootstraps an Asserts deployment on a Kubernetes cluster using the Helm package manager.
Prerequisites
- Kubernetes 1.17+
- Helm 3.2.0+
- PV provisioner support for the underlying infrastructure
- A Prometheus compatible endpoint with kube-state-metrics and node-exporter
Installing the Chart
helm repo add asserts https://asserts.github.io/helm-charts
helm repo update
helm upgrade asserts asserts/asserts \
--install \
--namespace asserts \
--create-namespace
Asserts uses metric label informaton to build the Entity Graph, it will use labels from service meshes (Istio, Linkerd) or from the Asserts eBPF Probe. By default the probe is not enabled, it can be enabled via a values file or from the Helm command line.
helm upgrade asserts asserts/asserts \
--upgrade \
--namespace asserts \
--create-namespace \
--set ebpfProbe.enabled=true
There any many configuration options such as PagerDuty and Slack integrations. These can be configured with a values file. View all install configuration options here.
Verify and Access
When Asserts is spinning up for the first time, it usually takes about 3-4 minutes but could take longer depending on the hardware resources allocated (e.g. a kind/k3d cluster).
Once all containers are initialized and running:
kubectl get pods -l app.kubernetes.io/instance=asserts -n asserts
You can then login to the asserts-ui by running:
kubectl port-forward svc/asserts-ui 8080 -n asserts
And opening your browser to http://localhost:8080, where you will be directed to the Asserts Registration page. There you can acquire a license.
Acquire a License
Acquire a trial license by following these steps
Configuring a Prometheus DataSource
Configure your Prometheus DataSource which Asserts will connect to and query by following these instructions. Once you're connected, you can see the data and start observing!
Upgrading the Chart
helm repo update
helm upgrade --install asserts asserts/asserts -n asserts
Sizing Values
The default Helm chart values in the values.yaml file are configured to allow you to quickly get Asserts up and running. Here are some sample values files for sizing resources according to the total number of raw metrics at the source Prometheus endpoints:
small: Up to 1 million metrics
medium: 1 to 5 million metrics
large: Over 5 million metrics
Uninstalling the Chart
To uninstall/delete the asserts deployment:
helm delete asserts -n asserts
The command removes all the Kubernetes components but PVC's associated with the chart and deletes the release.
To delete the PVC's associated with asserts:
kubectl delete pvc -l app.kubernetes.io/instance=asserts -n asserts
Note: Deleting the PVC's will delete all asserts related data as well.