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

[mce-2.5] Allow MachinePool autoscaler maxReplicas < #AZs #2216

Conversation

openshift-cherrypick-robot
Copy link

@openshift-cherrypick-robot openshift-cherrypick-robot commented Feb 22, 2024

This is an automated cherry-pick of #2215

/assign 2uasimojo

HIVE-2415

Our algorithm to spread MachinePool.Spec.Autoscaling.MinReplicas and
.MaxReplicas across spoke MachineAutoscalers previously assumed that it
was sane to create one MachineAutoscaler per AZ and set maxReplicas to
zero if that's what our computation came out with.

Not so.

MachineAutoscaler.Spec.MaxReplicas -- in contrast to
MachineSet.Spec.Replicas -- is
[not allowed to be zero](https://github.com/openshift/cluster-autoscaler-operator/blob/67999a5e79d0200ee0a4aab3dcfbfd18e097b514/pkg/apis/autoscaling/v1beta1/machineautoscaler_types.go#L18).

The resulting behavior would manifest as a hive-controllers error
similar to:

```
time="2024-02-21T16:33:56.802Z" level=error msg="unable to create machine autoscaler" controller=machinepool error="MachineAutoscaler.autoscaling.openshift.io \"efried-rg2wn-worker-test-us-east-1c\" is invalid: spec.maxReplicas: Invalid value: 0: spec.maxReplicas in body should be greater than or equal to 1" machinePool=efried/efried-worker-test reconcileID=nwpxskln
```

So instead we have to include a special case for this and delete such
MachineAutoscalers instead.

(Further, since this error causes us to bail out of the machinepool
controller's reconcile loop before updating the MachinePool status, the
user doesn't have a great way to discover what went wrong. They just
have to notice that MachineSets et al stop responding. We'll address
this in a separate commit.)

HIVE-2415
@2uasimojo
Copy link
Member

/lgtm

Copy link
Contributor

openshift-ci bot commented Feb 22, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 2uasimojo, openshift-cherrypick-robot

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

The pull request process is described here

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

@openshift-ci openshift-ci bot added approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. labels Feb 22, 2024
Copy link
Contributor

openshift-ci bot commented Feb 22, 2024

@openshift-cherrypick-robot: all tests passed!

Full PR test history. Your PR dashboard.

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/test-infra repository. I understand the commands that are listed here.

Copy link

codecov bot commented Feb 22, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 57.85%. Comparing base (f91ea54) to head (80d9694).

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff            @@
##           mce-2.5    #2216   +/-   ##
========================================
  Coverage    57.84%   57.85%           
========================================
  Files          187      187           
  Lines        26073    26073           
========================================
+ Hits         15083    15085    +2     
+ Misses        9724     9723    -1     
+ Partials      1266     1265    -1     
Files Coverage Δ
...g/controller/machinepool/machinepool_controller.go 52.90% <100.00%> (+0.25%) ⬆️

@openshift-merge-bot openshift-merge-bot bot merged commit 009fdec into openshift:mce-2.5 Feb 22, 2024
8 checks passed
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. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants