any thing worng? NAME READY STATUS RESTARTS AGE airbyte-abctl-bootloader 0/1 Completed 0 26d airbyte-abctl-cron-b6df94fbb-5bdnt 1/1 Running 4 (2m ago) 26d airbyte-abctl-manifest-server-5857bb75f9-xwttl 1/1 Running 4 (2m ago) 26d airbyte-abctl-server-ddf787dcc-v2mn5 1/1 Running 4 (2m ago) 26d airbyte-abctl-temporal-5c67b77849-tf798 1/1 Running 4 (2m ago) 26d airbyte-abctl-worker-7945b979d6-27cq6 1/1 Running 4 (2m ago) 26d airbyte-abctl-workload-api-server-579b6c4fd8-2x426 1/1 Running 4 (2m ago) 26d airbyte-abctl-workload-launcher-68b4ddf95b-dcks6 1/1 Running 8 (81s ago) 26d airbyte-db-0 1/1 Running 4 (2m ago) 26d

Thinking completed Based on the provided output, there are two primary observations: 1. The bootloader status is normal The

airbyte-abctl-bootloader

pod has a status of

Completed

(0/1). This is normal and expected behavior. The bootloader runs initialization tasks and database migrations at startup, then terminates successfully once finished [Common Errors]. 2. Recent container restarts across all active pods There is an issue indicating instability: • Simultaneous Restarts: Almost all running pods (

cron

,

manifest-server

,

server

,

temporal

,

worker

,

workload-api-server

, and

airbyte-db-0

) restarted approximately 2 minutes ago (each showing

4 (2m ago)

). • Workload Launcher Flapping:

airbyte-abctl-workload-launcher

has restarted 8 times, most recently only 81 seconds ago. A simultaneous restart across all services—including the database—usually points to host-level issues rather than a single component failure. Common causes include: • Out of Memory (OOM): The host node or Docker engine ran out of memory, causing containers to be killed (e.g., OOMKilled) or the Docker daemon/Kind node to restart [Github Issue (closed): Cannot use Airbyte on Kubernetes due to OOM when setting up connector; Github Issue (closed): [abctl] Unending "DEBUG helm: Deployment is not ready: airbyte-abctl/airbyte-abctl-server. 0 out of 1 expected pods are ready"]. • Host Reboot or Docker Restart: The host machine or Docker service itself restarted around 2 minutes ago. • Storage / Disk Pressure: The node may have run out of disk space or experienced storage connectivity disruptions [Github Issue (open): Failed to install airbyte. "pod airbyte-abctl-bootloader failed"; Github Issue (closed): workload-launcher false positive liveness probes under lost storage connection]. Recommended Troubleshooting Steps To find out why the pods restarted: 1. *Check the previous container termination reason:*kubectl describe pod airbyte-abctl-workload-launcher-68b4ddf95b-dcks6 kubectl describe pod airbyte-db-0Look at the

Last State

section for

Reason: OOMKilled

or exit codes (such as

137

). 2. *Check previous logs:*kubectl logs airbyte-abctl-workload-launcher-68b4ddf95b-dcks6 --previous 3. *Check available host memory and disk resources:*free -h df -h docker stats 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.