| 1 |
commit: e11343080f7df31dbbddb5643f2e4d52532f1ff2 |
| 2 |
Author: William Hubbs <william.hubbs <AT> sony <DOT> com> |
| 3 |
AuthorDate: Thu Jan 23 18:19:26 2020 +0000 |
| 4 |
Commit: William Hubbs <williamh <AT> gentoo <DOT> org> |
| 5 |
CommitDate: Thu Jan 23 18:22:42 2020 +0000 |
| 6 |
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e1134308 |
| 7 |
|
| 8 |
sys-cluster/kubeadm: take maintainership |
| 9 |
|
| 10 |
I was advised that the proxy maintainer no longer has time to maintain |
| 11 |
this. |
| 12 |
|
| 13 |
Signed-off-by: William Hubbs <williamh <AT> gentoo.org> |
| 14 |
|
| 15 |
sys-cluster/kubeadm/metadata.xml | 22 +++++++++------------- |
| 16 |
1 file changed, 9 insertions(+), 13 deletions(-) |
| 17 |
|
| 18 |
diff --git a/sys-cluster/kubeadm/metadata.xml b/sys-cluster/kubeadm/metadata.xml |
| 19 |
index 6833440b374..acebd7ff79e 100644 |
| 20 |
--- a/sys-cluster/kubeadm/metadata.xml |
| 21 |
+++ b/sys-cluster/kubeadm/metadata.xml |
| 22 |
@@ -2,23 +2,19 @@ |
| 23 |
<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd"> |
| 24 |
<pkgmetadata> |
| 25 |
<maintainer type="person"> |
| 26 |
- <email>dan@××××××××.com</email> |
| 27 |
- <name>Dan Molik</name> |
| 28 |
- </maintainer> |
| 29 |
- <maintainer type="project"> |
| 30 |
- <email>proxy-maint@g.o</email> |
| 31 |
- <name>Proxy Maintainers</name> |
| 32 |
+ <email>williamh@g.o</email> |
| 33 |
+ <name>William Hubbs</name> |
| 34 |
</maintainer> |
| 35 |
<longdescription lang="en"> |
| 36 |
- kubeadm performs the actions necessary to get a minimum viable cluster up |
| 37 |
- and running. By design, it cares only about bootstrapping, not about |
| 38 |
- provisioning machines. Likewise, installing various nice-to-have addons, |
| 39 |
- like the Kubernetes Dashboard, monitoring solutions, and cloud-specific |
| 40 |
- addons, is not in scope. |
| 41 |
+ kubeadm performs the actions necessary to get a minimum viable cluster |
| 42 |
+ up and running. By design, it cares only about bootstrapping, not |
| 43 |
+ about provisioning machines. Likewise, installing various |
| 44 |
+ nice-to-have addons, like the Kubernetes Dashboard, monitoring |
| 45 |
+ solutions and cloud-specific addons is not in scope. |
| 46 |
|
| 47 |
Instead, we expect higher-level and more tailored tooling to be built on |
| 48 |
- top of kubeadm, and ideally, using kubeadm as the basis of all deployments |
| 49 |
- will make it easier to create conformant clusters. |
| 50 |
+ top of kubeadm, and ideally, using kubeadm as the basis of all |
| 51 |
+ deployments will make it easier to create conformant clusters. |
| 52 |
</longdescription> |
| 53 |
<upstream> |
| 54 |
<remote-id type="github">kubernetes/kubernetes</remote-id> |
Archives