andata
/
rancher-charts
mirror of https://git.rancher.io/charts
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Generated changes

pull/758/head
actions 2020-10-02 16:27:21 +00:00
parent 4915ff8f5b
commit 1ae77fed59
9 changed files with 15 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
assets/index.yaml
View File

@ -350,7 +350,7 @@ entries:
catalog.cattle.io/ui-component: monitoring
apiVersion: v1
appVersion: 0.38.1
created: "2020-10-02T00:27:03.599551291Z"
created: "2020-10-02T16:27:20.573030514Z"
dependencies:
- condition: kubeStateMetrics.enabled
name: kube-state-metrics
@ -446,7 +446,7 @@ entries:
description: Collects several related Helm charts, Grafana dashboards, and Prometheus
rules combined with documentation and scripts to provide easy to operate end-to-end
Kubernetes cluster monitoring with Prometheus using the Prometheus Operator.
digest: ab2bbd414a62fd706910d66d1652f8634f4be04f6cc9c8a331069e2edaa0eee8
digest: 8664d8f7e730f0624dac7cb0771620895cf3811f9576a31541b4a3792551c9a2
home: https://github.com/prometheus-operator/kube-prometheus
icon: https://raw.githubusercontent.com/prometheus/prometheus.github.io/master/assets/prometheus_logo-cb55bb5c346.png
keywords:
@ -479,9 +479,9 @@ entries:
catalog.cattle.io/namespace: cattle-monitoring-system
catalog.cattle.io/release-name: rancher-monitoring-crd
apiVersion: v1
created: "2020-10-02T00:27:03.605372342Z"
created: "2020-10-02T16:27:20.579976815Z"
description: Installs the CRDs for rancher-monitoring.
digest: 80eaab5390ad86ed71b67b66540a55412e88253c1e37a5de2e844a238905c8a5
digest: e37dc98ff3a064a4f08d223c8bccdd6327525e241d8e72f97dc710e3159940e4
name: rancher-monitoring-crd
type: application
urls:
@ -585,4 +585,4 @@ entries:
urls:
- assets/rio/rio-0.8.000.tgz
version: 0.8.000
generated: "2020-10-02T00:27:03.573562166Z"
generated: "2020-10-02T16:27:20.548677712Z"

BIN
assets/rancher-monitoring/rancher-monitoring-9.4.200.tgz
View File

Binary file not shown.

BIN
assets/rancher-monitoring/rancher-monitoring-crd-9.4.200.tgz
View File

Binary file not shown.

2
charts/rancher-monitoring/CHANGELOG.md
View File

@ -9,7 +9,7 @@ All notable changes from the upstream Prometheus Operator chart will be added to
- Added support for `k3sControllerManager`, `k3sScheduler`, and `k3sProxy` PushProx exporters for monitoring k8s components within k3s clusters
- Added support for `kubeAdmControllerManager`, `kubeAdmScheduler`, `kubeAdmProxy`, and `kubeAdmEtcd` PushProx exporters for monitoring k8s components within kubeAdm clusters
- Added support for `rke2ControllerManager`, `rke2Scheduler`, `rke2Proxy`, and `rke2Etcd` PushProx exporters for monitoring k8s components within rke2 clusters
- Exposed `prometheus.prometheusSpec.ignoreNamespaceSelectors` on values.yaml and set it to `true` by default. This value instructs the default Prometheus server deployed with this chart to ignore the `namespaceSelector` field within any created ServiceMonitor or PodMonitor CRs that it selects. This prevents ServiceMonitors and PodMonitors from configuring the Prometheus scrape configuration to monitor resources outside the namespace that they are deployed in; if a user needs to have one ServiceMonitor / PodMonitor monitor resources within several namespaces, they will need to either disable this default option or create one ServiceMonitor / PodMonitor CR per namespace that they would like to monitor. Relevant fields were also updated in the default README.md
- Exposed `prometheus.prometheusSpec.ignoreNamespaceSelectors` on values.yaml and set it to `false` by default. This value instructs the default Prometheus server deployed with this chart to ignore the `namespaceSelector` field within any created ServiceMonitor or PodMonitor CRs that it selects. This prevents ServiceMonitors and PodMonitors from configuring the Prometheus scrape configuration to monitor resources outside the namespace that they are deployed in; if a user needs to have one ServiceMonitor / PodMonitor monitor resources within several namespaces (such as the resources that are used to monitor Istio in a default installation), they should not enable this option since it would require them to create one ServiceMonitor / PodMonitor CR per namespace that they would like to monitor. Relevant fields were also updated in the default README.md.
- Added `grafana.sidecar.dashboards.searchNamespace` to `values.yaml` with a default value of `cattle-dashboards`. The namespace provided should contain all ConfigMaps with the label `grafana_dashboard` and will be searched by the Grafana Dashboards sidecar for updates. The namespace specified is also created along with this deployment. All default dashboard ConfigMaps have been relocated from the deployment namespace to the namespace specified
- Added `monitoring-admin`, `monitoring-edit`, and `monitoring-view` default `ClusterRoles` to allow admins to assign roles to users to interact with Prometheus Operator CRs. These can be enabled by setting `.Values.global.rbac.userRoles.create` (default: `true`). In a typical RBAC setup, you might want to use a `ClusterRoleBinding` to bind these roles to a Subject to allow them to set up or view `ServiceMonitors` / `PodMonitors` / `PrometheusRules` and view `Prometheus` or `Alertmanager` CRs across the cluster. If `.Values.global.rbac.userRoles.aggregateRolesForRBAC` is enabled, these ClusterRoles will aggregate into the respective default ClusterRoles provided by Kubernetes
- Added `monitoring-config-admin`, `monitoring-config-edit` and `monitoring-config-view` default `Roles` to allow admins to assign roles to users to be able to edit / view `Secrets` and `ConfigMaps` within the `cattle-monitoring-system` namespace. These can be enabled by setting `.Values.global.rbac.userRoles.create` (default: `true`). In a typical RBAC setup, you might want to use a `RoleBinding` to bind these roles to a Subject within the `cattle-monitoring-system` namespace to allow them to modify Secrets / ConfigMaps tied to the deployment, such as your Alertmanager Config Secret.

