diff options
Diffstat (limited to 'sys-cluster/kubeadm/metadata.xml')
| -rw-r--r-- | sys-cluster/kubeadm/metadata.xml | 30 |
1 files changed, 30 insertions, 0 deletions
diff --git a/sys-cluster/kubeadm/metadata.xml b/sys-cluster/kubeadm/metadata.xml new file mode 100644 index 000000000000..c1a4c8210661 --- /dev/null +++ b/sys-cluster/kubeadm/metadata.xml @@ -0,0 +1,30 @@ +<?xml version='1.0' encoding='UTF-8'?> +<!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="person"> + <email>mrueg@gentoo.org</email> + <name>Manuel Rüger</name> + </maintainer> + <maintainer type="project"> + <email>proxy-maint@gentoo.org</email> + <name>Proxy Maintainers</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. + + 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. + </longdescription> + <upstream> + <remote-id type="github">kubernetes/kubernetes</remote-id> + </upstream> +</pkgmetadata> |