Loads of issues

[jaykeshur]

• i can't seem to create a master pool without creating both compute and master in the same subnets. i have to create cluster, then delete compute
• the pool- [ ]size in the create cluster does not work, it always creates a compute pool of even when you set the pool size to 0
• the elb does not appear to create the dns entry, do i use the host zone id or the domain name?
• the zero logging and it's a little scary to run create and destroy commands without seeing anything on the screen for 5/8 minutes )
• there's no way to customize the size of the master pools per az
• the command line options has been copied and paste and so you have references to computes when create a masterpool etc
• i know it been purposely left out from the scope of the tool, but it feels weird to use one tool to build the subnets and then switch to another tool to build boxes in them. I'm not sure what the advantage of leaving the subnet creation outside. I;m guessing by placing the contextual information in the tags is harder to consume more complex data.
• the kubernetes elb created is open to the world and their doesn't appear to be any way to say internal only
• the nodes created all have public ip addresses assigned even though i'm building behind a nat gateway, which is fine, but there's no way to turn the feature off.
• it would be good to have the feature assigning custom security groups to the nodepools i create.
• the name of the security group of a compute pool is named masterpool
• the security for the kubernetes elb should have a Name tag
• infra: Create domain for env ?
• keto: Create route53 entry for kube api
• --pool-size flag is completely ignored.
• labels do not get applied to nodes, see labels do not get applied to nodes keto-k8#46
• master nodes should be created a unschedulable or have taints on compute nodes to ensure kube-dns only runs on compute - see Ensure not everyone can deploy to Masters keto-k8#23.
• change description of cloudformation template based on name of cluster
• would be nice to have the Name tag of the instance to reflect the computepool name ... as everything has clustername-compute