OpenShift

Search…
💠
OpenShift
StackState Self-hosted v4.6.x
Overview
The OpenShift integration is used to create a near real-time synchronization of topology and associated internal services from an OpenShift cluster to StackState. This StackPack allows monitoring of the following:
Workloads
Nodes, pods, containers and services
Configmaps, secrets and volumes
OpenShift is a StackState core integration.
Data flow
The OpenShift integration collects topology data in an OpenShift cluster as well as metrics and events.
Data is retrieved by the deployed StackState Agents and then pushed to StackState via the Agent StackPack and the OpenShift StackPack.
In StackState:
​Topology data is translated into components and relations.
​Tags defined in OpenShift are added to components and relations in StackState.
Relevant metrics data is mapped to associated components and relations in StackState. All retrieved metrics data is stored and accessible within StackState.
​OpenShift events are available in the StackState UI Events Perspective and listed in the details pane on the right of the StackState UI.
​Objects changes events are created for every detected change to spec or metadata in OpenShift objects
Setup
Prerequisites
The following prerequisites are required to install the OpenShift StackPack and deploy the StackState Agent and Cluster Agent:
An OpenShift Cluster must be up and running.
A recent version of Helm 3.
A user with permissions to create privileged pods, ClusterRoles, ClusterRoleBindings and SCCs:
ClusterRole and ClusterRoleBinding are needed to grant StackState Agents permissions to access the OpenShift API.
StackState Agents need to run in a privileged pod to be able to gather information on network connections and host information.
Supported container runtimes
From StackState Agent v2.16, the following container runtimes are supported:
containerd
CRI-O
Docker
Note that versions of StackState Agent prior to v2.16 support the Docker container runtime only.
Install
Install the OpenShift StackPack from the StackState UI StackPacks > Integrations screen. You will need to provide the following parameters:
OpenShift Cluster Name - A name to identify the cluster. This does not need to match the cluster name used in kubeconfig, however, that is usually a good candidate for a unique name.
If the Agent StackPack is not already installed, this will be automatically installed together with the OpenShift StackPack. This is required to work with the StackState Agent, which will need to be deployed on each node in the OpenShift cluster.
Deploy: Agent and Cluster Agent
For the OpenShift integration to retrieve topology, events and metrics data, you will need to have the following installed on your OpenShift cluster:
StackState Agent V2 on each node in the cluster
StackState Cluster Agent on one node
kube-state-metrics
➡️ Deploy StackState Agents and kube-state-metrics.
To integrate with other services, a separate instance of the StackState Agent should be deployed on a standalone VM. It is not currently possible to configure a StackState Agent deployed on an OpenShift cluster with checks that integrate with other services.
Configure cluster check: Kubernetes_state check
The kubernetes_state check is responsible for gathering metrics from kube-state-metrics and sending them to StackState. It is configured on the StackState Cluster Agent and, by default, runs in the StackState Agent pod that is on the same node as the kube-state-metrics pod.
In a default deployment, all pods running a StackState Agent must be configured with sufficient CPU and memory requests and limits to run the check. This can consume a lot of memory in a large OpenShift cluster. Since only one StackState Agent pod will actually run the check, a lot of CPU and memory resources will be allocated, but not be used.
To remedy this situation, the kubernetes_state check can be configured to run as a cluster check. In this case, only the ClusterCheck Agent requires resources to run the check and the allocation for other pods can be reduced.
1.Update the values.yaml file used to deploy the cluster-agent, for example:
1
clusterChecks:
2
# clusterChecks.enabled -- Enables the cluster checks functionality _and_ the clustercheck pods.
3
  enabled: true
4
agent:
5
  config:
6
    override:
7
# agent.config.override -- Disables kubernetes_state check on regular agent pods.
8
    - name: auto_conf.yaml
9
      path: /etc/stackstate-agent/conf.d/kubernetes_state.d
10
      data: |
11
clusterAgent:
12
  config:
13
    override:
14
# clusterAgent.config.override -- Defines kubernetes_state check for clusterchecks agents. Auto-discovery
15
#                                 with ad_identifiers does not work here. Use a specific URL instead.
16
    - name: conf.yaml
17
      path: /etc/stackstate-agent/conf.d/kubernetes_state.d
18
      data: |
19
        cluster_check: true
20
​
21
        init_config:
22
​
23
        instances:
24
          - kube_state_url: http://YOUR_KUBE_STATE_METRICS_SERVICE_NAME:8080/metrics
Copied!
1.Deploy the cluster_agent using the updated values.yaml:
1
helm upgrade --install \
2
--namespace stackstate \
3
--create-namespace \
4
--set-string 'stackstate.apiKey'='<your-api-key>' \
5
--set-string 'stackstate.cluster.name'='<your-cluster-name>' \
6
--set-string 'stackstate.cluster.authToken=<your-cluster-token>' \
7
--set-string 'stackstate.url'='<stackstate-receiver-api-address>' \
8
--set 'agent.scc.enabled'=true \
9
--set 'kube-state-metrics.securityContext.enabled'=false \
10
--values values.yaml \
11
stackstate-cluster-agent stackstate/cluster-agent    
Copied!
Status
To check the status of the OpenShift integration, check that the StackState Cluster Agent (cluster-agent) pod and all of the StackState Agent (cluster-agent-agent) pods have status ready.
1
❯ kubectl get deployment,daemonset --namespace stackstate
2
​
3
NAME                                                 READY   UP-TO-DATE   AVAILABLE   AGE
4
deployment.apps/stackstate-cluster-agent             1/1     1            1           5h14m
5
NAME                                                 DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR   AGE
6
daemonset.apps/stackstate-cluster-agent-agent        10        10        10      10           10          <none>          5h14m
Copied!
Integration details
Data retrieved
The OpenShift integration retrieves the following data:
​Events​
​Metrics​
​Tags​
​Topology​
Events
The OpenShift integration retrieves all OpenShift events from the OpenShift cluster. In addition to this, Element Properties Change events will be generated in StackState for changes in Kubernetes objects.
OpenShift events
The OpenShift integration retrieves all events from the OpenShift cluster. The table below shows which event category will be assigned to each event type in StackState:
StackState event category
OpenShift events
Text
Activities
BackOff ContainerGCFailed ExceededGracePeriod FileSystemResizeSuccessful ImageGCFailed Killing NodeAllocatableEnforced NodeNotReady NodeSchedulable Preempting Pulling Pulled Rebooted Scheduled Starting Started SuccessfulAttachVolume SuccessfulDetachVolume SuccessfulMountVolume SuccessfulUnMountVolume VolumeResizeSuccessful
​
Alerts
NotTriggerScaleUp
​
Changes
Created (created container) NodeReady SandboxChanged SuccesfulCreate
​
Others
All other events
​
Object change events
The OpenShift integration will detect changes in OpenShift objects and will create an event of type Element Properties Change with a diff with a YAML representation of the changed object.
Element Properties Change event
Changes will be detected in the following object types:
ConfigMap
CronJob
DaemonSet
Deployment
Ingress
Job
Namespace
Node
PersistentVolume
Pod
ReplicaSet
Secret (a hash of the content will be compared)
Service
StatefulSet
Note that, in order to reduce noise of changes, the following object properties will not be compared:
metadata
managedFields
resourceVersion
annotations
kubectl.kubernetes.io/last-applied-configuration
status (except for Node, Pod and PersistentVolume objects)
You can also see current (or past) YAML definition of the object in the "Component properties":
OpenShift Component properties
Metrics
The OpenShift integration makes all metrics from the OpenShift cluster available in StackState. Relevant metrics are automatically mapped to the associated components.
All retrieved metrics can be browsed or added to a component as a telemetry stream. Select the data source StackState Metrics and type kubernetes in the Select box to get a full list of all available metrics.
Add an OpenShift metrics stream to a component
Topology
The OpenShift integration retrieves components and relations for the OpenShift cluster.
StackState Agent versions prior to 2.16: Topology information is only gathered from OpenShift clusters that use the Docker container runtime.
Components
The following OpenShift topology data is available in StackState as components:
Cluster
Ingress
Namespace
Job
Node
Persistent Volume
Pod
ReplicaSet
Container
Secret
ConfigMap
Service
CronJob
StatefulSet
DaemonSet
Volume
Deployment
​
Relations
The following relations between components are retrieved:
Container → PersistentVolume, Volume
CronJob → Job
DaemonSet → Pod
Deployment → ReplicaSet
Job → Pod
Ingress → Service
Namespace → CronJob, DaemonSet, Deployment, Job, ReplicaSet, Service, StatefulSet
Node → Cluster relation
Pod → ConfigMap, Container, Deployment, Node, PersistentVolume, Secret, Volume
ReplicaSet → Pod
Service → ExternalService, Pod
StatefulSet → Pod
Direct communication between processes
Process → Process communication via OpenShift service
Process → Process communication via headless OpenShift service
Traces
The OpenShift integration does not retrieve any traces data.
Tags
All tags defined in OpenShift will be retrieved and added to the associated components and relations in StackState.
REST API endpoints
The StackState Agent talks to the kubelet and kube-state-metrics API.
The StackState Agent and Cluster Agent connect to the OpenShift API to retrieve cluster wide information and OpenShift events. The following API endpoints used:
Resource type
REST API endpoint
Metadata > ComponentStatus
GET /api/v1/componentstatuses
Metadata > ConfigMap
GET /api/v1/namespaces/{namespace}/configmaps
Metadata > Event
GET /apis/events.k8s.io/v1/events
Metadata > Namespace
GET /api/v1/namespaces
Network > Endpoints
GET /api/v1/namespaces/{namespace}/endpoints
Network > Ingress
GET /apis/networking.k8s.io/v1/namespaces/{namespace}/ingresses
Network > Service
GET /api/v1/namespaces/{namespace}/services
Node > Node
GET /api/v1/nodes
Security > Secret
GET /api/v1/secrets
Storage > PersistentVolumeClaimSpec
GET /api/v1/namespaces/{namespace}/persistentvolumeclaims
Storage > VolumeAttachment
GET /apis/storage.k8s.io/v1/volumeattachments
Workloads > CronJob
GET /apis/batch/v1beta1/namespaces/{namespace}/cronjobs
Workloads > DaemonSet
GET /apis/apps/v1/namespaces/{namespace}/daemonsets
Workloads > Deployment
GET /apis/apps/v1/namespaces/{namespace}/deployments
Workloads > Job
GET /apis/batch/v1/namespaces/{namespace}/jobs
Workloads > PersistentVolume
GET /api/v1/persistentvolumes
Workloads > Pod
GET /api/v1/namespaces/{namespace}/pods
Workloads > ReplicaSet
GET /apis/apps/v1/namespaces/{namespace}/replicasets
Workloads > StatefulSet
GET /apis/apps/v1/namespaces/{namespace}/statefulsets
​
/version
For further details, refer to the OpenShift API documentation (openshift.com).
Component actions
A number of actions are added to StackState when the OpenShift StackPack is installed. They are available from the Actions section on the right of the screen when an OpenShift component is selected or from the component context menu, displayed when you hover over an OpenShift component in the Topology Perspective
Action
Available for component types
Description
Show configuration and storage
pods containers
Display the selected pod or container with its configmaps, secrets and volumes
Show dependencies (deep)
deployment replicaset replicationcontroller statefulset daemonset job cronjob pod
Displays all dependencies (up to 6 levels deep) of the selected pod or workload.
Show pods
deployment replicaset replicationcontroller statefulset daemonset job cronjob
Displays the pods for the selected workload.
Show pods & services
namespace
Opens a view for the pods/services in the selected namespace
Show services
namespace
Open a view for the service and ingress components in the selected namespace
Show workloads
namespace
Show workloads in the selected namespace
Details of installed actions can be found in the StackState UI Settings > Actions > Component Actions screen.
OpenShift views in StackState
When the OpenShift integration is enabled, the following OpenShift views are available in StackState for each cluster:
OpenShift - Applications -
OpenShift - Infrastructure -
OpenShift - Namespaces -
OpenShift - Workload Controllers -
Open source
The code for the StackState Agent OpenShift check is open source and available on GitHub at:
​https://github.com/StackVista/stackstate-agent/tree/master/pkg/collector/corechecks/cluster​
​https://github.com/stackvista/stackstate-agent​
​https://github.com/StackVista/stackstate-agent-integrations/tree/master/kubernetes​
Troubleshooting
Troubleshooting steps for any known issues can be found in the StackState support Knowledge base.
Uninstall
To uninstall the OpenShift StackPack, go to the StackState UI StackPacks > Integrations > OpenShift screen and click UNINSTALL. All OpenShift StackPack specific configuration will be removed from StackState.
To uninstall the StackState Cluster Agent and the StackState Agent from your OpenShift cluster, run a Helm uninstall:
1
helm uninstall <release_name> --namespace <namespace>
2
​
3
# If you used the standard install command provided when you installed the StackPack
4
helm uninstall stackstate-cluster-agent --namespace stackstate
Copied!
Release notes
OpenShift StackPack v3.7.10 (2022-03-02)
Improvement: Documentation for agent.containerRuntime.customSocketPath option.
OpenShift StackPack v3.7.9 (2021-11-30)
Bug Fix: Support nodes without instanceId
OpenShift StackPack v3.7.8 (2021-10-06)
Bug Fix: Fix metrics for generic events
OpenShift StackPack v3.7.7 (2021-08-20)
Improvement: Add description to Views
OpenShift StackPack v3.7.5 (2021-07-14)
Improvement: Documentation update
Improvement: Update of stackstate.url for the installation documentation of the StackState Agent
See also
​Agent StackPack​
​StackState Agent Kubernetes check (github.com)​
​StackState Cluster Agent Helm Chart (github.com)​
​OpenShift API documentation (openshift.com)​