GTgtirloni·Aug 13, 2025Submission
Yoke Kubernetes Package Manager
1 points · Open discussionyokecd
yoke
Go2025–2025
yokecd / yoke
yoke
Kubernetes Package Management as Code; infrastructure as code, but actually.
2Distinct people
3Mentions
0Explicit recommenders
781GitHub stars
What to know before exploring
What it is
Kubernetes Package Management as Code; infrastructure as code, but actually.
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by week3 dated mentions
Observed mentions: 2025-04-25 13:44:21 UTC to 2025-08-13 19:12:45 UTC. Weeks start Monday, UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Apr 21 | 2025-04-21 00:00:00 UTC | 2025-04-28 00:00:00 UTC | 2 | 1 | 1 |
| Apr 28 | 2025-04-28 00:00:00 UTC | 2025-05-05 00:00:00 UTC | 0 | 0 | 0 |
| May 5 | 2025-05-05 00:00:00 UTC | 2025-05-12 00:00:00 UTC | 0 | 0 | 0 |
| May 12 | 2025-05-12 00:00:00 UTC | 2025-05-19 00:00:00 UTC | 0 | 0 | 0 |
| May 19 | 2025-05-19 00:00:00 UTC | 2025-05-26 00:00:00 UTC | 0 | 0 | 0 |
| May 26 | 2025-05-26 00:00:00 UTC | 2025-06-02 00:00:00 UTC | 0 | 0 | 0 |
| Jun 2 | 2025-06-02 00:00:00 UTC | 2025-06-09 00:00:00 UTC | 0 | 0 | 0 |
| Jun 9 | 2025-06-09 00:00:00 UTC | 2025-06-16 00:00:00 UTC | 0 | 0 | 0 |
| Jun 16 | 2025-06-16 00:00:00 UTC | 2025-06-23 00:00:00 UTC | 0 | 0 | 0 |
| Jun 23 | 2025-06-23 00:00:00 UTC | 2025-06-30 00:00:00 UTC | 0 | 0 | 0 |
| Jun 30 | 2025-06-30 00:00:00 UTC | 2025-07-07 00:00:00 UTC | 0 | 0 | 0 |
| Jul 7 | 2025-07-07 00:00:00 UTC | 2025-07-14 00:00:00 UTC | 0 | 0 | 0 |
| Jul 14 | 2025-07-14 00:00:00 UTC | 2025-07-21 00:00:00 UTC | 0 | 0 | 0 |
| Jul 21 | 2025-07-21 00:00:00 UTC | 2025-07-28 00:00:00 UTC | 0 | 0 | 0 |
| Jul 28 | 2025-07-28 00:00:00 UTC | 2025-08-04 00:00:00 UTC | 0 | 0 | 0 |
| Aug 4 | 2025-08-04 00:00:00 UTC | 2025-08-11 00:00:00 UTC | 0 | 0 | 0 |
| Aug 11 | 2025-08-11 00:00:00 UTC | 2025-08-18 00:00:00 UTC | 1 | 1 | 0 |
What Hacker News says
3 sourcesShow HN: Helm is a pain, so I built Yoke – A Code-First Alternative
5 points · Open discussionManaging Kubernetes resources with YAML templates can quickly turn into an unreadable mess. I got tired of fighting it, so I built Yoke.
Yoke is a client-side CLI (like Helm) but instead of YAML charts, it allows you to describe your charts (“flights” in Yoke terminology) as code.
Your Kubernetes “packages” are actual programs, not templated text, which means you can use actual programming languages to define your packages; Allowing you to fully leverage your development environment.
At its core a flight is a program that reads inputs from stdin and writes resources to stdout. It is packaged as a WebAssembly Module for portability and security. This allows you to leverage any programming language that supports WebAssembly like Go or Rust to build your "chart" logic.
With yoke your packages get: control flow, static typing and intilisense,
Read the rest
type checking, test frameworks, package ecosystem (go modules, rust cargo, npm, and so on), and so on!
What's more Yoke doesn't stop at client-side package management. You can integrate your packages directly into the Kubernetes API with Yoke's Air-Traffic-Controller, enabling you to manage your packages as first-class Kubernetes resources.
This is still an early project, and I’d love feedback. Here is the Github Repository and the documentation.
Repo: https://github.com/yokecd/yoke
Docs: https://yokecd.github.io/docs
Would love to hear thoughts—good, bad, or otherwise.