Luke Hoban

I can't seem to reproduce this - is it fixed by the changes in v.0.3.0?

Thanks for this! There have been a few translations so far. I think what might be a better approach instead of contributing them all to folders in this repo is...

As noted in #43, I'm not sure this is the right change to address this - I'd like to include the details on how subclassing of builtins will be handled...

Yes - this section needs to be modified. But I think it does need to address the new model, and my understanding is that that is not yet 100% finalized....

Good point, I've got some content I should be able to add.

Note that the `instanceRole` is exposed from the component, so you should be able to attach additional `RolePolicyAttachment`s to it after creating the cluster and before deploying the kubernetes resources....

I just hit the need for this myself this morning, and it does seem like out of the box support for this would be really nice. I can imagine offering...

> ```ts > const launchTemplate = new aws.ec2.LaunchTemplate("my-launch-template", { > tags: {testTag: "tag value"}, > }); > ``` This tags the launch template, but does not tag the instances created...

The CNI YAML we use here is based on what's available from upstream. The upstream does indeed hard code this in, and expects that to be accessible. We could definitely...

Looking at this a little more deeply - it's a little unfortunate that we would have to allow specifying both `nodeSubnetIds` and `availabilityZone`. These are largely overlapping concepts for this...