From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 1FF8A138359 for ; Sun, 4 Oct 2020 21:57:31 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 2C245E0880; Sun, 4 Oct 2020 21:57:28 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id E044FE0826 for ; Sun, 4 Oct 2020 21:57:27 +0000 (UTC) Received: (nullmailer pid 2366 invoked by uid 1000); Sun, 04 Oct 2020 21:57:24 -0000 Date: Sun, 4 Oct 2020 16:57:24 -0500 From: William Hubbs To: gentoo-dev@lists.gentoo.org Cc: pr@gentoo.org Subject: Re: [gentoo-dev] newsitem: k8s split packages returning round 2 Message-ID: <20201004215724.GA2257@linux1.home> Mail-Followup-To: gentoo-dev@lists.gentoo.org, pr@gentoo.org References: <20201004194835.GA1431@linux1.home> <752ed6f4404bc5983669e429e4cb5b0efa8c1e5f.camel@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="d6Gm4EdcadzBjdND" Content-Disposition: inline In-Reply-To: <752ed6f4404bc5983669e429e4cb5b0efa8c1e5f.camel@gentoo.org> X-Archives-Salt: e1e55fdd-0d6a-40ed-9ab9-fcad6f57fcea X-Archives-Hash: cf7100ab58019168df3e7fcc791fdbbf --d6Gm4EdcadzBjdND Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Oct 04, 2020 at 10:23:10PM +0200, Micha=C5=82 G=C3=B3rny wrote: > On Sun, 2020-10-04 at 14:48 -0500, William Hubbs wrote: > > Title: K8s Split Packages Returning >=20 > I think you should really use the full name here, especially that it is > also the package name. This is fixed. >=20 > > Author: William Hubbs > > Posted: 2020-10-06 > > Revision: 1 > > News-Item-Format: 2.0 > > Display-If-Installed: sys-cluster/kubernetes > >=20 > > Due to bug #741572,, the k8s split packages are returning to fix issues > > with upgrading clusters [1]. >=20 > 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. > > 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. > >=20 > > 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 > >=20 > > Once the split packages are stabilized, sys-cluster/kubernetes will be > > masked and removed. >=20 > Why not make it a metapackage, and maybe have USE flags to assist common > configurations? =20 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. William --d6Gm4EdcadzBjdND Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABECAB0WIQTVeuxEZo4uUHOkQAluVBb0MMRlOAUCX3pFOgAKCRBuVBb0MMRl ODCjAJ9HOE65gJSInHohEOOQI+/sUi+UAACglGHjnvi0U0c+ReRLG1kTHbnNunQ= =r6sJ -----END PGP SIGNATURE----- --d6Gm4EdcadzBjdND--