On Sun, 2020-10-04 at 16:57 -0500, William Hubbs wrote:
> On Sun, Oct 04, 2020 at 10:23:10PM +0200, Michał Górny wrote:
> > > Author: William Hubbs <williamh@gentoo.org>
> > > Posted: 2020-10-06
> > > Revision: 1
> > > News-Item-Format: 2.0
> > > Display-If-Installed: sys-cluster/kubernetes
> > > 
> > > Due to bug #741572,, the k8s split packages are returning to fix issues
> > > with upgrading clusters [1].
> > 
> > It would be nice to include a short explanation what these issues are.
> >  Expecting all affected users to open Bugzilla just to see whether
> > the bug in question is relevant causes them unnecessary work.
> 
> The short version is it is not possible to upgrade a cluster if you have
> everything in one package.

Sure, that is certainly better, though some explanation why would also
be helpful.

> 
> > > Starting with k8s 1.17.12, 1.18.9 and 1.19.2, you will need to install
> > > the following packages in the appropriate configuration for your
> > > cluster.
> > > 
> > > sys-cluster/kubeadm
> > > sys-cluster/kube-apiserver
> > > sys-cluster/kube-controller-manager
> > > sys-cluster/kubectl
> > > sys-cluster/kubelet
> > > sys-cluster/kube-proxy
> > > sys-cluster/kube-scheduler
> > > 
> > > Once the split packages are stabilized, sys-cluster/kubernetes will be
> > > masked and removed.
> > 
> > Why not make it a metapackage, and maybe have USE flags to assist common
> > configurations?
>  
> I've thought about that, and I'm not opposed to  meta packages. I'm just
> not sure yet which pieces are required where. I know you don't need all
> of the pieces to run a cluster. I'm just not sure which pieces are
> required on which nodes.
> 
> I don't think it would be one kubernetes meta package, but several
> depending on the type of node you are setting up.
> 

That's why I said you could use USE flags.

-- 
Best regards,
Michał Górny