From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: k3s: add services, missing binaries.
Date: Tue, 15 Oct 2019 05:24:25 +0200 [thread overview]
Message-ID: <20191015032425.vnIG6FvXhcjDlBKEU1QjrifS1majW0-7Cy4iP8sgT4o@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-15101@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 817 bytes --]
There's a closed pull request on the void-packages repository
k3s: add services, missing binaries.
https://github.com/void-linux/void-packages/pull/15101
Description:
- Fix version string in 'k3s -v' output to match release builds.
- Adds the missing hyperkube binary. This conflicts with kubernetes, so
it may be an issue for folks who want to install both k3s and
kubernetes at the same time. Not sure who those folks are, but
I guess it could be a subpackage too.
- Fixes k3s builds to include kubectl and crictl (previous revisions
included the CLI commands in the usage output but could not be used).
- Add service files for k3s-agent and k3s-server.
- Fetch Traefik manifests for codegen bits of the build.
- Update short_desc to match k3s description.
- Set homepage to k3s.io.
prev parent reply other threads:[~2019-10-15 3:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-04 23:30 [PR PATCH] DO NOT MERGE: " voidlinux-github
2019-10-04 23:32 ` [PR PATCH] [Updated] " voidlinux-github
2019-10-04 23:32 ` voidlinux-github
2019-10-05 1:47 ` voidlinux-github
2019-10-06 0:16 ` voidlinux-github
2019-10-07 16:43 ` [PR PATCH] [Updated] " voidlinux-github
2019-10-07 16:43 ` voidlinux-github
2019-10-07 16:48 ` voidlinux-github
2019-10-07 18:24 ` voidlinux-github
2019-10-07 18:24 ` voidlinux-github
2019-10-07 18:25 ` voidlinux-github
2019-10-12 9:31 ` voidlinux-github
2019-10-15 3:24 ` voidlinux-github [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191015032425.vnIG6FvXhcjDlBKEU1QjrifS1majW0-7Cy4iP8sgT4o@z \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).