Quick start guide
StackState v6.0
Last updated
StackState v6.0
StackState v6.0
Last updated
When your StackState SaaS instance has been set up and configured, you will receive an email from StackState with the required login details. This quick start guide will help you get started and get your own data into your StackState SaaS instance.
To integrate your cluster(s) with StackState you can follow one of these guides for your appropriate environment.
Set up a Kubernetes integration to collect topology, events, logs, change and metrics data from a Kubernetes cluster and make this available in StackState.
Kubernetes 1.30
Kubernetes 1.29
Kubernetes 1.28
Kubernetes 1.27
Kubernetes 1.26
Kubernetes 1.25
Kubernetes 1.24
Kubernetes 1.23
Kubernetes 1.22
Kubernetes 1.21
Docker
ContainerD
CRI-O
To set up a StackState Kubernetes integration you need to have:
An up-and-running Kubernetes Cluster.
A recent version of Helm 3.
A user with the permission to create privileged pods, ClusterRoles and ClusterRoleBindings:
ClusterRole and ClusterRoleBinding are needed to grant StackState Agents permissions to access the Kubernetes API.
StackState Agents need to run in a privileged pod to be able to gather information on network connections and host information.
To get data from a Kubernetes cluster into StackState, follow the steps described below:
Add the StackState helm repository to the local helm client:
In the StackState UI, open the main menu by clicking in the top left of the screen and go to StackPacks > Integrations > Kubernetes.
Install a new instance of the Kubernetes StackPack:
Specify a Kubernetes Cluster Name
This name will be used to identify the cluster in StackState
Click install.
Deploy the StackState Agent, Cluster Agent, Checks Agent and kube-state-metrics on your Cluster using the helm command provided in the StackState UI after you have installed the StackPack.
Once the Agents have been deployed, they will begin collecting data and push this to StackState
Set up an OpenShift integration to collect topology, events, logs, change and metrics data from a OpenShift cluster and make this available in StackState.
OpenShift 4.12
Kubernetes 1.25
July 17, 2024
OpenShift 4.11
Kubernetes 1.24
February 10, 2024
OpenShift 4.10
Kubernetes 1.23
September 10, 2023
OpenShift 4.9
Kubernetes 1.22
April 18, 2023
Docker
ContainerD
CRI-O
To set up a StackState OpenShift integration you need to have:
An up-and-running OpenShift Cluster.
A recent version of Helm 3.
A user with the permission to create privileged pods, ClusterRoles and ClusterRoleBindings:
ClusterRole and ClusterRoleBinding are needed to grant StackState Agents permissions to access the Kubernetes API.
StackState Agents need to run in a privileged pod to be able to gather information on network connections and host information.
To get data from a Kubernetes cluster into StackState, follow the steps described below:
Add the StackState helm repository to the local helm client:
In the StackState UI, open the main menu by clicking in the top left of the screen and go to StackPacks > Integrations > Kubernetes.
Install a new instance of the Kubernetes StackPack:
Specify a Kubernetes Cluster Name
This name will be used to identify the cluster in StackState
Click install.
Deploy the StackState Agent, Cluster Agent, Checks Agent and kube-state-metrics on your Cluster using the helm command provided in the StackState UI after you have installed the StackPack.
Once the Agents have been deployed, they will begin collecting data and push this to StackState
Set up an Amazon EKS integration to collect topology, events, logs, change and metrics data from an Amazon EKS cluster and make this available in StackState.
1.30
May 23, 2024
July 23, 2025
July 23, 2026
1.29
January 23, 2024
March 23, 2025
March 23, 2026
1.28
September 26, 2023
November 01, 2024
November 26, 2025
1.27
May 24, 2023
July 2024
July 24, 2025
1.26
April 11, 2023
June 2024
June 11, 2025
1.25
February 21, 2023
May 2024
May 1, 2025
1.24
November 15, 2022
January 2024
January 31, 2025
1.23
August 11, 2022
October 11, 2023
October 11, 2024
1.22
April 4, 2022
June 4, 2023
September 1, 2024
1.21
July 19, 2021
February 15, 2023
July 15, 2024
1.20
May 18, 2021
November 1, 2022
N/A
1.19
February 16, 2021
August 1, 2022
N/A
1.18
October 13, 2020
August 15, 2022
N/A
Docker
ContainerD
CRI-O
To set up a StackState Amazon EKS integration you need to have:
An up-and-running Amazon EKS Cluster.
A recent version of Helm 3.
A user with the permission to create privileged pods, ClusterRoles and ClusterRoleBindings:
ClusterRole and ClusterRoleBinding are needed to grant StackState Agents permissions to access the Kubernetes API.
StackState Agents need to run in a privileged pod to be able to gather information on network connections and host information.
To get data from a Kubernetes cluster into StackState, follow the steps described below:
Add the StackState helm repository to the local helm client:
In the StackState UI, open the main menu by clicking in the top left of the screen and go to StackPacks > Integrations > Kubernetes.
Install a new instance of the Kubernetes StackPack:
Specify a Kubernetes Cluster Name
This name will be used to identify the cluster in StackState
Click install.
Deploy the StackState Agent, Cluster Agent, Checks Agent and kube-state-metrics on your Cluster using the helm command provided in the StackState UI after you have installed the StackPack.
Once the Agents have been deployed, they will begin collecting data and push this to StackState
Set up a Google GKE integration to collect topology, events, logs, change and metrics data from an Google GKE cluster and make this available in StackState.
1.30
June, 2024
August 15, 2025
1.29
January 25, 2024
March 21, 2025
1.28
December 4, 2023
February 4, 2025
1.27
June 14, 2023
August 31, 2024
1.26
April 14, 2023
June 30, 2024
Docker
ContainerD
CRI-O
To set up a StackState Google GKE integration you need to have:
An up-and-running Google GKE Cluster.
A recent version of Helm 3.
A user with the permission to create privileged pods, ClusterRoles and ClusterRoleBindings:
ClusterRole and ClusterRoleBinding are needed to grant StackState Agents permissions to access the Kubernetes API.
StackState Agents need to run in a privileged pod to be able to gather information on network connections and host information.
To get data from a Kubernetes cluster into StackState, follow the steps described below:
Add the StackState helm repository to the local helm client:
In the StackState UI, open the main menu by clicking in the top left of the screen and go to StackPacks > Integrations > Kubernetes.
Install a new instance of the Kubernetes StackPack:
Specify a Kubernetes Cluster Name
This name will be used to identify the cluster in StackState
Click install.
Deploy the StackState Agent, Cluster Agent, Checks Agent and kube-state-metrics on your Cluster using the helm command provided in the StackState UI after you have installed the StackPack.
Once the Agents have been deployed, they will begin collecting data and push this to StackState
Set up an Azure AKS integration to collect topology, events, logs, change and metrics data from an Azure AKS cluster and make this available in StackState.
1.30
June 2024
Not known when published
1.29
March 18, 2024
Jan 31, 2025
1.28
November 7, 2023
November 30, 2024
1.27
August 16, 2023
July 31, 2024
Docker
ContainerD
CRI-O
To set up a StackState Azure AKS integration you need to have:
An up-and-running Azure AKS Cluster.
A recent version of Helm 3.
A user with the permission to create privileged pods, ClusterRoles and ClusterRoleBindings:
ClusterRole and ClusterRoleBinding are needed to grant StackState Agents permissions to access the Kubernetes API.
StackState Agents need to run in a privileged pod to be able to gather information on network connections and host information.
To get data from a Kubernetes cluster into StackState, follow the steps described below:
Add the StackState helm repository to the local helm client:
In the StackState UI, open the main menu by clicking in the top left of the screen and go to StackPacks > Integrations > Kubernetes.
Install a new instance of the Kubernetes StackPack:
Specify a Kubernetes Cluster Name
This name will be used to identify the cluster in StackState
Click install.
Deploy the StackState Agent, Cluster Agent, Checks Agent and kube-state-metrics on your Cluster using the helm command provided in the StackState UI after you have installed the StackPack.
Once the Agents have been deployed, they will begin collecting data and push this to StackState
Set up a KOPS integration to collect topology, events, logs, change and metrics data from an KOPS cluster and make this available in StackState.
Kubernetes 1.30
Kubernetes 1.29
Kubernetes 1.28
Kubernetes 1.27
Kubernetes 1.26
Kubernetes 1.25
Kubernetes 1.24
Kubernetes 1.23
Kubernetes 1.22
Kubernetes 1.21
Kubernetes 1.20
Kubernetes 1.19
Kubernetes 1.18
Kubernetes 1.17
Kubernetes 1.16
Docker
ContainerD
CRI-O
To set up a StackState KOPS integration you need to have:
An up-and-running KOPS Cluster.
A recent version of Helm 3.
A user with the permission to create privileged pods, ClusterRoles and ClusterRoleBindings:
ClusterRole and ClusterRoleBinding are needed to grant StackState Agents permissions to access the Kubernetes API.
StackState Agents need to run in a privileged pod to be able to gather information on network connections and host information.
To get data from a Kubernetes cluster into StackState, follow the steps described below:
Add the StackState helm repository to the local helm client:
In the StackState UI, open the main menu by clicking in the top left of the screen and go to StackPacks > Integrations > Kubernetes.
Install a new instance of the Kubernetes StackPack:
Specify a Kubernetes Cluster Name
This name will be used to identify the cluster in StackState
Click install.
Deploy the StackState Agent, Cluster Agent, Checks Agent and kube-state-metrics on your Cluster using the helm command provided in the StackState UI after you have installed the StackPack.
Once the Agents have been deployed, they will begin collecting data and push this to StackState
Set up a Self-hosted integration to collect topology, events, logs, change and metrics data from an Self-hosted cluster and make this available in StackState.
Kubernetes 1.30
Kubernetes 1.29
Kubernetes 1.28
Kubernetes 1.27
Kubernetes 1.26
Kubernetes 1.25
Kubernetes 1.24
Kubernetes 1.23
Kubernetes 1.22
Kubernetes 1.21
Kubernetes 1.20
Kubernetes 1.19
Kubernetes 1.18
Kubernetes 1.17
Kubernetes 1.16
Docker
ContainerD
CRI-O
To set up a StackState Self-hosted integration you need to have:
An up-and-running Self-hosted Cluster.
A recent version of Helm 3.
A user with the permission to create privileged pods, ClusterRoles and ClusterRoleBindings:
ClusterRole and ClusterRoleBinding are needed to:
Grant StackState Agents permissions to access the Kubernetes API
StackState Agents need to run in a privileged pod to be able to gather information on network connections and host information.
To get data from a Kubernetes cluster into StackState, follow the steps described below:
Add the StackState helm repository to the local helm client:
In the StackState UI, open the main menu by clicking in the top left of the screen and go to StackPacks > Integrations > Kubernetes.
Install a new instance of the Kubernetes StackPack:
Specify a Kubernetes Cluster Name
This name will be used to identify the cluster in StackState
Click install.
Deploy the StackState Agent, Cluster Agent, Checks Agent and kube-state-metrics on your Cluster using the helm command provided in the StackState UI after you have installed the StackPack.
Once the Agents have been deployed, they will begin collecting data and push this to StackState
Before you begin, check the .
When running on a self-hosted air-gapped environment prepare the agent installation first with the .
Before you begin, check the .
Before you begin, check the .
Before you begin, check the .
Before you begin, check the .
Before you begin, check the .
Generate a secret for the mutating validation webhook which is part of
Before you begin, check the .