bd00842800
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.
32 lines
1.0 KiB
YAML
32 lines
1.0 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.
|
|
#
|
|
|
|
metadataPrefix: "/cluster1"
|
|
|
|
pulsar_metadata:
|
|
configurationStore: pulsar-cs-zookeeper
|
|
configurationStoreMetadataPrefix: "/configuration-store"
|
|
|
|
## disable pulsar-manager
|
|
components:
|
|
pulsar_manager: true
|
|
|
|
## disable monitoring stack
|
|
kube-prometheus-stack:
|
|
enabled: false |