# Automated Diagnostics
Kubernetes is an open-source platform that allows for the management on a containers on a large scale. Developers, IT administrators, and DevOps engineers use Kubernetes to automate the deployment, scaling, maintenance, scheduling, and operation of "containerized" applications and services. Kubernetes is frequently used for managing microservices applications with multiple service instances, where each microservice is deployed in an individual container.
# Troubleshooting Kubernetes
Because of so many moving components, it is sometimes difficult to pin down the root cause of an issue for an application running on Kubernetes. Unintended behavior could be isolated to a single container, one or more pods, a controller, control-plane components or one of the underlying infrastructure components.
Because some organizations only have a handful of Kubernetes experts on staff, this results in frequent escalations to these experts or prolonged incidents while non-experts try to diagnose issues.
In order to effectively troubleshoot issues in Kubernetes, teams must be equipped with the right tooling that spreads expert-level knowledge and reduces silos between application-development teams and their counterparts in Operations.
# Plugins for Kubernetes
There are numerous plugins that make it possible to get started quickly with Auto-Diagnostics in Kubernetes:
- Kubernetes Pods - Resource Model (opens new window)
- Kubernetes Node Executor (opens new window)
- Check on a Kubernetes Deployment (opens new window)
It is also very common for users to want to “wrap around” the Kubernetes command-line
# Template Job: Recent Pod logs and Kubernetes Events
When an issue arises with applications deployed in Kubernetes, one of the first common actions taken by engineers is to check the health of Pods. If any pods are "unhealthy," then the engineer will look at recent logs and Kubernetes Events pertaining to the unhealthy pods.
To do this troubleshooting effectively not only requires the right set of permissions, but also involves multiple commands that require a decent familiarity with Kubernetes.
Here is an example Job that retrieves recent Pod logs and Kubernetes events - specifically for unhealthy pods - using
Right click here (opens new window) and click
Save Link As... to download the Job definition YAML and import the Job to your Automation instance.