From: William Hubbs Date: Thu, 23 Jan 2020 18:19:26 +0000 (-0600) Subject: sys-cluster/kubeadm: take maintainership X-Git-Url: http://git.tremily.us/gitweb.cgi?a=commitdiff_plain;h=e11343080f7df31dbbddb5643f2e4d52532f1ff2;p=gentoo.git sys-cluster/kubeadm: take maintainership I was advised that the proxy maintainer no longer has time to maintain this. Signed-off-by: William Hubbs --- diff --git a/sys-cluster/kubeadm/metadata.xml b/sys-cluster/kubeadm/metadata.xml index 6833440b3746..acebd7ff79e8 100644 --- a/sys-cluster/kubeadm/metadata.xml +++ b/sys-cluster/kubeadm/metadata.xml @@ -2,23 +2,19 @@ - dan@danmolik.com - Dan Molik - - - proxy-maint@gentoo.org - Proxy Maintainers + williamh@gentoo.org + William Hubbs - kubeadm performs the actions necessary to get a minimum viable cluster up - and running. By design, it cares only about bootstrapping, not about - provisioning machines. Likewise, installing various nice-to-have addons, - like the Kubernetes Dashboard, monitoring solutions, and cloud-specific - addons, is not in scope. + kubeadm performs the actions necessary to get a minimum viable cluster + up and running. By design, it cares only about bootstrapping, not + about provisioning machines. Likewise, installing various + nice-to-have addons, like the Kubernetes Dashboard, monitoring + solutions and cloud-specific addons is not in scope. Instead, we expect higher-level and more tailored tooling to be built on - top of kubeadm, and ideally, using kubeadm as the basis of all deployments - will make it easier to create conformant clusters. + top of kubeadm, and ideally, using kubeadm as the basis of all + deployments will make it easier to create conformant clusters. kubernetes/kubernetes