pulsar-helm-chart/examples/values-bookkeeper-aws.yaml
Michael Marshall bd00842800
Fix monitoring configuration broken by #299 (#313)
Related to #311

### Motivation

In #299, I updated the values without also updating the test values. As a result, I unintentionally enabled the monitoring stack in the tests and broke some examples. Because we are deploying all resources to a single node. It is possible that we are resource constrained, so I am going to re-disable the monitoring stack.

### Modifications

* Update test cluster configurations to re-disable deploying the monitoring stack
* Update examples with the new configuration

### Verifying this change

- [ ] Make sure that the change passes the CI checks.
2022-10-19 22:50:31 -05:00

81 lines
2.3 KiB
YAML

#
# Licensed to the Apache Software Foundation (ASF) under one
# or more contributor license agreements. See the NOTICE file
# distributed with this work for additional information
# regarding copyright ownership. The ASF licenses this file
# to you under the Apache License, Version 2.0 (the
# "License"); you may not use this file except in compliance
# with the License. You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing,
# software distributed under the License is distributed on an
# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
# KIND, either express or implied. See the License for the
# specific language governing permissions and limitations
# under the License.
#
## start
components:
# zookeeper
zookeeper: true
# bookkeeper
bookkeeper: true
# bookkeeper - autorecovery
autorecovery: true
# broker
broker: true
# functions
functions: true
# proxy
proxy: true
# toolset
toolset: false
# pulsar manager
pulsar_manager: false
## disable monitoring stack
kube-prometheus-stack:
enabled: false
zookeeper:
volumes:
# use a persistent volume or emptyDir
persistence: true
data:
name: data
size: 5Gi
local_storage: false
## If you already have an existent storage class and want to reuse it, you can specify its name with the option below
##
storageClassName: gp2
#
## 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:
replicaCount: 3
volumes:
# use a persistent volume or emptyDir
persistence: true
journal:
name: journal
size: 5Gi
local_storage: false
## If you already have an existent storage class and want to reuse it, you can specify its name with the option below
##
storageClassName: gp2
ledgers:
name: ledgers
size: 5Gi
local_storage: false
## If you already have an existent storage class and want to reuse it, you can specify its name with the option below
##
storageClassName: gp2