Kubernetes Submit Queue e88496a248 Merge pull request #4061 from meringu/create-subnets ... Automatic merge from submit-queue. Add --subnets and --utility-subnets to kops create cluster This change adds two new options to `kops create cluster` When specifying `--vpc`, `--subnets` can be specified as an unordered array of subnet ids. Kops will then look up the zones of the subnets to find which zone to add the subnet id to. If `--topology private` is also specified, `--utility-subnets` can similarly be specified. ~If a zone was specified but a subnet wasn't given that matches the zone, then the subnet will be allocated a CIDR with the current behaviour.~ This case fails validation here 7bd0a6a703/pkg/apis/kops/validation/validation.go (L151) I can add unit tests and docs changes if required, but I am keen to get feedback before I proceed much further. I have only added support for AWS. I have tested this by running a command similar to this: ```bash kops create cluster \ --zones=us-east-1a,us-east-1b,us-east-1c \ --topology private \ --master-zones=us-east-1a,us-east-1b,us-east-1c \ --vpc $vpc_id \ --subnets subnet-111111,subnet-222222,subnet-333333 \ --utility-subnets subnet-444444,subnet-555555,subnet-666666 \ $cluster_hosted_zone_name ``` And the cluster spec was as expected.		2017-12-18 21:12:59 -08:00
..
mockautoscaling	update cloudmock for aws-sdk-go v1.10.34	2017-11-18 18:01:34 -08:00
mockec2	Merge pull request #4061 from meringu/create-subnets	2017-12-18 21:12:59 -08:00
mockelb	missing mockelb build file	2017-12-13 23:57:45 -07:00
mockroute53	update cloudmock for aws-sdk-go v1.10.34	2017-11-18 18:01:34 -08:00