Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Autoscaling #11

Open
fnmarquez opened this issue Jul 30, 2021 · 1 comment
Open

Autoscaling #11

fnmarquez opened this issue Jul 30, 2021 · 1 comment
Labels
enhancement New feature or request

Comments

@fnmarquez
Copy link

Is it possible to autoscale runners on demand? (not manually from the workflow)

@fnmarquez fnmarquez added the question Further information is requested label Jul 30, 2021
@tetchel
Copy link
Contributor

tetchel commented Jul 30, 2021

There is no auto-scaling feature at this time.

Something you can do is patch the deployment as needed. Depending on your needs you could do something like scale it up or down during certain times of day (using a cron workflow) or maybe at the beginning/end of a workflow run.

You can patch the replicas count as follows:

$ oc patch deployment actions-runner-1627686781  -p '{ "spec": { "replicas": 2 } }'
deployment.apps/actions-runner-1627686781 patched
$ oc get deploy
NAME                        READY   UP-TO-DATE   AVAILABLE   AGE
actions-runner-1627686781   1/2     2            1           3m37s

The deployment name is the same as the Helm release name, or you can do:

oc get deploy -l=app.kubernetes.io/instance=$RELEASE_NAME

@tetchel tetchel added enhancement New feature or request and removed question Further information is requested labels Jul 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants