Are those recommendations correct as kubernetes specs?

The knowledge sources show example Kubernetes resource sections from the Airbyte Helm chart values (for jobs, web app, and server) with comments like “Example” and empty

limits: {}

/

requests: {}

blocks. These are syntactically valid Kubernetes resource specs and follow the standard

resources.requests

/

resources.limits

structure. [compose/api issue] However: • They are examples / defaults, not prescriptive sizing guidance. • Airbyte explicitly recommends not setting default resources in the chart so users can tune them based on their own cluster and workloads. [compose/api issue] For actual capacity planning and scaling, Airbyte instead recommends: • Starting with mid-sized instances (4–8 cores) and tuning based on workload. [Scaling Airbyte] • Ensuring enough memory for sync jobs (source worker can hold up to 10,000 records in memory). [Scaling Airbyte] • Ensuring sufficient disk and pod capacity in the cluster. [Scaling Airbyte] So: yes, those snippets are correct as Kubernetes resource spec syntax, but you should treat the values as placeholders and size them according to your own environment and the scaling guidance. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.