Local Qovery on M1 Mac: Node(s) didn't match Pod's node affinity/selector

[C_G (Cyrus G)]

I am trying to deploy hasura (hasura/graphql-engine:v2.38.1.ubuntu.arm64) to my local cluster in the qovery demo, but I keep running into the below issue:

“0/1 nodes are available: 1 node(s) didn’t match Pod’s node affinity/selector. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling…”

Based on my research, the issue seems to arise from the deployment yaml’s affinity requirement not matching the labels of my k3 nodes (see below). I am running all this on my M1 Max Macbook Pro, and it doesn’t seem like I can change the kubernetes.io/arch label of the node. I imagine others have ran into this issue with M1 Macs?

affinity:
nodeAffinity:
requiredDuringSchedulingIgnoredDuringExecution:
nodeSelectorTerms:
- matchExpressions:
- key: kubernetes.io/arch
operator: In
values:
- amd64

Labels:
beta.kubernetes.io/arch=arm64
beta.kubernetes.io/instance-type=k3s
beta.kubernetes.io/os=linux
kubernetes.io/arch=arm64
kubernetes.io/hostname=k3d-cyrus-local-cluster-server-0
kubernetes.io/os=linux
node-role.kubernetes.io/control-plane=true
node-role.kubernetes.io/master=true
node.kubernetes.io/instance-type=k3s

[a_carrano (Alessandro Carrano)]

Hi @C_G ,

how did you install the Qovery CLI? (via homebrew, via the curl command provided on our page curl -s https://get.qovery.com | bash )

we have found a bug in the installation process of the script hosted on https://get.qovery.com . if you installed it via this command can you try to re-install the qovery CLI again and re-deploy?