@kapa.ai, are there some connectors which does not support arm64 architecture?

Based on the knowledge sources, there are known architecture compatibility issues with certain Airbyte components and connectors on ARM64, though the sources don't provide a definitive list of which specific connectors lack ARM64 support. Here's what is documented: ARM64 Compatibility Issues Normalization Images The normalization step has been a known problem area on ARM64 systems. Specifically: •

airbyte/normalization-snowflake

caused

exec format error

on ARM64 EKS nodes [Snowflake Normalization Issue] •

airbyte/normalization-mysql

showed the same

Exec format error

on an Oracle ARM Ampere A1 instance [MySQL Normalization Error] Custom Connectors Built on Apple Silicon Custom connectors built on M1/M2 Macs (ARM64) without multi-arch support will fail when deployed to AMD64 servers, and vice versa. The fix is to use Docker Buildx to build multi-architecture images: [Custom Connector ARM Issue]

docker buildx build --platform linux/amd64 --push -t repo/image-name:tag .

Kubernetes Workload Pods on ARM64 Nodes In EKS/Kubernetes deployments, workload pods (check, replication, normalization) may be scheduled on ARM64 nodes and fail if the images don't support that architecture. A common workaround is to force scheduling on AMD64 nodes: [EKS Pod Failure]

global:
  jobs:
    kube:
      nodeSelector:
        kubernetes.io/arch: amd64

What Airbyte Does for Official Connectors Official Airbyte connector images are built for both

linux/amd64

and

linux/arm64

using their CI pipeline. [Connector Build Action] However, the knowledge sources do not provide a comprehensive list of which specific connectors may still lack ARM64 support. If you're hitting issues with a specific connector on ARM64, checking the connector's Docker Hub manifest or the Airbyte GitHub issues would be the best approach. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.