-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
Agents aren't spawning on infra.ci #3918
Comments
I opened an issue with azure/microsoft, the detail of my ticket are not in the email but the title was: the first feedback is :
if my understanding is correct I probably explained badly the problem, so I replied:
|
We had similar problems with spot instances, if we had it set to 0 it didn't work, whereas 1 did. |
Thanks @timja, I did tell the azure support team I had over on visio, they will look into it, will keep you informed here but it sound right that the spot instance are the trouble here. |
Given we can't afford (in the current subscription) to use non-spot instances, WDYT if we start working on adding a new AKS cluster only for infra.ci.jenkins.io and release.ci.jenkins.io Kubernetes agents in the new "sponsored" subscription. Multiple achievement for us:
If it make sense, I propose to close this issue and track the solution above in a new one (ping @smerle33 if you don't mind writing it). The new issue would need to mention:
|
Is there an issue to just leave 1 spot instance? |
Cost 😅 (but might be OK though @smerle33 do you mind checking the cost?) |
I think its quite acceptable ... less than 15$/month |
…ces nodes (#609) as per jenkins-infra/helpdesk#3918 for the ARM64 node the price for 1 node all month is around 14$: ![image](https://github.com/jenkins-infra/azure/assets/95630726/dcf8a6fc-7432-4710-b7f8-f6fb24b2864d) for the intel node the price for 1 node all month is around 33$: ![image](https://github.com/jenkins-infra/azure/assets/95630726/93fd25e9-426a-4a7a-a703-b4052498ce64)
last answer from microsoft confirm our choice :
|
new answer from microsoft :
|
Isn't it exactly the same response as last week minus the last phrase? ^^ |
Service(s)
infra.ci.jenkins.io
Summary
The build queue counts 30+ items while writing this, but the executor status is stuck in the launching state:
ref https://infra.ci.jenkins.io/job/kubernetes-jobs/job/kubernetes-management/view/change-requests/job/PR-4886/ and other PRs
Reproduction steps
No response
The text was updated successfully, but these errors were encountered: