summaryrefslogtreecommitdiff
blob: c1a4c82106616714c8914fd59f8d80deea8d5675 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
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>