Problem:
can't get windows container/node metrics

Solution:
1. deploy windows node exporter
2. add add windows metrics service, endpoint, service monitor
3. add metric relabel rules to unify windows and linux expression

Issue:
https://github.com/rancher/rancher/issues/20513
https://github.com/rancher/rancher/issues/20076
https://github.com/rancher/rancher/issues/20122

Problem:
current elasticsearch gems has warning log for elasticsearch 7.x, rancher/fluentd have release new version

Solution:
upgrade fluentd, elasticsearch etc gems version

Issue:
https://github.com/rancher/rancher/issues/20450
https://github.com/rancher/rancher/issues/20509

Problem:
Daemonset api version extensions/v1beta1 is deperated in 1.16

Solution:
Use the capabilities API versions defined in template

Issue:
https://github.com/rancher/rancher/issues/21770

Problem:
now filename only allow numbers and letter

Solution:
change regex expression to allow all charaters

Issue:
https://github.com/rancher/rancher/issues/17022

Formerly, it is accessible by authenticated users.
Now, it is accessible by cluster owners and authorized users/groups.

* important stuff: update README

* cis chart - initial version

* updating to use same image

* adding owner

* fixing the image name, version

Using Rancher repo instead of harbor repo.

Change all the repository in the istio to use rancher repo to pull the
image.

Problem:
Registry pod stuck in AttchVolumeFailed status on upgrade. Deadlock happens where the new pod waits the old pod to dettach the volume, and the old one waits for the new one to be ready.

Solution:
Set maxUnavailable to 1, so that the old pod can be released before the new pod is ready.

  * add istio and certmanager CRDs
  * add rancher system default registry config
  * add rancher proxy to the Grafana, Prometheus, Kiali and Tracing
  * remove not used demo values.yaml files and serviceGraph(deprecated)

Add globalRegistryMode to enable deploying the Harbor as a global
registry in Rancher. It use the same domain as Rancher server in
ingress rules, and use the same tls-rancher-ingress secret for TLS.

Co-authored-by: Guangbo <guangbo@rancher.com>
Co-authored-by: gitlawr <lawrleegle@gmail.com>

Do Helm lint validation and Helm unittest for the charts

Problem:
alertmanager 0.16.0 unable to send email notification without SMTP authentication
Solution:
upgrade to alertmanger 0.17.0 which solve this problem

Issue:
https://github.com/rancher/rancher/issues/20060

**Problem:**
Buffering proxy data causes client to receive slow

**Solution:**
Disable buffer via `proxy_buffering  off;` to response client directly

**Issue:**
https://github.com/rancher/rancher/issues/19689

**Problem:**
Upgrade the operator would have errors because we change the version of
the operator charts.

**Solution:**
Keep the old version 0.0.2 the operator used before.

**Problem:**
There are two kubelet scraping targets on Prometheus, one is scraping `/metrics`, another one is scraping `/metrics/cadvisor`.
The metrics from `/metrics` endpoint are not including `container_name`.
So the `container_*` expression will double the actual mount without
`conatiner_name!=""`

**Solution:**
Add `container_name!=""` into the expression

**Issue:**
https://github.com/rancher/rancher/issues/20162