gha-runner-scale-set-controller imagePullSecrets w/ custom actions-runners on github.com enterprise work? #2835
-
Folks, I was wondering if any has gotten the newer GH Actions runner Scale-Set-Controller to pull custom actions-runner from a private container registry (in this case ghcr.io/MyOrg/actions-runner:v2.0 ? gha-runner-scale-set-controller - v.0.5.0 I've read thru all the newer documentation on Github Scale Sets: My config for the Scale-Set controller looks like this: githubConfigUrl: "https://github.com/MyOrg"
githubConfigSecret: "gha-myorg-secret"
runnerGroup: "infra-runner-grp"
maxRunners: 6
minRunners: 1
imagePullSecrets:
- name: "arc-regcred"
containerMode:
type: "kubernetes"
kubernetesModeWorkVolumeClaim:
accessModes: ["ReadWriteOnce"]
storageClassName: "longhorn"
resources:
requests:
storage: 1Gi
template:
spec:
containers:
- name: runner
#image: ghcr.io/actions/actions-runner:latest
image: ghcr.io/myorg/actions-runner:v2.0
imagePullPolicy: IfNotPresent
command: ["/home/runner/run.sh"]
env:
- name: ACTIONS_RUNNER_REQUIRE_JOB_CONTAINER
value: "false"
controllerServiceAccount:
namespace: arc-systems
name: arc-serviceaccount It works perfectly fine if i use image: ghcr.io/actions/actions-runner:latest however there is some additional software and a private CA I add (/usr/local/share/ca-certificates) I'd like to add so we don't have wait during deployment. Any suggestion would be most appreciated... Kind regards,
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Well.. it turns out I had the ImagepullSecrets in the wrong section of the myscaleset.yml.. reviewing other standard k8s pod deployment... Now is working... |
Beta Was this translation helpful? Give feedback.
Well.. it turns out I had the ImagepullSecrets in the wrong section of the myscaleset.yml..
reviewing other standard k8s pod deployment...
template:
spec:
imagePullSecrets:
- name: arc-regcred
Now is working...