zeritti
zeritti
The `no_proxy` field is currently not supported by the operator (0.71). Work in progress: https://github.com/prometheus-operator/prometheus-operator/pull/6290
The problem should get fixed by setting `root_url` in `grafana.ini` ([Ref.](https://grafana.com/docs/grafana/latest/setup-grafana/configure-grafana/#root_url)). For example, with ingress host `grafana.example.local` and TLS: ```yaml grafana: grafana.ini: server: domain: grafana.example.local root_url: "https://%(domain)s/" ``` If using...
> Isn't this a default value? No, it is not. The default `root_url` is set to ``` %(protocol)s://%(domain)s:%(http_port)s/ ``` `protocol`, `domain` and `http_port` are configuration parameters of the `server` section...
Some hints: 1. `groups` belongs in a Prometheus' [rules file](https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/), i.e. is a Prometheus' [configuration](https://prometheus.io/docs/prometheus/latest/configuration/configuration/) parameter 2. In `routes[].matchers[]`, a list of label key/value pairs is expected ([example](https://prometheus.io/docs/alerting/latest/configuration/#example)), e.g. ```...
The config you see on the alertmanager's status page as shown above is indeed the default one. It means that your custom config had not been accepted by the operator....
The values file needs to be amended as the exporter release 0.9 does not start with an invalid `consulServer`: ```yaml consulServer: host:port ``` As users set their own Consul server...
> @zeritti done, should this be considered a breaking change? In my opinion, no, not at all.
Thank you, @FalkW, for your PR. Please, raise the chart's version number in Chart.yaml.
Please, check your commits' signatures - DCO check is not passing.
My impression is that introducing 2381 as an Etcd metrics port in the chart was based on a specific internal change in _kubeadm_, judging from the link to its constants...