gbxk

5 ms·

1.
by gbxk 29d ago
And here is the deep-dive blogpost series: https://beci.me/blog
2.
Show HN: K7d – Fork live Kubernetes clusters in <1s –> GRPO-train AI on infra(github.com)
3 points by gbxk 29d ago|1 comments
3.
by gbxk 1mo ago
Amazing project. Have you guys thought about running it or adapting it for FPGA-like approaches like this one below that reach Taalas-speed like 20k tok/sec on cheap hardware? https://www.mikeayles.com/blog/on-chip
4.
by gbxk 1mo ago
Amazing project, I love it. How about using these Cactus models? Would it make sense for you to collab with those guys (1) for you to design a cheap but improved, commercialisable version of your $250 chip and (2) for them to tailor their r
5.
by gbxk 1mo ago
That does not look planned.
6.
by gbxk 1mo ago
Nobody said that’s the only safeguard. When the attack surface is all of language you better have a defense-in-depth philosophy or as close as you can to that.
7.
by gbxk 11mo ago
Update: Katakate now supports ARM architecture (on Linux) thanks to a PR merged from Katakate's first external GitHub contributor: @spullara. Thank you!
8.
by gbxk 11mo ago
Test passed, PR merged
9.
by gbxk 11mo ago
As promised: https://github.com/Katakate/k7/tree/fix/no-dns-res-in-lockdo... Will merge that in after it passes all network tests on a clean/wiped instance.
10.
by gbxk 11mo ago
Thanks! I'll review Arrakis and come back. E2B is often considered harder to setup and less AI engineers friendly for direct stack contributions, as Katakate is the only alternative fully implemented in Python (core modules, Typer CLI,
11.
by gbxk 11mo ago
Thanks! Yes: Katakate provides much stronger isolation, since it uses hardware virtualization (via Kata Containers and Firecracker) while gVisor relies purely on software sandboxing in user space. gVisor isolates containers by intercepting
12.
by gbxk 11mo ago
Thanks for sharing, adding it to my list.
13.
by gbxk 11mo ago
Very cool! Apple containers run on Apple ARM so it's complimentary to my stack which doesn't support ARM yet (but soon will when extending to Qemu which supports ARM). Thanks for sharing!
14.
by gbxk 11mo ago
This is an excellent point. I moved this to #1 on the TODO list. I'll deny all DNS resolution by default until Cilium is integrated, if that passes the basic functionality tests. I'll also add to the roadmap whilelist/deny f
15.
by gbxk 11mo ago
Thanks, will study that one too!
16.
by gbxk 11mo ago
Interesting, thanks for sharing!
17.
by gbxk 11mo ago
Very cool one. That's dedicated to Apple ARM which I don't currently support so the two are complimentary. Apple containers shares some primitives with Kata. I'll investigate if it's possible to use Apple containers as a
18.
by gbxk 11mo ago
Thanks, I'll review that one too and compare.
19.
by gbxk 11mo ago
Lucky you! And lucky me for sharing the info :)
20.
by gbxk 11mo ago
Katakate is built on top of Kata, and sets up a stack combining Kubernetes (K3s), Kata, Firecracker, and devmapper snapshotter for thin pool provisioning. Combining these tools together is highly non-trivial and can be a headache for many,
21.
by gbxk 11mo ago
That's a config example. Yes, blocking DNS exfiltration requires DNS filtering at cluster level. This is what will be added with the Cilium integration which is top-3 on the roadmap (top of readme). DNS resolution is required for basic
22.
by gbxk 11mo ago
Thanks everyone for the amazing feedback and discussion! For anyone curious: – Docs: https://docs.katakate.org - LangChain Agent tutorial: https://docs.katakate.org/guides/langchain-agent It's getting
23.
by gbxk 11mo ago
It uses Kata with Firecracker which gives you as light of a boot as it gets. Subsecond booting for instance is accessible with a lighter rootfs, which is also on the roadmap (one of the easiest items, actually). The k8s layer doesn't a
24.
by gbxk 11mo ago
That's an interesting direction! TEE support would be relatively straightforward with current stack (and it's on my roadmap), so that could be a first step forward.
25.
by gbxk 11mo ago
It is well known that containers do not provide you safe isolation. It is not their purpose. They share kernel and page cache with the host. Any kernel exploit gives to someone in a container potential root control of the host (see DirtyPip
26.
by gbxk 11mo ago
Sure one day if it really kicks off I could think of offering additionally a SaaS solution with paid enterprise features like SOC 2 compliance, RBAC, multiple clouds supported, etc. Why not. But I strongly believe that for it to be successf
27.
by gbxk 11mo ago
If you have any suggestion on how I can make this more friendly UX-wise to your personal usage, I am most interested to hear! And this will shape my roadmap.
28.
by gbxk 11mo ago
Actually you can! After you run "k7 install" you'll have a k3s cluster up and running, with Kata as a runtime class, and Firecracker specified in Kata config. So nothing prevents you from hitting the Kubernetes API! kubectl w
29.
by gbxk 11mo ago
True! GCP does. I haven't tested it yet. I didn't know D.O does. If anyone knows others, I'm interested too!
30.
by gbxk 11mo ago
No business model short-term. My goal is broad adoption, 100% open-source. By multi-node I mean so far I only support 1 k8s node, i.e. 1 machine, but soon adding support for multiple. Still, on 20 CPUs I can run +50 VM pods with fractional

More ›