monogon VS talos

It's somewhere in my git stack :).

Until I get to publishing it, the proto/gRPC definitions for node management are a good enough start: https://github.com/monogon-dev/monogon/blob/main/metropolis/...

And the top level API to actually deploy workloads is plain Kubernetes.

Monogon, a fully remote, self-funded and engineer-led technology company, is hiring software engineers to work on Metropolis, an open source [1], secure, distributed cluster operating system based on Linux and Kubernetes.

Metropolis runs on a fleet of bare metal or cloud machines and provides users with a hardened, production ready Kubernetes - without the overhead of traditional Linux distributions or configuration management systems. It does away with the scripting/YAML duct tape and configuration drift inherent to traditional deployments, and instead provides a stable, API-driven, secure and vendor-lock-in-free platform for companies to build their products upon.

We're looking for senior candidates who can design, implement and verify complex systems that will make up part of Metropolis. We offer a kind and honest work environment in which we prioritize quality over quantity. You'll be the fourth member of a team working on an ambitious, industry-challenging product.

Our ideal candidate is a generalist with deeper knowledge in one or more of the following areas:

- Distributed systems;

- Software engineering of systems built to last;

- Security engineering, especially experience with secure boot chains;

- Low-level programming and debugging (C, Linux Kernel, …);

- Kubernetes, especially practical experience of running bare-metal production deployments;

- Platform development, ie. running a 'Company A' style infrastructure/DevOps team [2].

Our codebase is mostly Go (including pid1!), so knowledge of the language is a plus, but not a requirement (given the seniority of the position, we expect any candidate to be able to ramp up on Go within a few weeks).

To get in touch, email me at at nexantic.com.

[1] - https://github.com/monogon-dev/monogon

[2] - https://rachelbythebay.com/w/2020/05/19/abc/

- Platform development, ie. running a 'Company A' style infrastructure/DevOps team [2].

Our codebase is mostly Go (including pid1!), so knowledge of the language is a plus, but not a requirement (given the seniority of the position, we expect any candidate to be able to ramp up on Go within a few weeks).

To get in touch, email me at at nexantic.com.

[1] - https://github.com/monogon-dev/monogon

Super cool. I always enjoy reading about systems that challenge, well, "ossified" assumptions. An OS not providing a shell, for example? Madness! ... or is it genius, if the OS has a specific purpose...? It's thought-provoking, if nothing else.

I'm a bit skeptical of parts. For instance, the "init" binary being less than 400 lines of golang - wow! And sure, main.go [1] is less than 400 lines and very readable. Then you squint at the list of imported packages, or look to the left at the directory list and realize main.go isn't nearly the entire init binary.

That `talosctl list` invocation [2] didn't escape my notice either. Sure, the base OS may have only a handful of binaries - how many of those traditional utilities have been stuffed into the API server? Not that I disagree with the approach! I think every company eventually replaces direct shell access with a daemon like this. It's just that "binary footprint" can get a bit funny if you have a really sophisticated API server sitting somewhere.

[1]: https://github.com/siderolabs/talos/blob/main/internal/app/m...

[2]: https://www.talos.dev/v1.6/reference/cli/#talosctl-list

Where `kube.cue` sets reasonable defaults (e.g. image is /). The "cluster" runs on a mini PC in my basement, and I have a small Digital Ocean VM with a static IP acting as an ingress (networking via Tailscale). Backups to cloud storage with restic, alerting/monitoring with Prometheus/Grafana, Caddy/Tailscale for local ingress.

[1] https://www.talos.dev/

[2] https://cuelang.org/

Looks somewhat similar to the talos Linux project[1]

[1] https://www.talos.dev/

Talos Linux basically implements their entire userspace in Go and its similar to BottleRocketOS, because it is designed to host Kubernetes.

https://www.talos.dev/

You might be surprised to find that Talos os (linux distro for kubernetes) mostly uses Go: https://github.com/siderolabs/talos

I've been using a 3 nuc (actually Ryzen devices) k3s on SuSE MicroOS https://microos.opensuse.org/ for my homelab for a while, and I really like it. They made some really nice decisions on which parts of k8s to trim down and which Networking / LB / Ingress to use.

The option to use sqlite in place of etcd on an even lighter single node setup makes it super interesting for even lighter weight homelab container environment setups.

I even use it with Longhorn https://longhorn.io/ for shared block storage on the mini cluster.

If anyone uses it with MicroOS, just make sure you switch to kured https://kured.dev/ for the transactional-updates reboot method.

I'd love to compare it against Talos https://www.talos.dev/ but their lack of support for a persistent storage partition (only separate storage device) really hurts most small home / office usage I'd want to try.

If you’re interested in something not AWS check out Talos https://www.talos.dev/

It’s been around longer than Bottlerocket

Can't talk about work, but my homelab is Azure and Oracle managed k8s (AKS/OKE), with onprem Talos soon (Turing Pi 2). My Flux monorepo has the details. OKE performs noticably worse (update cycle, features, control plane performance), but it provides 4 ARM cores and 24GB RAM free so I can't complain

Talos