Add option to deploy without a CNI to enable use of custom CNI's

[philchristensen]

I'm working on replacing a Terraform-based EKS cluster deployment script with CloudFormation based on the QuickStart templates. I had to make a number of changes to support the particular vagaries of my work environment, but everything is going quite well.

I'm stuck on one minor issue though. Previously, our Terraform process installed a chart that setup the CNI configuration details to allow us to leverage an additional CIDR range, and in addition to that, also created the aws-node service roles, daemon sets, and so forth.

However, after successful cluster creation with the QuickStart templates, it appears that something has already configured these aws-node resources.

I'm trying to decide whether to keep this stuff in our chart or drop it altogether, but I'd really like to know where in the QuickStart process these objects get created. I've looked all through the source with no luck.

Thanks in advance, -Phil