diff options
| author |   William Hubbs <william.hubbs@sony.com> | 2020-01-23 12:19:26 -0600 |
|---|---|---|
| committer |   William Hubbs <williamh@gentoo.org> | 2020-01-23 12:22:42 -0600 |
| commit | e11343080f7df31dbbddb5643f2e4d52532f1ff2 (patch) | |
| tree | 97f5d633fb35e3a79ec212f18283a57f8396f1fb /sys-cluster | |
| parent | media-gfx/geeqie: fix live ebuild (diff) | |
| download | gentoo-e11343080f7df31dbbddb5643f2e4d52532f1ff2.tar.gz gentoo-e11343080f7df31dbbddb5643f2e4d52532f1ff2.tar.bz2 gentoo-e11343080f7df31dbbddb5643f2e4d52532f1ff2.zip | |
sys-cluster/kubeadm: take maintainership
I was advised that the proxy maintainer no longer has time to maintain
this.
Signed-off-by: William Hubbs <williamh@gentoo.org>
Diffstat (limited to 'sys-cluster')
| -rw-r--r-- | sys-cluster/kubeadm/metadata.xml | 22 |
1 files changed, 9 insertions, 13 deletions
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 @@ <!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd"> <pkgmetadata> <maintainer type="person"> - <email>dan@danmolik.com</email> - <name>Dan Molik</name> - </maintainer> - <maintainer type="project"> - <email>proxy-maint@gentoo.org</email> - <name>Proxy Maintainers</name> + <email>williamh@gentoo.org</email> + <name>William Hubbs</name> </maintainer> <longdescription lang="en"> - 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. </longdescription> <upstream> <remote-id type="github">kubernetes/kubernetes</remote-id> |