Ole Markus With
Ole Markus With
What do you mean by that it detects cluster name from the node it runs on?
Right. It seems this flag isn't being consumed at all. Instead it uses `KubernetesClusterID` under the `[global]` section of cloud-config. This fairly close to a bug.
Not using this one. But it's standard ini-file stuff. So this probably works: ``` [global] KubernetesClusterID= KubernetesClusterTag= ```
It's the whole provider that does this. So I'd think this affects all controllers.
The logic right now is to take the network CIDR, divide it into 8, and then take the last of those 8 and divide further into 8 subnets. That logic...
BTW, based on looking at some real clusters, the private subnets consume way more IPs than the utility subnets.
I think we can do things a bit simpler for `kops create`. The purpose of running `kops create cluster` is just to get a cluster going. If one has special...
My suggestion was only for allowing smaller clusters without redoing the entire logic for how we split subnets. Changing the logic for any CIDR would be larger discussion, I think....