murder VS microshift

> I have many thousands of machines running in multiple datacenters and even getting a ~4mb binary distributed onto them without saturating the network (100mbit) and slowing everything else down, is a bit of a challenge.

You may find murder[1] of some use.

[1] https://github.com/lg/murder

Is there a repository for Fork Freshness? I could see the twitter account ignoring requests in the future and the same fate could fall to this project. I would recommend releasing the project under AGPL-3.0-or-later to partially solve this issue so the project can continue in the event of abandonment. I could see people contributing code to search for projects in other known forges such as GitLab, Sourceforge, Savannah, Gitea, pagure, and sourcehut as sometimes projects are forked outside of the original forge.

I have noticed this issue that Fork Freshness tries to solve. My example is Twitter's project murder https://github.com/lg/murder When a project becomes unmaintained whether officially or unofficially, the future home is often lost unless the original points to the new home at the top of the README file. You can dig within GitHub in the Insights > Network section to get a visual glimpse of what has changed since. https://github.com/lg/murder/network The original repository put up a notice that the project is unmaintained and archived the project which effectively ends the project in practice. In this case, ervinb's fork seems to be the most active commits before being abandoned. https://github.com/ervinb/murder Other forks also had independent commits that never were pulled into other projects. Looking at the network method fails to differentiate 30 grammar fixes from 30 new features without digging into each promising looking fork. Even then, you may miss a single commit that included more work then the entirety of the other commits. Disclosure: I have not worked on murder.

This is a serious problem and I hope we solve it.

Another good option is Microshift: https://github.com/openshift/microshift

RPM RHEL derivatives I recommend: https://microshift.io

If you are moving to edge you can try microshift (https://microshift.io/). There is also option to run a single node ocp (https://docs.openshift.com/container-platform/4.9/installing/installing_sno/install-sno-installing-sno.html).

There is also microshift. https://microshift.io/

I use one snap, but not on Fedora, instead with RHEL. It is the only way to use Microk8s, which is a quite full-featured distribution of Kubernetes that has a small footprint. Red Hat recently came out with an early offering called MicroShift, but it's not really ready yet. When it can satisfy my needs, you'll bet I'm switching.

This is an open source project from the start (as most things red hat creates), you can find the coffee here: https://github.com/redhat-et/microshift

GitHub - redhat-et/microshift: A small form factor OpenShift/Kubernetes optimized for edge computing