Aaron Levy
Aaron Levy
fwiw it wouldn't just be a provision time, if they ever scaled down to 1 master - upgrades would stop working if we enforce 'require'. Also, the control-plane components will...
During an upgrade pods are deleted, then re-recreated. At time of re-creation the scheduler decides anew where they should be placed. Consider: - 3 master nodes - 2 controller-manager pods...
For posterity -- in an offline discussion, the behavior @chancez is describing has to do with a node update (for example) -- not with a control-plane (application) updates. An issue...
Switching object types based on number of masters would be fairly problematic for supporting automated updates. So my initial feeling is that it would be a non-starter. My current list...
It's an option. The downsides I see: The change from preferred to required is a podSpec change, so they would trigger a rolling update of all the pods in the...
`#3` is likely being started this week, but don't want to put estimates on it until someone has had time to start looking into it. For `#1`, I'm not outright...
From an offline discussion yesterday - we might have a better option (thanks @yifan-gu) What we really care about is anti-affinity between the same "version" of a particular component. However,...
FWIW when we talk about running the kubelet in a container, we might be doing this slightly differently than others. Namely using "rkt-fly". More or less running the kubelet in...
I'm going to keep this open for now, as I think we still need to add some consistency to the build process. e.g. build in a container with specific go...