K3s is another compact Kubernetes distribution. Developed by SUSE, it's packaged as a single binary that comes in at less than 70MB. Despite this tiny footprint, K3s is certified as compatible with upstream Kubernetes, is ready for production use, and supports high availability. - Source: dev.to / 19 days ago

For self-hosting I've found https://k3s.io to be really good from the SUSE people. Works on basically any Linux distro and makes self-hosting k8s not miserable. - Source: Hacker News / 3 months ago

K3S: is a lightweight distribution of Kubernetes that is designed for resource-constrained environments. It is an excellent option for running Kubernetes on a virtual machine or cloud server. - Source: dev.to / 5 months ago

I recently purchased a used Lenovo M900 Think Centre (i7 with 32GB RAM) from eBay to expand my mini-homelab, which was just a single Synology DS218+ plugged into my ISP's router (yuck!). Since I've been spending a big chunk of time at work playing around with Kubernetes, I figured that I'd put my skills to the test and run a k3s node on the new server. While I was familiar with k3s before starting this project,... - Source: dev.to / 7 months ago

I’ve created a local cluster with K3S and installing Windmill could not be simpler with just one chart to configure, which already has sane defaults to get started. For this demo we will also configure workers to passthrough environment variables to our scripts so that they have access to the Kubernetes API server for later. - Source: dev.to / 7 months ago

Protocol Buffers: https://developers.google.com/protocol-buffers. - Source: dev.to / over 1 year ago

ProtocolBuffers’ OneOf message addresses the case of having a message with many fields where at most one field will be set at the same time. - Source: dev.to / over 1 year ago

That's definitely the bigger thing. I think something like Protocol Buffers (Protobuf) is what you're looking for there. Output the data and consume it by something that can handle the analysis. Source: over 1 year ago

These protocols prevent an O(N x M) explosion of code that have to solve for many cases. For example, since JSON is an almost ubiquitous format for wire transfer (although other things do exist like protobufs), if I had N data formats that I want to serialize, I only need to write N serializers/deserializers (SerDes). If there was no such narrow waist and there were M alternatives to JSON in wide usage, I would... Source: over 1 year ago

gRPC uses protocol buffers (it is an open source message format) as the default method of communication between client and server. Also, gRPC uses HTTP/ 2 as the default protocol. - Source: dev.to / over 1 year ago