Epic Goal

• update the cluster api aws provider to include the scale from zero guidance as defined in proposal Opt-in Autoscaling from Zero .

Why is this important?

• openshift users depend on scale from zero functionality when using the cluster autoscaler, to ensure that there is no gap in features when switching from machine api to cluster api the aws provider should be updated to include the upstream guidance for enabling scale from zero.

Scenarios

1. When using openshift with cluster-api and creating MachineSet objects in cluster-api authoritative mode when the machine-api controllers are not running, there is no automation to add the scale from zero annotations. In these scenarios the cluster autoscaler is not able to scale from zero unless it can find the capacity information in the infrastructure machine templates for the provider.

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• autoscaling from zero works on aws when cluster-api is authoritative with no annotations for scaling.

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>