-
-
Notifications
You must be signed in to change notification settings - Fork 10
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
[ci.jenkins.io] Use DigitalOcean VM agents instead of container agents #3576
Comments
uh oh, does that mean i actually have to help out on that plugin again? I'm a terrible plugin maintainer. |
|
snapshot template have been created within digital ocean called locally with |
Delaying: no bandwidth on the upcoming milestone |
Service(s)
ci.jenkins.io, DigitalOcean
Summary
The past 4 months events showed that using Kuberenetes agents in DigitalOcean for ci.jenkins.io is not the most efficient way to spend our credits and is also limited on some features.
336$ per month (4k$ per year, for a credit of 18k$)As pointed out by @halkeye months ago, we could use DigitalOcean with VM agents instead.
Major elements to consider:
instanceCap
attribute looks like configurable on both cloud and templates levelsusePrivateNetworking
indicates that https://docs.digitalocean.com/products/networking/vpc/ could be used BUT it does not looks like that inbound protocol is a feature (ping @halkeye : is SSH required?) so we'll be stuck with Public IP to allow ci.jenkins.io to access the agent with SSH (not mentioning the need for 1/2 egress IPs)InitScript
attribute: would be useful for setting up datadog agent (and custom stuff)Reproduction steps
No response
The text was updated successfully, but these errors were encountered: