Non-high availability setup
StackState Self-hosted v5.1.x
The recommended Kubernetes/OpenShift deployment of StackState is a production ready setup with many services running redundantly. If required, it's also possible to run StackState in a non-redundant setup, where each service has only a single replica.
To deploy StackState in a non-high availability setup, you will need a
nonha_values.yamlfile. Follow the instructions below to create this file and use it for deployment of StackState.
- 1.Create a Helm values file
nonha_values.yamlwith the following content and store it next to the generated
values.yamlfile:# This files defines additional Helm values to run StackState on a# non-high availability production setup. Use this file in combination# with a regular values.yaml file that contains your API key, etc.elasticsearch:minimumMasterNodes: 1replicas: 1hbase:hbase:master:replicaCount: 1regionserver:replicaCount: 1hdfs:datanode:replicaCount: 1secondarynamenode:enabled: falsetephra:replicaCount: 1kafka:replicaCount: 1defaultReplicationFactor: 1offsetsTopicReplicationFactor: 1transactionStateLogReplicationFactor: 1stackstate:components:ui:replicaCount: 1zookeeper:replicaCount: 1