Replies: 2 comments 2 replies
-
same question here, @shaul75 did you figure out an alternative? |
Beta Was this translation helpful? Give feedback.
-
Hey @shaul75, The reason is that the runner pod doesn't need to communicate with the k8s API in order to run a job. However, to run a job in k8s mode, the runner has to be able to talk to the k8s API. Running in kubernetes mode assumes that the default hook implementation is used, so we tried to provision the role, role binding and the service account for the ephemeral runner pod for you in advance. However, if you need to modify something, you have complete control over the ephemeral runner spec. If defaults provided by the chart are insufficient for your use case, you can keep the container mode commented out, and provide the desired spec |
Beta Was this translation helpful? Give feedback.
-
actions-runner-controller/charts/gha-runner-scale-set/values.yaml
Lines 88 to 90 in d727747
Why not make it simply
serviceAccount: {}
, and have it work regardless of the mode?We need it in dind mode, in order to assign an IAM role to the pod.
It seemed like it was more work and additional complexities to have the chart developed this way, so I'm trying to understand the rationale here.
Beta Was this translation helpful? Give feedback.
All reactions