Kubernetes integration
Monitor cluster health and automate container operations directly from service tickets.
What it connects
- Live pod status, restart counts, container logs, and crash events across all namespaces.
- Node inventory with capacity, resource allocation, and hardware condition alerts.
- Deployment replica counts, rollout progress, and update history to track application state.
- Service endpoints and network configuration to map inter-application dependencies.
What it automates
- Restart pods and trigger deployment rollouts to recover from failures without manual intervention.
- Cordon and uncordon nodes during maintenance to gracefully reschedule workloads.
- Scale deployments up or down to adjust capacity based on demand or incident response.
- Attach labels and annotations to resources for incident tracking, change management, and operational metadata.
In practice
Pods are crashing. STLabs pulls container logs showing a missing config secret, identifies the deployment that needs a restart, and executes the rollout to recovery.
A node is failing health checks. STLabs cordons the node to stop new scheduling, gracefully evicts its pods to healthy nodes, and opens a maintenance ticket with hardware diagnostics.
Traffic spikes during peak hours. STLabs scales a deployment up via the ticket system, monitors the rollout progress, and scales back down when demand subsides.
An application update is rolled out. STLabs tracks the deployment's replica counts and rollout status, annotates the resources with change ticket IDs, and verifies the new pods are healthy.
