The README referenced the old, deprecated helm/charts repository, even though these are not used by rancher-monitoring anymore.
Signed-off-by: Bastian Hofmann <mail@bastianhofmann.de>
Specifically, the default keys in questions.yaml are ignored by the
frontend, even when set, and have no effect. I'm assuming these are
a holdover from some older version of the frontend.
With the switch from AngularJS to ReactJS, grafana is now using
/absolute/url style hrefs in its templates and its JavaScript assets,
but these URLs are passed directly into React's clientside routing
engine rather than hitting the proxy on the backend. Thus, rewriting
these URLs is inappropriate, confuses the clientside router, and breaks
interlink between several tabs in the UI, and a few dashboards, among
other things.
Attempts to address #2445
It seems like the order of parameters in the CRD uninstall Job are incorrect.
```
arvindiyengar: ~/Rancher/charts/src/github.com/rancher/charts
$ kubectl apply -f charts/rancher-monitoring-crd/101.0.0+up19.0.3/crd-manifest
customresourcedefinition.apiextensions.k8s.io/alertmanagerconfigs.monitoring.coreos.com created
customresourcedefinition.apiextensions.k8s.io/alertmanagers.monitoring.coreos.com created
customresourcedefinition.apiextensions.k8s.io/podmonitors.monitoring.coreos.com created
customresourcedefinition.apiextensions.k8s.io/probes.monitoring.coreos.com created
customresourcedefinition.apiextensions.k8s.io/prometheuses.monitoring.coreos.com created
customresourcedefinition.apiextensions.k8s.io/prometheusrules.monitoring.coreos.com created
customresourcedefinition.apiextensions.k8s.io/servicemonitors.monitoring.coreos.com created
customresourcedefinition.apiextensions.k8s.io/thanosrulers.monitoring.coreos.com created
arvindiyengar: ~/Rancher/charts/src/github.com/rancher/charts
$ kubectl delete -Rf --ignore-not-found=true charts/rancher-monitoring-crd/101.0.0+up19.0.3/crd-manifest
the path "--ignore-not-found=true" does not exist
arguments in resource/name form may not have more than one slash
```
Since it is invalid to place `--ignore-not-found=true` after `-Rf`, I'm just switching the order to be successful.