Skip to content

Unify ClusterAutoscaler configs#75800

Open
liangxia wants to merge 1 commit intoopenshift:mainfrom
liangxia:cluster-auto-scaler
Open

Unify ClusterAutoscaler configs#75800
liangxia wants to merge 1 commit intoopenshift:mainfrom
liangxia:cluster-auto-scaler

Conversation

@liangxia
Copy link
Member

@liangxia liangxia commented Mar 6, 2026

ClusterAutoscaler is enabled on all of managed build farm clusters, unify the configs from configs inside each of the build farm cluster folder to one config file inside common.

$ for x in app.ci core-ci hosted-mgmt build{01..11} ; do echo "===$x:" ; oc --context $x get clusterautoscaler | grep default ; echo ; done
===app.ci:
default   4y312d

===core-ci:
default   91d

===hosted-mgmt:
default   689d

===build01:
default   6y36d

===build02:
default   272d

===build03:
default   311d

===build04:
default   272d

===build05:
default   100d

===build06:
default   470d

===build07:
default   381d

===build08:
default   164d

===build09:
default   291d

===build10:
default   337d

===build11:
default   412d

Also introduce a new option balanceSimilarNodeGroups: true to let Cluster Autoscaler to provision worker nodes evenly across Availability Zones.

@openshift-ci-robot openshift-ci-robot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Mar 6, 2026
@openshift-ci-robot
Copy link
Contributor

[REHEARSALNOTIFIER]
@liangxia: no rehearsable tests are affected by this change

Note: If this PR includes changes to step registry files (ci-operator/step-registry/) and you expected jobs to be found, try rebasing your PR onto the base branch. This helps pj-rehearse accurately detect changes when the base branch has moved forward.

@openshift-ci openshift-ci bot requested review from deepsm007 and pruan-rht March 6, 2026 10:05
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 6, 2026
@liangxia
Copy link
Member Author

liangxia commented Mar 6, 2026

/hold
Plan to get this in on next Monday.

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 6, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 6, 2026

@liangxia: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@bear-redhat
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 6, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 6, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bear-redhat, liangxia

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. lgtm Indicates that a PR is ready to be merged. rehearsals-ack Signifies that rehearsal jobs have been acknowledged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants