The recommended Kubernetes/OpenShift deployment of StackState is a production ready setup with many services running redundantly. If required, it is also possible to run StackState in a non-redundant setup, where each service has only a single replica.
The non-high availability setup is only suitable for situations that do not require high availability.
Create nonha_values.yaml
To deploy StackState in a non-high availability setup, you will need a nonha_values.yaml file. Follow the instructions below to create this file and use it for deployment of StackState.
1.
Create a Helm values file nonha_values.yaml with the following content and store it next to the generated values.yaml file:
1
# This files defines additional Helm values to run StackState on a
2
# non-high availability production setup. Use this file in combination
3
# with a regular values.yaml file that contains your API key, etc.
4
elasticsearch:
5
minimumMasterNodes:1
6
replicas:1
7
8
hbase:
9
hbase:
10
master:
11
replicaCount:1
12
regionserver:
13
replicaCount:1
14
hdfs:
15
datanode:
16
replicaCount:1
17
secondarynamenode:
18
enabled:false
19
tephra:
20
replicaCount:1
21
22
kafka:
23
replicaCount:1
24
defaultReplicationFactor:1
25
offsetsTopicReplicationFactor:1
26
transactionStateLogReplicationFactor:1
27
stackstate:
28
components:
29
ui:
30
replicaCount:1
31
32
zookeeper:
33
replicaCount:1
Copied!
2.
Continue with the instructions to deploy StackState with Helm: