-
Notifications
You must be signed in to change notification settings - Fork 43
[Kubernetes] - missing architecture for amd64 jobs #68
Comments
Since my issue ( harness/harness#2816 )was closed and this issue has been open for a while. Any ideas what's causing this? I've checked and nodeSelector is not set for amd64 jobs. |
I understand that all the contributors might be busy with other stuff, but I'd appreciate some pointers to where the nodeSelector label gets set. It should be an easy fix, I'll be happy to submit a pull request. Sidenote: I am aware of the upcoming Kubernetes run-time changes, and I'm excited for the improvements. But I'd like to continue using Drone on Kubernetes until the new run-time/project is ready since it already works great in my environment. |
In case someone stumbles upon this, I've found a workaround using a Example: kind: pipeline
name: amd64
platform:
os: linux
arch: amd64
+ node:
+ kubernetes.io/arch: amd64
steps:
... |
fixed by drone-runners/drone-runner-kube@971c183 new kubernetes runner documentation can be found here: |
I am running a drone pipeline in a cluster with arm and amd64 nodes. The arm job has the right nodeSelector
but the nodeSelector is missing on the amd64 job. This results on the sometimes job (and its pod) being scheduled in the arm node. Even worse: the steps are then executed in the wrong architecture resulting on invalid docker containers.
I run the same .drone.yml successfully with the cloud.drone.io: https://github.com/angelnu/docker-ioBroker
Here the job in the amd64 node:
The main drone server is deployed to a amd64 node - I am going to check how it looks like when I deploy it to the arm node...
Update: same result after deploying drone/drone:1 to arm. The amd64 is still deployed without a nodeSelector annotation.
The text was updated successfully, but these errors were encountered: