Fedor Barannik

Hey @mumoshu . Thanks for the reply. Is `privileged: false` part of the helm chart? Also, I am reusing the same token if I dont use fargate. I deployed two...

I kinda assumed that I can replica what gitlab ci doing.

I get this error on the runner pod. `actions-runner-controller` is good. It seems that the secret is not being mounted when I use fargate. I am going to try mounting...

I have done a bit more investigating and these are the findings. It looks like runner pod is not mounting secrets when running on fargate. I was able to solve...

OMG! Thanks for pointing out that I was using the wrong image. I am going to update it and redeploy. Will update you shortly!

@mumoshu Here is an updated config which seem to work on fargate: ``` apiVersion: actions.summerwind.dev/v1alpha1 kind: RunnerDeployment metadata: name: 4-10-fargate namespace: github spec: template: metadata: labels: fargate: "true" eks.amazonaws.com/fargate-profile: "github"...

Thanks for the info! Will give this a shot.

@mumoshu Tried your suggestions and removing `runnerForScaleFromToZero.ObjectMeta.Labels = nil` seemed to work! :tada:

Looks like it @mumoshu . Example of nothing running on the ci: ``` NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE 4-10-fargate 0 0 0 0 7m27s ``` Executed one job on...

Just finished running a pipeline with 18 jobs in it and it was able to scale up and down with no issues :tada: