From: hholst80 <hholst80@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Package request: kustomize (for K8s)
Date: Mon, 22 May 2023 08:34:56 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44027@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 774 bytes --]
New issue by hholst80 on void-packages repository
https://github.com/void-linux/void-packages/issues/44027
Description:
### Package name
kustomize
### Package homepage
https://kustomize.io/
### Description
https://github.com/void-linux/void-packages/issues/27230
There are features of kustomize that has been integrated into kubectl, but kustomize is a separate tool, and has features that are not available via kubectl. One workflow that I am especially using with kustomize is `kustomize build` that bakes out a kustomize file as a set of regular manifests in a multi-document yaml.
I am happy to work on this as a first PR for the void.
### Does the requested package meet the package requirements?
Compiled
### Is the requested package released?
Yes
next reply other threads:[~2023-05-22 6:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 6:34 hholst80 [this message]
2023-05-23 22:09 ` hholst80
2023-08-09 20:16 ` [ISSUE] [CLOSED] " hholst80
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44027@inbox.vuxu.org \
--to=hholst80@users.noreply.github.com \
--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).