* Addon: Use Hostprocess for Windows Exporter #1627

This allows for Windows Exporter to be deployed and configured
dynamically without requiring to specify targets manually for each
Windows node

Documentation and example added

* Addon: Windows Exporter using Hostprocess

Fix some performance issues.
- Specify resource limits for windows exporter.
- Allow for scrape timeout and interval to be configured. Depending
on how many pods are running on a node it can take from 500ms to 15s
to scrape metrics from node. Default timeout is 10s.
- Allow for enabled collectors to be configured.
- Only enable collectors that are being used in rules and dashboards.

* Addon: Windows Exporter using Hostprocess

Fix formatting issues

* Fix formatting issues in windows-hostprocess addon

* Windows Addon: update doc to reflect both configs
- Hostprocess and static

* Windows Addon: update doc

---------

Co-authored-by: Dinesh Sharma <dinesh.sharma@health.telstra.com>

Co-authored-by: Prometheus Operator Bot <prom-op-bot@users.noreply.github.com>

I want to deploy that version and rather than doing an overwrite on our end, I thought I might just send the PR through here right away.

* create service to expose coredns metrics

Signed-off-by: Raul Garcia Sanchez <info@raulgarcia.de>

* create service to expose coredns metrics

Signed-off-by: Raul Garcia Sanchez <info@raulgarcia.de>

---------

Signed-off-by: Raul Garcia Sanchez <info@raulgarcia.de>

Co-authored-by: Prometheus Operator Bot <prom-op-bot@users.noreply.github.com>

Co-authored-by: Prometheus Operator Bot <prom-op-bot@users.noreply.github.com>

Co-authored-by: Prometheus Operator Bot <prom-op-bot@users.noreply.github.com>

Co-authored-by: Prometheus Operator Bot <prom-op-bot@users.noreply.github.com>

Co-authored-by: Prometheus Operator Bot <prom-op-bot@users.noreply.github.com>

Co-authored-by: Prometheus Operator Bot <prom-op-bot@users.noreply.github.com>

Co-authored-by: Prometheus Operator Bot <prom-op-bot@users.noreply.github.com>

Co-authored-by: Prometheus Operator Bot <prom-op-bot@users.noreply.github.com>

Co-authored-by: Prometheus Operator Bot <prom-op-bot@users.noreply.github.com>

* Improve ArgoCD support

Signed-off-by: Fran Sanjuán <francesc.sanjuan@marfeel.com>

* Add modified yamls

Signed-off-by: Fran Sanjuán <francesc.sanjuan@marfeel.com>

---------

Signed-off-by: Fran Sanjuán <francesc.sanjuan@marfeel.com>

Co-authored-by: Prometheus Operator Bot <prom-op-bot@users.noreply.github.com>

Missing in prometheus-operator, node-exporter and blacbox-exporter.

Signed-off-by: Haoyu Sun <hasun@redhat.com>

Issue: https://issues.redhat.com/browse/OCPBUGS-7694



Problem: in clusters with a large nb of CRDs deployed prom-adapter takes too long to discover all of them which makes it fail the livenessProbe

Solution: introduce a startupProbe that gives 3 minutes for prom-adapter to initialize

Signed-off-by: JoaoBraveCoding <jmarcal@redhat.com>

Co-authored-by: Prometheus Operator Bot <prom-op-bot@users.noreply.github.com>

Co-authored-by: Prometheus Operator Bot <prom-op-bot@users.noreply.github.com>

Co-authored-by: Prometheus Operator Bot <prom-op-bot@users.noreply.github.com>

Signed-off-by: Haoyu Sun <hasun@redhat.com>
Co-authored-by: SUN Haoyu <hasun@redhat.com>

Co-authored-by: Prometheus Operator Bot <prom-op-bot@users.noreply.github.com>

Co-authored-by: Prometheus Operator Bot <prom-op-bot@users.noreply.github.com>

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

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

Co-authored-by: Prometheus Operator Bot <prom-op-bot@users.noreply.github.com>

Co-authored-by: Prometheus Operator Bot <prom-op-bot@users.noreply.github.com>

* update ksm target git branch name

* `jb update`; `make generate`

Co-authored-by: Prometheus Operator Bot <prom-op-bot@users.noreply.github.com>

Co-authored-by: Prometheus Operator Bot <prom-op-bot@users.noreply.github.com>

Co-authored-by: Prometheus Operator Bot <prom-op-bot@users.noreply.github.com>

Update regex used for selecting disk devices to include raid devices of
the form "md123".

Kubernetes has switched registry from k8s.gcr.io to registry.k8s.io
in https://github.com/kubernetes/kubernetes/pull/109938.

kube-state-metrics also did the switch in
https://github.com/kubernetes/kube-state-metrics/pull/1750.

This commit also updates the registry in a kubeadm configuration
example.