BIN
charts/rancher-monitoring/charts/rancher-pushprox-0.1.0.tgz
View File

Binary file not shown.

2
charts/rancher-monitoring/requirements.lock
View File

@ -57,4 +57,4 @@ dependencies:
repository: file://../../rancher-pushprox/charts
version: 0.1.0
digest: sha256:816a7b6760971acf88b62b4178a5d8919cb97b6576cdca22021137929b1ed031
generated: "2020-10-02T00:26:55.306803187Z"
generated: "2020-10-02T16:27:12.603362637Z"

2
charts/rancher-monitoring/values.yaml
View File

@ -2124,7 +2124,7 @@ prometheus:
## Ignore NamespaceSelector settings from the PodMonitor and ServiceMonitor configs
## If true, PodMonitors and ServiceMonitors can only discover Pods and Services within the namespace they are deployed into
##
ignoreNamespaceSelectors: true
ignoreNamespaceSelectors: false
## Define which Nodes the Pods are scheduled on.
## ref: https://kubernetes.io/docs/user-guide/node-selection/

10
index.yaml
View File

@ -350,7 +350,7 @@ entries:
catalog.cattle.io/ui-component: monitoring
apiVersion: v1
appVersion: 0.38.1
created: "2020-10-02T00:27:03.599551291Z"
created: "2020-10-02T16:27:20.573030514Z"
dependencies:
- condition: kubeStateMetrics.enabled
name: kube-state-metrics
@ -446,7 +446,7 @@ entries:
description: Collects several related Helm charts, Grafana dashboards, and Prometheus
rules combined with documentation and scripts to provide easy to operate end-to-end
Kubernetes cluster monitoring with Prometheus using the Prometheus Operator.
digest: ab2bbd414a62fd706910d66d1652f8634f4be04f6cc9c8a331069e2edaa0eee8
digest: 8664d8f7e730f0624dac7cb0771620895cf3811f9576a31541b4a3792551c9a2
home: https://github.com/prometheus-operator/kube-prometheus
icon: https://raw.githubusercontent.com/prometheus/prometheus.github.io/master/assets/prometheus_logo-cb55bb5c346.png
keywords:
@ -479,9 +479,9 @@ entries:
catalog.cattle.io/namespace: cattle-monitoring-system
catalog.cattle.io/release-name: rancher-monitoring-crd
apiVersion: v1
created: "2020-10-02T00:27:03.605372342Z"
created: "2020-10-02T16:27:20.579976815Z"
description: Installs the CRDs for rancher-monitoring.
digest: 80eaab5390ad86ed71b67b66540a55412e88253c1e37a5de2e844a238905c8a5
digest: e37dc98ff3a064a4f08d223c8bccdd6327525e241d8e72f97dc710e3159940e4
name: rancher-monitoring-crd
type: application
urls:
@ -585,4 +585,4 @@ entries:
urls:
- assets/rio/rio-0.8.000.tgz
version: 0.8.000
generated: "2020-10-02T00:27:03.573562166Z"
generated: "2020-10-02T16:27:20.548677712Z"

4
sha256sum/rancher-monitoring/rancher-monitoring.sum
View File

@ -1,10 +1,10 @@
ef03cc1278c0b75fb92012a5136500f5c2bdce9129d2c66c9c9ceec45021cc45 packages/rancher-monitoring/overlay/charts/grafana/templates/nginx-config.yaml
909d2625c716cebb846218604f54369de9436729133004d041b65ec7345d618f packages/rancher-monitoring/overlay/app-README.md
60dddc3209e3be9974a35bac31cfe580a777be98fc6618be95224aed5f3cfd0d packages/rancher-monitoring/overlay/CHANGELOG.md
e0eddabe716afe6e14b6e82adc0275e4b1406b8347dbd37852ce5295965ded9a packages/rancher-monitoring/overlay/CHANGELOG.md
af335d5859f759a451fb6590d1865b3fb49459c50ba002b6791fb3ddb5a36865 packages/rancher-monitoring/overlay/templates/prometheus/nginx-config.yaml
5ad9876026208a86d66a2ae78ed5d0789ac5aa490cf126b47f73a9919bd37b47 packages/rancher-monitoring/overlay/templates/rancher-monitoring/dashboard-role.yaml
bb4f6fc55612f35e086c1b5657fc1ca356f8c3add72145a39e1d6202a4d40ebe packages/rancher-monitoring/overlay/templates/rancher-monitoring/config-role.yaml
20ce89ac7421675c54005889cdeba74fe2d08442f4c1ecaf76138bf99c81e9d5 packages/rancher-monitoring/overlay/templates/rancher-monitoring/default-dashboard.yaml
582dce5bad0b69f3b576baca91e9a590d8306fb6a423773f3169e77d0b0c796a packages/rancher-monitoring/overlay/templates/rancher-monitoring/clusterrole.yaml
5cf5a67ca2d52d08147201514f872f7fe6c8f099f55b2aba206e039b6220a851 packages/rancher-monitoring/package.yaml
3773eb96662776d1da1b3127620a0eeb6ccfbb8cbfc6cf3aaf8c090cc1660ff5 packages/rancher-monitoring/rancher-monitoring.patch
648db85abcb871c047b5e3bacd8a0ff1b79fd40a192149b73403fcbd58098278 packages/rancher-monitoring/rancher-monitoring.patch