StackState Self-hosted v4.6.x
This page describes StackState version 4.6.
All of StackState's own components can run without any extra permissions. However in order to install StackState successfully, you need some additional privileges, or ensure that the requirements described in this page are met.
In order to run the Autonomous Anomaly Detector, or prepare your Kubernetes cluster to run it, StackState needs to create a
ClusterRoleBindingresources. Creating these cluster-wide resources is often prohibited for users that are not a Kubernetes administrator.
The automatic creation of cluster-wide resources during installation of StackState can be disabled by adding the following section to the
values.yamlfile used to install StackState:
Note that if automatic creation of cluster-wide resources is disabled the Autonomous Anomaly Detector will NOT be able to authenticate against the running StackState installation unless you manually create the cluster-wide resources.
If you need to manually create the cluster-wide resources, ask your Kubernetes administrator to create the 3 resources below in the Kubernetes cluster.
Ensure that you specify the correct namespace for the bound
ServiceAccountfor both of the
- kind: ServiceAccount
- kind: ServiceAccount
StackState uses Elasticsearch to store its indices. There are some additional requirements for the nodes that Elasticsearch runs on.
vm.max_map_countLinux system setting is usually lower than required for Elasticsearch to start, an init container is used that runs in privileged mode and as the root user. The init container is enabled by default to allow the
vm.max_map_countsystem setting to be changed.
In case you and/or your Kubernetes administrators do not want the privileged Elasticsearch init container to be enabled by default, you can disable this behavior in the file
values.yamlused to install StackState:
If this is disabled, you will need to ensure that the
vm.max_map_countsetting is changed from its common default value of
262144. If this is not done, Elasticsearch will fail to start up and its pods will be in a restart loop.
To inspect the current
vm.max_map_countsetting, run the following command. Note that it runs a privileged pod:
kubectl run -i --tty sysctl-check-max-map-count --privileged=true --image=busybox --restart=Never --rm=true -- sysctl vm.max_map_count
If the current
vm.max_map_countsetting is not at least
262144, it will need to be increased in a different way or Elasticsearch will fail to start up and its pods will be in a restart loop. The logs will contain an error message like this:
bootstrap checks failed
max virtual memory areas vm.max_map_count  is too low, increase to at least 
Depending on what your Kubernetes administrators prefer, the
vm.max_map_countcan be set to a higher default on all nodes by either changing the default node configuration (for example via init scripts) or by having a DaemonSet do this right after node startup. The former is very dependent on your Kubernetes cluster setup, so there are no general solutions there.
Below is an example that can be used as a starting point for a DaemonSet to change the
# Make sure the setting always gets changed as soon as possible:
- effect: NoSchedule
- effect: NoExecute
# Optional node selector (assumes nodes for Elasticsearch are labeled `elastichsearch:yes`
# elasticsearch: yes
- name: set-vm-max-map-count
command: ["sysctl", "-w", "vm.max_map_count=262144"]
# A pause container is needed to prevent a restart loop of the pods in the daemonset
# See also this Kubernetes issue https://github.com/kubernetes/kubernetes/issues/36601
- name: pause
To limit the number of nodes that this is applied to, nodes can be labeled. NodeSelectors on both this DaemonSet, as shown in the example, and the Elasticsearch deployment can then be set to run only on nodes with the specific label. For Elasticsearch, the node selector can be specified via the values: