This operator helps to configure uptrends monitoring for your Ingress Controllers.
The operator is based on the uptrends package. It is a Kubernetes operator that watches for Ingress resources and creates uptrends checks for them. It also watches for changes in the Ingress resources and updates the uptrends checks accordingly.
Helm can be used to install 📈 uptrends Operator.
helm repo add uptrends https://ionos-cloud.github.io/uptrends-operator/
helm repo updateThe most recent version is installed via.
helm install uptrends uptrends/uptrends --create-namespace --namespace uptrends --version v0.1.11The required API_USERNAME and API_PASSWORD can be securely configured via envFrom in the values.yaml.
This configures the required username for the uptrends API access. See the uptrends documentation for more information.
This configures the required password for the uptrends API access. See the uptrends documentation for more information.
The operator supports creating a monitor via the Uptrends kind, but also via annotations on an Ingress.
The operator will create an uptrend in case the ingress has this annotation: uptrends.ionos-cloud.github.io/monitor: "true",
otherwise the ingress will not be monitored.
The following keys are supported:
This can be either HTTPS or HTTP.
This can be an interval from 1 to 60 minutes.
The annotations are evaluates agains the
hostfields on therules. Wildcard hosts and empty hosts are ignored.
This can be used to add the monitor to a Monitor Group identified with a MonitorGroupID.
This is a list of regions to include as checkpoints. An example "54,1007"
This is a list of point of presence to include.
This is a list of point of presence to exclude as checkpoints.
/examples contains the example of an Ingress and Uptrends based monitor.
Renaming the ingress does not delete monitors.