feat: add connection_max_age config #1340
Conversation
|
Hey @uosjead! 👋 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:
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:
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. |
| maximum_concurrent_jobs = optional(number, 10) | ||
| prometheus_listen_address = optional(string, "") | ||
| sentry_dsn = optional(string, "__SENTRY_DSN_REPLACED_BY_USER_DATA__") | ||
| connection_max_age = optional(string, "15m") |
There was a problem hiding this comment.
|
Could you please add some context? What problems have you seen? |
Yes - currently seeing some occasional connectivity issues running behind a NAT gateway - where connections are limited to 5 minutes. The gitlab-runner config by defaults limits connections to 15 minutes. Was looking to set the Let me know if you need any further information. |
2 participants
Description
Add connection_max_age as a configurable option to the runner config
Migrations required
No
Verification
Please mention how you test the changes.