Jaeger operator role resources (#11596)

* Add jobs and cronjobs resources to jaeger operator role

Signed-off-by: Arief Rahmansyah <ariefrahmansyah@hotmail.com>

* Bump jaeger-operator version

Signed-off-by: Arief Rahmansyah <ariefrahmansyah@hotmail.com>

* Add new api groups for jobs and cron jobs role

Signed-off-by: Arief Rahmansyah <ariefrahmansyah@hotmail.com>
This commit is contained in:
Arief Rahmansyah
2019-02-22 06:37:04 -08:00
committed by Kubernetes Prow Robot
parent 5058299a82
commit 58ec0e8048
3 changed files with 15 additions and 8 deletions
+1 -1
View File
@@ -1,7 +1,7 @@
apiVersion: v1
description: jaeger-operator Helm chart for Kubernetes
name: jaeger-operator
version: 2.2.0
version: 2.2.1
appVersion: 1.9.0
home: https://www.jaegertracing.io/
icon: https://www.jaegertracing.io/img/jaeger-icon-reverse-color.svg
+8 -7
View File
@@ -43,17 +43,18 @@ The following table lists the configurable parameters of the jaeger-operator cha
Parameter | Description | Default
--- | --- | ---
`image.repository` | controller container image repository | `jaegertracing/jaeger-operator`
`image.tag` | controller container image tag | `1.9.0`
`image.pullPolicy` | controller container image pull policy | `IfNotPresent`
`rbac.create` | all required roles and SA will be created | `true`
`resources` | k8s pod resorces | `None`
`image.repository` | Controller container image repository | `jaegertracing/jaeger-operator`
`image.tag` | Controller container image tag | `1.9.0`
`image.pullPolicy` | Controller container image pull policy | `IfNotPresent`
`rbac.create` | All required roles and rolebindings will be created | `true`
`serviceAccount.create` | Service account to use | `true`
`serviceAccount.name` | Service account name to use. If not set and create is true, a name is generated using the fullname template | ``
`resources` | K8s pod resorces | `None`
`nodeSelector` | Node labels for pod assignment | `{}`
`tolerations` | Toleration labels for pod assignment | `[]`
`affinity` | Affinity settings for pod assignment | `{}`
Specify each parameter you'd like to override using a YAML file as described above in the [installation](#Installing the Chart) section.
Specify each parameter you'd like to override using a YAML file as described above in the [installation](#installing-the-chart) section.
You can also specify any non-array parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
@@ -43,4 +43,10 @@ rules:
- ingresses
verbs:
- "*"
- apiGroups:
- batch
resources:
- jobs
- cronjobs
verbs: ["get", "list", "watch", "create", "update", "patch", "delete"]
{{- end }}