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.

Sign up for GitHub

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

Jump to bottom

create an ARM64 nodepool on publick8s to start using arm64 pods #3584

Closed
smerle33 opened this issue May 15, 2023 · 2 comments
Closed

create an ARM64 nodepool on publick8s to start using arm64 pods #3584

smerle33 opened this issue May 15, 2023 · 2 comments
Assignees
@smerle33
Labels
aws azure billing-report
Milestone
infra-team-sync-2...

Comments

@smerle33
Copy link
Contributor

smerle33 commented May 15, 2023 •
edited

Service(s)

AZURE

Summary

this will allow us to lower the cost on AZURE (#3551), we could try with the build of javadoc on ARM

Reproduction steps

No response
@smerle33 smerle33 added the triage Incoming issues that need review label May 15, 2023
@dduportal dduportal removed the triage Incoming issues that need review label May 23, 2023
@dduportal dduportal added this to the infra-team-sync-2023-05-30 milestone May 23, 2023
@smerle33 smerle33 mentioned this issue May 29, 2023
Merged
dduportal added a commit to jenkins-infra/azure that referenced this issue May 31, 2023
@smerle33 @dduportal
feat(publick8s): add an ARM cluster node pool (#369)
49202bc 
as per jenkins-infra/helpdesk#3584
create an ARM pool based on
[Standard_D8ps_v5](https://learn.microsoft.com/en-us/azure/virtual-machines/dv5-dsv5-series#dsv5-series)

---------

Co-authored-by: Damien Duportal <damien.duportal@gmail.com>
@lemeurherve lemeurherve mentioned this issue Jun 1, 2023
Merged
@smerle33 smerle33 mentioned this issue Jun 5, 2023
Merged
@smerle33
Copy link
Contributor Author

smerle33 commented Jun 5, 2023

impossible to scale up, fail with this message :

"statusMessage": "{\"status\":\"Failed\",\"error\":{\"code\":\"ResourceOperationFailure\",\"message\":\"The resource operation completed with terminal provisioning state 'Failed'.\",\"details\":[{\"code\":\"OverconstrainedZonalAllocationRequest\",\"target\":\"11\",\"message\":\"Allocation failed. VM(s) with the following constraints cannot be allocated, because the condition is too restrictive. Please remove some constraints and try again. Constraints applied are:\\n - Availability Zone\\n - Differencing (Ephemeral) Disks\\n - Networking Constraints (such as Accelerated Networking or IPv6)\\n - VM Size\\n\"}]}}",

Allocation failed. VM(s) with the following constraints cannot be allocated, because the condition is too restrictive. Please remove some constraints and try again. Constraints applied are:

  • Availability Zone
  • Differencing (Ephemeral) Disks
  • Networking Constraints (such as Accelerated Networking or IPv6)
  • VM Size

smerle33 added a commit to jenkins-infra/azure that referenced this issue Jun 5, 2023
@smerle33
feat(publick8s): arm64 nodes only available in zone 1
955fadd 
as per jenkins-infra/helpdesk#3584
@smerle33 smerle33 mentioned this issue Jun 5, 2023
Merged
dduportal pushed a commit to jenkins-infra/azure that referenced this issue Jun 5, 2023
@smerle33
feat(publick8s): arm64 nodes only available in zone 1 (#390)
53f415b 
as per jenkins-infra/helpdesk#3584
@smerle33
Copy link
Contributor Author

smerle33 commented Jun 6, 2023

ARM machines Standard_D4pds_v5 not available in zone 3.

@smerle33 smerle33 mentioned this issue Jun 6, 2023
Merged
@smerle33 smerle33 closed this as completed Jun 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@smerle33 smerle33

Labels
aws azure billing-report
Projects
None yet
Milestone
infra-team-sync-2023-06-06
Development

No branches or pull requests
3 participants
@MarkEWaite @dduportal @smerle33