Spot Instance Support for AWSManagedMachinePool

[cabrinha]

/kind feature

Describe the solution you'd like
I'd like to use AWSManagedMachinePool / MachinePool with spot instances.

Environment:

• Cluster-api-provider-aws version: v6.5.0
• Kubernetes version: (use kubectl version): v1.19
• OS (e.g. from /etc/os-release): amazon linux 2

[voor]

Referencing https://www.github.com/kubernetes-sigs/cluster-api/tree/master/docs%2Fproposals%2F20200330-spot-instances.md

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[voor]

/remove-lifecycle stale

[richardcase]

/priority important-soon
/milestone v1.x

[richardcase]

/triage accapted

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[richardcase]

/lifecycle frozen

[pydctw]

Spot Instance support is already available with AWSManagedMachinePool + MachinePool flavor (EKS cluster) by specifying capacityType in AWSManagedMachinePool spec.

apiVersion: infrastructure.cluster.x-k8s.io/v1beta1
kind: AWSManagedMachinePool
metadata:
  name: eks-pool-0
spec:
  capacityType: spot
  ...

What are remaining tasks for the issue? (I may lack context on this, hence asking)

[Ankitasw]

Correct me if I am wrong but I think this is the ask here.

[pydctw]

After reading the proposal, I am still not clear what else is needed for spot instance support in EKS managed node group case (with AWSManagedMachinePool). Could you help elaborate, @Ankitasw?

[pydctw]

/retitle Spot Instance Support for AWSManagedMachinePool

[AustinSiu]

@pydctw if this issue is scoped to just AWSManagedMachinePools, do you know what is the state of Spot support in AWSMachinePools/non-managed case? From the CAPA book, I had assumed this issue was tracking both (wasn't aware of the existing EKS support!).

[pydctw]

We discussed spot instance support in CAPA during 6/13/22 office hr. Decided to create a new issue for AWSMachinePool spot instance support.

• Spot Instance Support for AWSMachinePool #3522

[pydctw]

I will create a PR to update spot instance doc with AWSManagedMachinePool.