[rustyk8s] Hi and whats the plan?

Sylvain Wallez sylvain at bluxte.net
Sun Feb 10 08:29:25 UTC 2019


Hi,

A comment from the peanut gallery: reimplementing k8s in Rust is an 
interesting goal (and having a fast and robust api-server that is not 
based on etcd would be awesome). We have to consider however what would 
help increase usage of Rust in the k8s ecosystem and make it a strong 
alternative to Go to develop k8s components.

Good client libararies is a must, but helpers/sdk on top of it would 
make the choice even easier. We started a project at $work a few months 
ago to build a custom operator and Go was chosen just because of there 
are great supporting libraries, like 
https://github.com/kubernetes-sigs/kubebuilder

So first thing to do would be to agree on a common k8s api crate, pretty 
much like tokio is the de-facto standard crate for async networking, to 
avoid having a fragmented landscape and allow building higher-level 
functionality on top of it.

My 2 cents,
Sylvain

Le 08/02/2019 à 00:20, Justin Cormack a écrit :
> Hi,
>
> Its all pretty free form! We have a few people who should chime in
> shortly and talk about their experiences with
> writing Kubernetes client APIs in Rust, and working with the types and
> so on, which I think is generally helpful,
> and another who hacked together a bit of a rough prototype as an
> experiment, which I think will generally be
> helpful.
>
> Overall we have a mix of Rust beginners and experts and also people
> with varying depth on the k8s APIs, so people
> may want to collaborate, but I agree we definitely don't all want to
> sit down on day one and try and work on one
> thing, just see what you can get to work and ask for help and advice,
> but ideally in the open so others can look and
> contribute.
>
> Justin
>
> On Thu, 7 Feb 2019 at 17:59, Darren Shepherd <darren at rancher.com> wrote:
>> I've missed any discussion on this topic might have happened so all I know is based on the https://www.cloudatomiclab.com/rustyk8s/ blog.  Is the purpose of rustyk8s to hack on a shared implementation or a place where people can share thoughts on their own k8s implementation in rust they are hacking on? Asking because of this tweet https://twitter.com/justincormack/status/1067185866001575936 makes it seem like a competition (which I'm all for).
>>




More information about the rustyk8s mailing list