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

This is a follow up fix of https://github.com/prometheus-operator/kube-prometheus/pull/1613

. @simonpasquier recommended to sanitize all denylist metrics.

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

The following metrics are missing from kube-state-metrics:
- kube_pod_container_status_terminated_reason
- kube_pod_init_container_status_terminated_reason
- kube_pod_status_scheduled_time

Previously, some metrics were removed from kube-state-metrics by adding the following --metric-denylist argument to the kube-state-metrics container

```
--metric-denylist=
kube_.+_created,
kube_.+_metadata_resource_version,
kube_replicaset_metadata_generation,
kube_replicaset_status_observed_generation,
kube_pod_restart_policy,
kube_pod_init_container_status_terminated,
kube_pod_init_container_status_running,
kube_pod_container_status_terminated,
kube_pod_container_status_running,
kube_pod_completion_time,
kube_pod_status_scheduled
```

--metric-denylist: Comma-separated list of metrics not to be enabled. This list comprises of exact metric names and/or regex patterns. The allowlist and denylist are mutually exclusive.

However, all the list of metrics is managed as RegEx, thus "kube_pod_container_status_terminated" denies .*kube_pod_container_status_terminated.*, that's why kube_pod_init_container_status_terminated_reason is missing

Co-authored-by: Florian Gleizes <fgleizes@redhat.com>
Signed-off-by: Arunprasad Rajkumar <arajkuma@redhat.com>

Drop Linux capabilities

jsonnet: filter out kube-proxy alerts when kube-proxy is disabled

Signed-off-by: Paweł Krupa (paulfantom) <pawel@krupa.net.pl>

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

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

[bot] [main] Automated version update

This reverts commit f0d9be27.

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

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

docs: Update broken link

Document security audit exceptions for node-exporter

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

Explicitly declare allowPrivilegeEscalation to false in all components

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

Although containers that do not run as privileged already have this set to false by kubernetes
Kubespace [asks us](https://hub.armo.cloud/docs/c-0016

) to explicitly declare it to false where not needed.

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

[bot] [main] Automated version update

Scan generated manifests with kubescape in CI

https://github.com/armosec/kubescape allows us to
run a scan of the generated manifests and assess the
security risk.

build: Bump to build with Go 1.17