Kops generate Cloud Formation code for AWS

[krisnova]

This is an issue to track the progress of generating official AWS Cloud Formation code with kops.

Success Criteria

1. Generate Cloud Formation code for all permutations of clusters.
2. Support for JSON and YAML encoding (link)
3. Comparable UX and flow as --target terraform

Future considerations

Output

1. Output to STDOUT
2. Output to file system
3. Output to AWS API

CC @jbeda @justinsb

[ahawkins]

What's the use case? Also I guess why not use CloudFormation for all AWS operations instead of the internal homegrown thing? I see this being useful as means to replace the internal implementation.

[krisnova]

So @jbeda had a great suggestion (that we will probably need to get in for this feature 😉)

But we would like to include meaningful comments for each of the resources that explain what they do. An example of doing this can be found here

[krisnova]

@ahawkins the use cases are providing an AWS native approach to defining and deploying k8s clusters. Something that is going to be necessary as we start to tell the "What does an official AWS k8s cluster look like" story.

[scribnar]

Does Kops create CloudFormation configuration? or does it provision the resources as needed such that any major failure is unlikely to be restored like in case that can happen if we use CloudFormation in conjunction?

[chrislovecnm]

Yes kops now supports basic cf.

Closing as we have basic support.

[srflaxu40]

So with the cloudformation option / target could I generate the template and then just upload it to AWS? How would this effect an already-existing cluster?

[Raffo]

@chrislovecnm What does "basic" mean here?