this will change, and hopefully improve how we deploy kubeadm and what options it will support. it will definitely impact our project, so we will want to ensure that we do the following things:
pin versions of kubeadm, and branch both halcyon-kubernetes / halcyon-vagrant-kubernetes. this is important, and we should be doing this anyway (we only have one release for each; it's time, as we've added some very useful features since last release). we want as little disruption to our project as possible.
we will want to keep a close eye on kubeadm changes, because this will improve what our users will be able to do with the project (in particular the more portable halcyon-kubernetes project).
comment and review @luxas PR. he's super helpful, he does this part time (of his own volition), and he's asking for helpful feedback. i want to give it to him, as he represents a large body of projects who will eventually look towards kubeadm as the single source of truth. - plus, it's just being good open source citizens.
get @wilkers-steve and @larryrensing to review and comment on this PR, so they can weight in. @wilkers-steve represents kolla-kubernetes as well as our team, and we want to help that project mature as well. they potentially have impacts/opportunities.
we can talk about some of these items next week, and if anyone in the community has some suggestions or wants to help; help is always welcome!
@aric49 we may want to keep a very close eye on the changes coming for kubeadm.
here is the issue: https://github.com/kubernetes/kubeadm/pull/156
(we're giving general input now)
this will change, and hopefully improve how we deploy kubeadm and what options it will support. it will definitely impact our project, so we will want to ensure that we do the following things:
pin versions of kubeadm, and branch both halcyon-kubernetes / halcyon-vagrant-kubernetes. this is important, and we should be doing this anyway (we only have one release for each; it's time, as we've added some very useful features since last release). we want as little disruption to our project as possible.
we will want to keep a close eye on kubeadm changes, because this will improve what our users will be able to do with the project (in particular the more portable halcyon-kubernetes project).
comment and review @luxas PR. he's super helpful, he does this part time (of his own volition), and he's asking for helpful feedback. i want to give it to him, as he represents a large body of projects who will eventually look towards kubeadm as the single source of truth. - plus, it's just being good open source citizens.
get @wilkers-steve and @larryrensing to review and comment on this PR, so they can weight in. @wilkers-steve represents kolla-kubernetes as well as our team, and we want to help that project mature as well. they potentially have impacts/opportunities.
we can talk about some of these items next week, and if anyone in the community has some suggestions or wants to help; help is always welcome!
v1k