For kubeadm , kubetlet , kubectl should same version package in this lab I used v1.31 to have 1.31.7 References: Https://kubernetes.io/docs/reference/networking/ports-and-protocols/ Https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/install-kubeadm/ Https://github.com/opencontainers/runc/releases/... - Source: dev.to / 3 months ago

Previously I wrote about the multiple variants of Docker and also the dependencies behind the Docker daemon. One of the dependencies was the container runtime called runc. That is what creates the usual containers we are all familiar with. When you use Docker, this is the default runtime, which is understandable since it was started by Docker, Inc. - Source: dev.to / 8 months ago

Now we have dockerd which uses containerd, but containerd will not create containers directly. It needs a runtime and the default runtime is runc, but that can be changed. Containerd actually doesn't have to know the parameters of the runtime. There is a shim process between containerd and runc, so containerd knows the parameters of the shim, and the shim knows the parameters of runc or other runtimes. - Source: dev.to / 8 months ago

It's interesting that, in light of things like this, you still see large software companies adding support for new components written in non-memory safe languages (e.g. C) As an example Red Hat OpenShift added support for crun(https://github.com/containers/crun), which is written in C as an alternative to runc, which is written in Go( - Source: Hacker News / over 1 year ago

Yeah, runtimeClass lets you specify which CRI plugin you want based on what you have available. Here's an example from the containerd documentation - you could have one node that can run containers under standard runc, gvisor, kata containers, or WASM. Without runtimeClass, you'd need either some form of custom solution or four differently configured nodes to run those different runtimes. That's how krustlet did... Source: over 2 years ago

I've been working on an open source implementation of a Stellate (https://stellate.co) like GraphQL cache service, and it's finally hit v0.1 TL,DR; It is a cached proxy for your GraphQL API with automatic purging. Deploy it in front of GraphQL API, and it will start caching all requests passing through it. - Source: Hacker News / 9 months ago

Stellate - Stellate is a blazing-fast, reliable CDN for your GraphQL API and free for two services. - Source: dev.to / over 1 year ago

While some of the metrics aren't particularly helpful (depending on the actual company being evaluated) as others have mentioned, the round sizes are in the right ballpark. Our[0] actual round sizes were: 1. Pre-seed: $1M (led by System.One) 2. Seed: $4M (led by Boldstart) 3. Series A: $25M (led by Tiger Global) Note that all of these were all raised in 2021 & 2022 before the investment market crash, but even now... - Source: Hacker News / about 2 years ago

For server-side caching, you have neat solutions like GraphCDN or plugins (eg. The envelop plugin with GraphQL Yoga). - Source: dev.to / about 3 years ago

Out of the thousands of production GraphQL APIs we've seen at GraphCDN, the two most common pre-made GraphQL APIs are Hasura and WPGraphQL! Source: about 3 years ago