Fix typos in Helm chart and sync values-mini with values (#6009)

### Motivation

Fix typos and sync values-mini with values

### Modifications

Comments only.
This commit is contained in:
Kévin Dunglas 2020-01-11 14:48:44 +01:00 committed by Sijie Guo
parent f76253d699
commit cad175d8e6

View File

@ -21,9 +21,9 @@
namespace: pulsar namespace: pulsar
namespaceCreate: yes namespaceCreate: yes
## If persistence is enabled, components that has state will ## If persistence is enabled, components that have state will
## be deployed with PersistentVolumeClaims, otherwise, for test ## be deployed with PersistentVolumeClaims, otherwise, for test
## purposes, they will be deployed with emptDir ## purposes, they will be deployed with emptyDir
persistence: no persistence: no
## If prometheus_persistence is enabled, prometheus will be deployed ## If prometheus_persistence is enabled, prometheus will be deployed
@ -80,6 +80,17 @@ zookeeper:
data: data:
name: data name: data
size: 2Gi size: 2Gi
## If you already have an existent storage class and want to reuse it, you can specify its name with the option below
##
# storageClassName: existent-storage-class
#
## Instead if you want to create a new storage class define it below
## If left undefined no storage class will be defined along with PVC
##
# storageClass:
# type: pd-ssd
# fsType: xfs
# provisioner: kubernetes.io/gce-pd
## Zookeeper configmap ## Zookeeper configmap
## templates/zookeeper-configmap.yaml ## templates/zookeeper-configmap.yaml
## ##
@ -107,8 +118,8 @@ zookeeper:
maxUnavailable: 1 maxUnavailable: 1
## Pulsar Zookeeper metadata. The metadata will be deployed as ## Pulsar Zookeeper metadata. The metadata will be deployed as
## soon as the las zookeeper node is reachable. The deployment ## soon as the last zookeeper node is reachable. The deployment
## of other components that depends o zookeeper, such as the ## of other components that depends on zookeeper, such as the
## bookkeeper nodes, broker nodes, etc will only start to be ## bookkeeper nodes, broker nodes, etc will only start to be
## deployed when the zookeeper cluster is ready and with the ## deployed when the zookeeper cluster is ready and with the
## metadata deployed ## metadata deployed
@ -139,9 +150,31 @@ bookkeeper:
journal: journal:
name: journal name: journal
size: 5Gi size: 5Gi
## If you already have an existent storage class and want to reuse it, you can specify its name with the option below
##
# storageClassName: existent-storage-class
#
## Instead if you want to create a new storage class define it below
## If left undefined no storage class will be defined along with PVC
##
# storageClass:
# type: pd-ssd
# fsType: xfs
# provisioner: kubernetes.io/gce-pd
ledgers: ledgers:
name: ledgers name: ledgers
size: 5Gi size: 5Gi
## If you already have an existent storage class and want to reuse it, you can specify its name with the option below
##
# storageClassName: existent-storage-class
#
## Instead if you want to create a new storage class define it below
## If left undefined no storage class will be defined along with PVC
##
# storageClass:
# type: pd-ssd
# fsType: xfs
# provisioner: kubernetes.io/gce-pd
## Bookkeeper configmap ## Bookkeeper configmap
## templates/bookkeeper-configmap.yaml ## templates/bookkeeper-configmap.yaml
## ##
@ -290,14 +323,14 @@ dashboard:
annotations: {} annotations: {}
tolarations: [] tolarations: []
gracePeriod: 0 gracePeriod: 0
resources:
requests:
memory: 64Mi
cpu: 0.1
image: image:
repository: apachepulsar/pulsar-dashboard repository: apachepulsar/pulsar-dashboard
tag: latest tag: latest
pullPolicy: IfNotPresent pullPolicy: IfNotPresent
resources:
requests:
memory: 64Mi
cpu: 0.1
## Dashboard service ## Dashboard service
## templates/dashboard-service.yaml ## templates/dashboard-service.yaml
## ##
@ -308,6 +341,18 @@ dashboard:
port: 80 port: 80
ingress: ingress:
enabled: false enabled: false
annotations: {}
tls:
enabled: false
## Optional. Leave it blank if your Ingress Controller can provide a default certificate.
secretName: ""
## Required if ingress is enabled
hostname: ""
path: "/"
port: 80
## Pulsar Extra: Bastion ## Pulsar Extra: Bastion
## templates/bastion-deployment.yaml ## templates/bastion-deployment.yaml
@ -341,19 +386,30 @@ prometheus:
annotations: {} annotations: {}
tolarations: [] tolarations: []
gracePeriod: 0 gracePeriod: 0
resources:
requests:
memory: 64Mi
cpu: 0.1
image: image:
repository: prom/prometheus repository: prom/prometheus
tag: v1.6.3 tag: v1.6.3
pullPolicy: IfNotPresent pullPolicy: IfNotPresent
resources:
requests:
memory: 64Mi
cpu: 0.1
volumes: volumes:
data: data:
name: data name: data
size: 2Gi size: 2Gi
## Prometheus service ## If you already have an existent storage class and want to reuse it, you can specify its name with the option below
##
# storageClassName: existent-storage-class
#
## Instead if you want to create a new storage class define it below
## If left undefined no storage class will be defined along with PVC
##
# storageClass:
# type: pd-standard
# fsType: xfs
# provisioner: kubernetes.io/gce-pd
## Prometheus service
## templates/prometheus-service.yaml ## templates/prometheus-service.yaml
## ##
service: service:
@ -373,15 +429,15 @@ grafana:
annotations: {} annotations: {}
tolarations: [] tolarations: []
gracePeriod: 0 gracePeriod: 0
resources:
requests:
memory: 64Mi
cpu: 0.1
image: image:
repository: apachepulsar/pulsar-grafana repository: apachepulsar/pulsar-grafana
tag: latest tag: latest
pullPolicy: IfNotPresent pullPolicy: IfNotPresent
## Grafana service resources:
requests:
memory: 64Mi
cpu: 0.1
## Grafana service
## templates/grafana-service.yaml ## templates/grafana-service.yaml
## ##
service: service: