Epic Goal

• When a user scales a MachinePool, report back the status of the MachineSet scaling up a new Machine.

Why is this important?

• When a user takes an action on an API, the API should be able to tell the user whether or not the action has failed or has succceeded.
• The scaling is inconvenient if the user has to go to the cluster to see if the scaling action was successful or not.  If this is the expected behavior from a user, then the user should be scaling MachineSets directly, and the MachinePool API has no benefit to users.

Scenarios

1. User increases replica count on a Machine Pool.  Hive, scales up one of the MachineSets on the cluster.  The MachineSet spins up a new Machine, the Machine fails for X reason; and the node is not created.  The MachinePool reports back in it's status that the scaling action is failing.

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>