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.

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

feat(cik8s) add a new 3x node pool dedicated to the bom builds #396

Merged
merged 1 commit into from
Apr 25, 2023

Conversation

dduportal
Copy link
Contributor

@dduportal dduportal commented Apr 25, 2023

Related to jenkins-infra/helpdesk#3521

This PR adds a new node pool on the EKS cluster cik8s.

The goal is, folllowing experiementations in jenkinsci/bom#1969, to reduce the initial scope and deliver the "resource split" between bom and plugins.

Since increasing the size of VM (to execute more pods at the same time) led to contentions not diasgnosed yet, the choice is to keep the same sizing as we have today.

This node pool is reserved for the bom builds on ci.jenkins.io through the use of taints.
The size of the nodes in this new pool is the same as the current node pool used for both plugins and bom builds.

[boyscout improvements]

  • The node label "ci.jenkins.io/agents-density" was missing on the current node pool: it's added (will allow automation of the pod/agents quotas)
  • Update naming convention of the current "big" node pool which is unused so can be updated
  • Updating the .shared-tools dependency

@dduportal
Copy link
Contributor Author

Terraform plan looks good to me:

Plan: 12 to add, 1 to change, 6 to destroy.

=> A given node pool is made of 6 terraform resources (identity, policies, etc.).
=> We change 1 node pool (eg. 6 destroy + 6 add) and add 1 node pool (6 add) + the cluster itself to modify

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