This message was deleted.

Here are some troubleshooting steps based on the known issues and documentation: 1. Check the dataplane_group_id Configuration A common cause of connection pods not launching (resulting in

0 bytes | no records loaded

or pods simply not starting) is a misconfigured

dataplane_group_id

. This is especially relevant if you recently upgraded from Airbyte v1 to v2. [GitHub issue] Fix: Add the following to your Helm values before upgrading or redeploying:

global:
  dataplaneGroups:
    defaultDataplaneGroupName: "AUTO"

Or, if you're on v2, use

"default"

instead of

"AUTO"

. You can also directly update the

dataplane_group_id

in the

public.workspace

table to match an enabled entry in

public.dataplane_group

. [GitHub issue] 2. Verify Pods Are Running Run the following to check pod status:

kubectl get pods -n airbyte
kubectl -n airbyte get events --sort-by='{.lastTimestamp}'

Look for pods stuck in

Pending

or

Init

states, which may indicate resource or volume provisioning issues. [EKS deploy issue] 3. Check Logs from the Right Containers For sync pods, the

orchestrator

container is the one that aggregates human-readable logs — the

source

and

destination

containers use stdout for Airbyte protocol messages and won't have useful logs there. [log collection docs]

# Find workload pods
kubectl get pods -l airbyte=job-pod --all-namespaces

# Check orchestrator logs
kubectl logs <pod-name> -c orchestrator -n <namespace>

For check/discover/spec pods, check the

sidecar

container instead. [log collection docs] 4. Set Up a Log Collector If you're not seeing logs in your observability stack, you may need to deploy a DaemonSet-based log collector (e.g., Fluent Bit, Vector, or Datadog Agent) to collect stdout from your pods. Note that Airbyte data plane Helm chart v2.1.0+ is required for structured JSON logging. [log collection docs] > Important for Fluent Bit users: Set

Buffer_Size 256k

on the Kubernetes filter, as the default 32KB is too small for Airbyte workload pod metadata, causing label enrichment to silently fail. [log collection docs] 5. Check MinIO Storage Space If you see log file paths referenced (e.g.,

/tmp/workspace/.../logs.log

) but the message says "No logs available," you may need to increase the storage space allocated to MinIO (

/storage

path). [K8s no logs forum] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.