Skip to content

[WIP] fix fleeting plugin installation for docker autoscaler #1260

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

Open
wants to merge 7 commits into
base: main
Choose a base branch
from

Conversation

daveaie
Copy link

@daveaie daveaie commented Mar 4, 2025

Description

Hello everyone,

i have pushed 3 improvement to use docker autoscaler gitlub runner:

  • [WIP] install fleeting plugin for gitlab runner 17.x as explained here : I marked it as WIP because it might be necessary to add a condition on the GitLab Runner version used to apply the correct installation method, but I'm not sure it's needed.
  • Fixed the name assignment to distinguish the runner manager from the runner worker in EC2 instances, as requested in this issue
  • add variable to set delete instances (runner worker) on shut down runner manager

Migrations required

No migration required.

Verification

I'm using my version of this module in our gitlab on premise installation since a week.

The reason I implemented this fix is that with the old installation method of the fleeting plugin, the runners did not scale down correctly as indicated in this issue

@daveaie daveaie requested review from npalm and kayman-mk as code owners March 4, 2025 21:51
Copy link
Contributor

github-actions bot commented Mar 4, 2025

Hey @daveaie! 👋

Thank you for your contribution to the project. Please refer to the contribution rules for a quick overview of the process.

Make sure that this PR clearly explains:

  • the problem being solved
  • the best way a reviewer and you can test your changes

With submitting this PR you confirm that you hold the rights of the code added and agree that it will published under this LICENSE.

The following ChatOps commands are supported:

  • /help: notifies a maintainer to help you out

Simply add a comment with the command in the first line. If you need to pass more information, separate it with a blank line from the command.

This message was generated automatically. You are welcome to improve it.

Copy link
Collaborator

@kayman-mk kayman-mk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great work!

I think we have to check the installation of the plugin. So I prefer to have this in a separate PR and merge the other changes before,


capacity_per_instance = ${runners_capacity_per_instance}
update_interval = "${runners_update_interval}"
update_interval_when_expecting = "${runners_update_interval_when_expecting}"

delete_instances_on_shutdown = ${delete_instances_on_shutdown}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thought: does this make our Lambda function superfluous? We have it to kill the instances on shutdown of the agent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants