Support Flatcar linux for nodes

[richardcase]

/kind feature

Describe the solution you'd like
I would like to be able to use Flatcar linux for the control plane and worker nodes with CAPA.

Anything else you would like to add:
Documentation for running flatcar on ec2 is here. There are existing AMIs that can be used but we'd need to think about the ignition and kubeadm config.

Environment:

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

[ncdc]

See also kubernetes-sigs/image-builder#248 and kubernetes-sigs/cluster-api#3437

[vbatts]

Having a provider like CAPA would be a good use case to test the WIP Ignition bootstrap provider in kubernetes-sigs/cluster-api#3437

[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

[richardcase]

/remove-lifecycle stale

[invidian]

See #1875 (comment) for some progress update.

[invidian]

Created #2271 with initial implementation to resolve this and possibly #1875.

[invidian]

Should this be moved to v0.7.0 milestone the same as #2271 ?

[randomvariable]

Yup, thx.

/milestone v0.7.0

[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

[invidian]

/remove-lifecycle stale

We're doing a good progress on kubernetes-sigs/cluster-api#4172, we recently added missing e2e tests, a feature gate and documentation.

BTW, as CABPK decided that Ignition support will be behind a feature gate for the time being, how does it affect this PR? Can we enable the feature gate for e2e tests?

[sedefsavas]

Adding ignition support directly to the API that uses an experimental feature in the core cluster-api repository may not be the best option. We should consider feature-gating it in this repository as well.

Can we enable the feature gate for e2e tests?

yes, we do it for other experimental feats:

cluster-api-provider-aws/test/e2e/data/e2e_conf.yaml

Line 150 in 06e02b2

EXP_CLUSTER_RESOURCE_SET: "true"

[invidian]

Adding ignition support directly to the API that uses an experimental feature in the core cluster-api repository may not be the best option. We should consider feature-gating it in this repository as well.

We will do it, thanks for the advice, it make sense 👍 CC @surajssd

[invidian]

CABPK PR kubernetes-sigs/cluster-api#4172 has been merged and will be part of v1.1 release, so we're getting closer getting this resolved 🎉

[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

[invidian]

/remove-lifecycle stale

This is still in progress.