kubernetes VS kine

Kubernetes + Pipeline CI/CD

Cloud-Native Friendly: Lightweight and fast, Go apps fit perfectly into containerized environments like Docker and Kubernetes.

Over the years, Indian developers have played increasingly vital roles in many international projects. From contributions to frameworks such as Kubernetes and Apache Hadoop to the emergence of homegrown platforms like OpenStack India, India has steadily carved out a global reputation as a powerhouse of open source talent.

I'd also strongly recommend this view of how Kubernetes uses cgroups, showing similar drill downs for how everything gets managed.

I've been a bit apoplectic in the past that cgroups seemed not super helpful in Kubernetes, but this really showed me how the different Kubernetes QoS levels are driven by similar juggling of different cgroups.

I'm not sure if this makes use of cpu.max.burst or not. There's a fun article that monkeys with these cgroups directly, which is neat to see. It also links to an ask that Linux support the new (5.14) CFS Burst system. Which is a whole nother fun rabbit hole to go down! https://medium.com/@christian.cadieux/kubernetes-throttling-... https://github.com/kubernetes/kubernetes/issues/104516

Kubernetes isn't just for container orchestration—it packs a powerful built-in service discovery system that's changing how developers think about service connectivity. It uses DNS under the hood, along with environment variables, to help services find each other.

https://github.com/kubernetes/kubernetes/commit/7fef0a4f6a44...

Of course, we'd already fixed other issues like Kubelet listening on a secondary debug port with no authentication. Those problems stemmed from its origins as a make-it-possible hacker project and it took a while to pivot it to something usable in an enterprise.

For a comprehensive overview, explore the Kubernetes 1.33 release notes and GitHub changelog. Engage with the community at events like KubeCon or join the Kubernetes Slack to collaborate on the future of cloud-native computing. With Octarine, Kubernetes continues to shine as the backbone of modern infrastructure.

Historical Note: For a brief period around Kubernetes 1.10, the default was accidentally changed to HostToContainer before being reverted. If you're managing a very old cluster, be aware of this possibility (#62462).

Imagine trying to keep a fleet of ships sailing smoothly across the ocean. You need to ensure each ship has enough crew, fuel, and cargo, and that they're all heading in the right direction. This is a complex task, requiring constant monitoring and adjustments. In the world of Kubernetes, Controllers and Operators play a similar role, ensuring your applications run smoothly and efficiently. This blog post delves deep into the differences between these two essential components, providing clear examples to illustrate their functionalities and use cases.

Kubernetes has become the de facto standard for container orchestration. With the rise of microservices and cloud-native applications, managing network traffic within a Kubernetes cluster has become increasingly critical. The Ingress API has been the traditional solution for managing external access to services in Kubernetes. However, with the evolution of Kubernetes and the need for more advanced traffic management capabilities, the Gateway API has emerged as a powerful alternative. This post provides a detailed comparison of Gateway API and Ingress API, highlighting the advantages of Gateway API and offering recommendations for when to choose it over Ingress API.

At this point i would like to mention a project called Kine. Kine is an option to replace ETCD to MySQL or PostgreSQL, the most popular SQL databases. It can solve the database size issue, but it still lacks on the other aspects of the limitations.

-- Kine (Kine is not etcd)

Looking at [1], is there any reason why this couldn’t run in something like DynamoDB? I feel like the operations required would fit

https://github.com/k3s-io/kine/blob/master/pkg/drivers/gener...

I don't like some of the decisions that k3s makes which is why I stay away from it, but it's a great project. I'm not using kine yet, but I fantasize about using it exclusively every time I deal with etcd-induced slowness/random CPU spikes on my group of controller nodes. k0s supports kine too of course but I just haven't switched it on yet.

Well in some situations you can also get away with CRDTs or Gossip (SWIM), but yeah in the general sense Paxos (Raft is a Paxos-family algo). There are lots of paxos family algos to choose from[0].

> I’m also currently building a distributed search engine using etcd for the service registry, broker peer announcements, and worker queue and it’s been a good experience so far.

As a random stranger on the internet, please build an abstraction layer around etcd. Even if there's only one implementation, I've found that so many distributed projects that just never reach the scale that etcd is built for would benefit from the option of writing their own drivers (you don't need a full plugin system just a regular abstraction layer).

One example is Kine[0] for k8s -- if k8s had a built in option for writing/reading from something like Postgres from the beginning it would have been a better project for it, IMO.

If you do build a plugin system though, you can pass off the work of maintaining the other implementations!

[0]: https://vadosware.io/post/paxosmon-gotta-concensus-them-all

[1]: https://github.com/k3s-io/kine

I could spent >0s looking into this, but I've been curious how kline implements Etcd's Watch API. For the matter, I don't have much idea in general how kline handles data. Kline would be a great candidate for a blog post or introductory technical article on.

I do quickly see one issue- evidently watches presently use polling. The issue requests use of postgres triggers: https://github.com/k3s-io/kine/issues/20

check out https://github.com/k3s-io/kine