Fix several chart problems (#18430)

Signed-off-by: vas <vasily.sliouniaev@jet.com>
This commit is contained in:
Vasily Sliouniaev
2019-11-02 12:27:39 -07:00
committed by Kubernetes Prow Robot
parent edecc9842d
commit 6d22112751
8 changed files with 33 additions and 16 deletions
@@ -3,7 +3,6 @@
1. Fork this repository, develop and test your Chart.
1. Bump the chart version for every change.
1. Ensure PR title has the prefix `[stable/prometheus-operator]`
1. When making changes to values.yaml, update the files in `ci/` by running `hack/update-ci.sh`
1. When making changes to rules or dashboards, see the README.md section on how to sync data from upstream repositories
1. Check the `hack/minikube` folder has scripts to set up minikube and components of this chart that will allow all components to be scraped. You can use this configuration when validating your changes.
1. Check for changes of RBAC rules.
+1 -1
View File
@@ -11,7 +11,7 @@ name: prometheus-operator
sources:
- https://github.com/coreos/prometheus-operator
- https://coreos.com/operators/prometheus
version: 7.3.0
version: 7.4.0
appVersion: 0.34.0
tillerVersion: ">=2.12.0"
home: https://github.com/coreos/prometheus-operator
+6 -3
View File
@@ -171,14 +171,17 @@ The following tables list the configurable parameters of the prometheus-operator
| `prometheusOperator.configmapReloadImage.repository` | Repository for configmapReload image | `quay.io/coreos/configmap-reload` |
| `prometheusOperator.configmapReloadImage.tag` | Tag for configmapReload image | `v0.0.1` |
| `prometheusOperator.createCustomResource` | Create CRDs. Required if deploying anything besides the operator itself as part of the release. The operator will create / update these on startup. If your Helm version < 2.10 you will have to either create the CRDs first or deploy the operator first, then the rest of the resources | `true` |
| `prometheusOperator.denyNamespaces` | Namespaces not to scope the interaction of the Prometheus Operator (deny list). | `{}` |
| `prometheusOperator.namespaces` | Namespaces to scope the interaction of the Prometheus Operator and the apiserver (allow list). This is mutually exclusive with `denyNamespaces`. Setting this to an empty object will disable the configuration | `{}` |
| `prometheusOperator.namespaces.releaseNamespace` | Include the release namespace | `false` |
| `prometheusOperator.namespaces.additional` | Include additional namespaces besides the release namespace | `[]` |
| `prometheusOperator.denyNamespaces` | Namespaces not to scope the interaction of the Prometheus Operator (deny list). This is mutually exclusive with `namespaces` | `[]` |
| `prometheusOperator.enabled` | Deploy Prometheus Operator. Only one of these should be deployed into the cluster | `true` |
| `prometheusOperator.hyperkubeImage.repository` | Image pull policy for hyperkube image used to perform maintenance tasks | `IfNotPresent` |
| `prometheusOperator.hyperkubeImage.repository` | Repository for hyperkube image used to perform maintenance tasks | `k8s.gcr.io/hyperkube` |
| `prometheusOperator.hyperkubeImage.tag` | Tag for hyperkube image used to perform maintenance tasks | `v1.12.1` |
| `prometheusOperator.image.pullPolicy` | Pull policy for prometheus operator image | `IfNotPresent` |
| `prometheusOperator.image.repository` | Repository for prometheus operator image | `quay.io/coreos/prometheus-operator` |
| `prometheusOperator.image.tag` | Tag for prometheus operator image | `v0.32.0` |
| `prometheusOperator.image.tag` | Tag for prometheus operator image | `v0.33.0` |
| `prometheusOperator.kubeletService.enabled` | If true, the operator will create and maintain a service for scraping kubelets | `true` |
| `prometheusOperator.kubeletService.namespace` | Namespace to deploy kubelet service | `kube-system` |
| `prometheusOperator.logFormat` | Operator log output formatting | `"logfmt"` |
@@ -188,7 +191,7 @@ The following tables list the configurable parameters of the prometheus-operator
| `prometheusOperator.podLabels` | Labels to add to the operator pod | `{}` |
| `prometheusOperator.priorityClassName` | Name of Priority Class to assign pods | `nil` |
| `prometheusOperator.prometheusConfigReloaderImage.repository` | Repository for config-reloader image | `quay.io/coreos/prometheus-config-reloader` |
| `prometheusOperator.prometheusConfigReloaderImage.tag` | Tag for config-reloader image | `v0.32.0` |
| `prometheusOperator.prometheusConfigReloaderImage.tag` | Tag for config-reloader image | `v0.33.0` |
| `prometheusOperator.resources` | Resource limits for prometheus operator | `{}` |
| `prometheusOperator.securityContext` | SecurityContext for prometheus operator | `{"runAsNonRoot": true, "runAsUser": 65534}` |
| `prometheusOperator.service.annotations` | Annotations to be added to the prometheus operator service | `{}` |
@@ -29,8 +29,14 @@ defaultRules:
# Default configuration of prometheus operator will create CRDs in the cluster idempotently
prometheusOperator:
enabled: true
serviceMonitor:
selfMonitor: false
createCustomResource: false
tlsProxy:
enabled: false
admissionWebhooks:
enabled: false
namespaces:
releaseNamespace: true
additional:
- kube-system
@@ -1,2 +1,6 @@
prometheusOperator:
createCustomResource: false
namespaces:
releaseNamespace: true
additional:
- kube-system
@@ -1,6 +0,0 @@
#!/usr/bin/env bash
sed \
-e 's/createCustomResource: true/createCustomResource: false/' \
-e 's/port: 9100/port: 9101/' \
-e 's/targetPort: 9100/targetPort: 9101/' \
values.yaml > ci/02-test-without-crds-values.yaml
@@ -45,6 +45,13 @@ spec:
{{- end }}
{{- if .Values.prometheusOperator.denyNamespaces }}
- --deny-namespaces={{ .Values.prometheusOperator.denyNamespaces | join "," }}
{{- end }}
{{- with $.Values.prometheusOperator.namespaces }}
{{ $ns := .additional }}
{{- if .releaseNamespace }}
{{- $ns = append $ns $.Release.Namespace }}
{{- end }}
- --namespaces={{ $ns | join "," }}
{{- end }}
- --logtostderr=true
- --localhost=127.0.0.1
+9 -5
View File
@@ -932,10 +932,6 @@ nodeExporter:
## Configuration for prometheus-node-exporter subchart
##
prometheus-node-exporter:
service:
port: 9100
targetPort: 9100
podLabels:
## Add the 'node-exporter' label to be used by serviceMonitor to match standard common usage in rules and grafana dashboards
##
@@ -978,9 +974,17 @@ prometheusOperator:
podAnnotations: {}
nodeSelector: {}
## Namespaces to scope the interaction of the Prometheus Operator and the apiserver (allow list).
## This is mutually exclusive with denyNamespaces. Setting this to an empty object will disable the configuration
##
namespaces: {}
# releaseNamespace: true
# additional:
# - kube-system
## Namespaces not to scope the interaction of the Prometheus Operator (deny list).
##
denyNamespaces: {}
denyNamespaces: []
## Service account for Alertmanager to use.
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/