Option to use bottlerocket AMI's for EKS nodes

[richardcase]

/kind feature

Describe the solution you'd like
I would like an option to be able to use Bottlerocket for machine nodes for an EKS based cluster. I could manually specify the AMIs but ideally i should be able to specify i want bottlerocket and it should then lookup which AMIs to use for the nodes.

Anything else you would like to add:
See the docs here

Environment:

• Cluster-api-provider-aws version: 0.6.0
• Kubernetes version: (use kubectl version):
• OS (e.g. from /etc/os-release):

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[TBBle]

/remove-lifecycle stale

[randomvariable]

I believe @kschumy is interested in this?

[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

[richardcase]

/area provider/eks
/priority important-longterm
/help

[k8s-ci-robot]

@richardcase:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/area provider/eks
/priority important-longterm
/help

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.

[richardcase]

/remove-lifecycle frozen

[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]

/remove-lifecycle stale
/priority important-soon
/help

[edmondceausu]

EKS now support bottlerocket as an option when creating managed node groups (as well as a few other values). Is this something that we want to add?

I would be willing to work on this!

[richardcase]

I would be willing to work on this!

That would be great @edmondceausu. Even if CAPA just supported bottlerocket via managed node groups (via AWSManagedMachinePool) that would be a great step forward.

Feel free to assign the issue to yourself (or i can).

[edmondceausu]

/assign