Runbook
Airbyte pods using too much disk space and failing to create new connections in Kubernetes cluster.
Back to Runbooks
Overview
This incident type involves Airbyte, a software tool running in a Kubernetes cluster, failing to create new connections as a result of Airbyte pods using too much disk space. This can cause disruptions to the functioning of the software and affect its ability to perform its intended tasks. A runbook needs to be written to clean unnecessary files on Airbyte pods and free up disk space to resolve this issue.
Parameters
Debug
Check the status of the Airbyte pods
Describe the Airbyte pods to get more detailed information about their current state
Check the disk usage of the Airbyte pod in the Kubernetes cluster
List the largest files in the Airbyte pod to identify files that are consuming the most disk space
Check the logs of the Airbyte pod to identify any errors or anomalies that could be causing the issue
Check the Kubernetes events to see if there were any recent events related to the Airbyte pods or the underlying infrastructure
Check the Kubernetes resource usage to identify any resource constraints that could be causing the issue
Print disk usage for each Airbyte pod
Repair
Learn more
Related Runbooks
Check out these related runbooks to help you debug and resolve similar issues.