Don Bowman
Don Bowman
You can run e.g. 'sudo machinectl set-limit 20G' before you launch the first machine, this will set the max limit prior to it creating the btrfs.
its one thing to do a sanity check, another to try and infer the config of the system or fix it. I think we are headed down a bad path...
maybe at least make it such behaviour off by default. e.g. a '--run-checks-and-change-your-system-if-it-matches-my-assumptions' On Thu, 23 Aug 2018 at 07:59, Dongsu Park wrote: > I would call it a "necessary...
the names are still unique. kube-spawn---# and # is incrementing. it just allows me to always refer to a worker when using NodePort to come into it, rather than run...
any comment on this?
I guess i don't understand what the random one achieves for anyone? Its no more unique.
the issue is the node-names we create. they need to be locally resolvable. Since we made them, its insufficient to allow local dns server. otherwise we are hammering the root...
This was referenced from https://github.com/kinvolk/kube-spawn/issues/14 but the 'fix' assumes 131072 is the right value where the auto-tuner in kube-proxy is assuming 589824 for the memory size of my system.
no comments?
scaling is 100% on both displays