summaryrefslogtreecommitdiff
path: root/sys-cluster/kubeadm/metadata.xml
diff options
context:
space:
mode:
Diffstat (limited to 'sys-cluster/kubeadm/metadata.xml')
-rw-r--r--sys-cluster/kubeadm/metadata.xml22
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>