Fix typo in jsonnet dependency upgrade GH actions

Replace `commiter` to `committer`.

Refer https://github.com/peter-evans/create-pull-request#action-inputs

 for more
info about supported input properties for `peter-evans/create-pull-request@v3`.

Signed-off-by: Arunprasad Rajkumar <arajkuma@redhat.com>

.github/workflows: automated commits should come from @prom-op-bot account

Add grafana ldap support (take 2)

[bot] [main] Automated version update

remove deprecated policy/v1beta1 kubernetes api

Signed-off-by: Sahil Raja <sahilraja242@gmail.com>

Signed-off-by: Sahil Raja <sahilraja242@gmail.com>

[bot] [main] Automated version update

Signed-off-by: GitHub <noreply@github.com>

replace deprecated "app" label selector with "app.kubernetes.io/name" in documents and examples

documents and examples

Better ephemeral workspace support with Codespaces

[bot] [main] Automated version update

Signed-off-by: ArthurSens <arthursens2005@gmail.com>

Signed-off-by: GitHub <noreply@github.com>

Add e2e tests for Grafana deployment

Fix jsonnet extension

Add changelogs to automated version updates

Signed-off-by: ArthurSens <arthursens2005@gmail.com>

Signed-off-by: Arthur Sens <arthursens2005@gmail.com>

Drop some of the metrics exposed by prometheus-adapter

Add the links to the changelogs of the freshly updated components to the
automated PR that does the update. This allow verifying that we are not
missing any important changes before merging the update. This happened
recently with node-exporter 1.2 which changed some flag names that we
took 3 months to update.

Signed-off-by: Damien Grisonnet <dgrisonn@redhat.com>

jsonnet/node-exporter: adjust to node-exporter v1.2.0 arg name change

The current implementation of prometheus-adapter exposes a lot of
metrics about the health of its aggregated apiserver. The issue is that
the some of these metrics are not very useful in the context of
prometheus-adapter, and we currently can't avoid exposing them since
they are registered to the Kubernetes global Prometheus registry. Until
this is improved in upstream Kubernetes, we could benefit from dropping
some of the metrics that are not very useful.

Before this change, in a default kube-prometheus installation, we would
have 800+ series for prometheus-adapter against 400+, so we divided the
number of series by two will focusing on the most valuable metrics for
prometheus-adapter.

Signed-off-by: Damien Grisonnet <dgrisonn@redhat.com>