|over 3 years ago||6 days ago|
|MIT License||Mozilla Public License 2.0|
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
We haven't tracked posts mentioning Overcast yet.
Tracking mentions began in Dec 2020.
Kubernetes at Home with K3s
5 projects | news.ycombinator.com | 5 Dec 2021
That's a false statement as far as the technical aspects are concerned (Swarm is still usable and supported), but is a true statement when you look at the social aspects (Kubernetes won the container wars and now even Nomad is uncommon to run into).
Right now the company i'm in uses Swarm in a lot of places due to its simplicity (Compose file support) and low resource usage - Swarm hits the sweet spot when it comes to getting started with container orchestration and doing so without needing multiple people to wrangle the technical complexity of Kubernetes, or large VMs to deal with its resource usage, at least in on prem environments.
In combination with Portainer (https://www.portainer.io/) it's perhaps one of the best ways to get things done, when you expect everything to just work and aren't doing something too advanced (think along the lines of 10 servers, rather than 100, which is probably most of the deployments out there).
I actually wrote about some of its advantages in my blog post, "Docker Swarm over Kubernetes": https://blog.kronis.dev/articles/docker-swarm-over-kubernete...
That said, if there are any good options to replace Swarm, it has to either be Hashicorp Nomad (https://www.nomadproject.io/) which is a really nice platform, especially when coupled with Consul (https://www.consul.io/), as long as you can get past the weirdness of HCL. Alternatively, it has to be K3s (https://k3s.io/), which gives you Kubernetes without the insane bloat and hardware usage.
I actually benchmarked K3s against Docker Swarm in similar app deployments: 1 leader server, 2 follower servers, running a Ruby on Rails app and an ingress, while they're under load testing by K6 (https://k6.io/). I was attempting to see whether COVID contract tracking with GPS would be viable as far as the system load goes in languages with high abstraction level, here's more info about that: https://blog.kronis.dev/articles/covid-19-contact-tracing-wi...
Honestly, the results were pretty close - on the follower servers, the overhead of the orchestrator agents were a few percent (K3s being heavier, but a few dozen MB here or there not being too relevant), whereas the bigger differences were in the leader components, where K3s was heavier almost by a factor of two, which isn't too much when you consider how lightweight Swarm is (there was a difference of a few hundred MB) and the CPU usage was reasonably close in both of the cases as well. Sadly, the text of the paper is in Latvian, so it's probably of no use to anyone, but i advise you to do your own benchmarks! Being a student, i couldn't afford many servers then, so it's probably a good idea to benchmark those with more servers.
Of note, on those VPSes (4 GB of RAM, single core), the full Kubernetes wouldn't even start, whereas at work, trying to get the resources for also running Rancher on top of a "full" Kubernetes cluster (e.g. RKE) can also take needlessly long due to the backlash from ops. Also, personally i find the Compose syntax to be far easier to deal with, rather than the amalgamation that Kubernetes uses, Helm probably shouldn't even be a thing if the deployment descriptors weren't so bloated. Just look at this: https://docs.docker.com/compose/compose-file/compose-file-v3...
- Docker Swarm is pretty good when you're starting out with containers and is reasonably stable and easy to use
Creating GCP disk images with (for?) TerraForm
1 project | reddit.com/r/devops | 23 Nov 2021
Also if you don’t want to look at kube then check out Nomad. https://www.nomadproject.io/
Is cloud native getting a bit too complex?
1 project | reddit.com/r/sre | 10 Nov 2021
Hahaha sure: https://www.nomadproject.io it’s by HashiCorp.
De docker para Kubernetes
1 project | reddit.com/r/devpt | 4 Nov 2021
An Update on Our Outage
3 projects | news.ycombinator.com | 31 Oct 2021
Creating my personal cloud with HashiCorp
6 projects | news.ycombinator.com | 30 Oct 2021
Yeah, this pains me too. Here's a relevant issue to keep an eye on:
I've used an nginx-based S3 proxy in the past to get around this. Not ideal but it works.
Datadog Reveals Hidden AWS Performance Problems
2 projects | dev.to | 25 Oct 2021
At Lob, we currently use Convox as our deployment platform, a “roll your own Platform-as-a-Service” that you can install to handle container orchestration on AWS’s ECS (Elastic Container Service). Convox is showing its age and this year we began the process of replacing Convox with HashiCorp’s Nomad, a flexible workload orchestrator to deploy and manage our containers on AWS.
How are you guys deploying containers?
1 project | reddit.com/r/homelab | 3 Oct 2021
its an orchestration tool similar to something like K8S https://www.nomadproject.io/
Podman in Linux
7 projects | news.ycombinator.com | 28 Sep 2021
That does seem better! Of course, there are a few lingering issues with support, but overall the trend is good: https://github.com/containers/podman/issues?q=is%3Aissue+is%...
Of course, there's no Swarm support, as evidenced by that very article:
> One known caveat is that Podman has not and will not implement the Swarm function. Therefore, if your Docker Compose instance uses Swarm, it will not work with Podman.
Feels like people will either be pigeonholed into Kubernetes for all of their deployments, or will have to migrate over to something like Hashicorp Nomad: https://www.nomadproject.io/
Curiously, it also supports Podman as a task driver: https://www.nomadproject.io/docs/drivers/podman
Which tool do you use to run scripts?
1 project | reddit.com/r/devops | 8 Sep 2021
I'm not sure I understand the situation here, but for something like running one-off / batch jobs across nodes, that sounds like something nomad should cover, or maybe Ansible depending on what you need.
What are some alternatives?
Rundeck - Enable Self-Service Operations: Give specific users access to your existing tools, services, and scripts
k3s - Lightweight Kubernetes
Dkron - Dkron - Distributed, fault tolerant job scheduling system https://dkron.io
kubernetes - Production-Grade Container Scheduling and Management
Docker Compose - Define and run multi-container applications with Docker
gocelery - Celery Distributed Task Queue in Go
SaltStack - Software to automate the management and configuration of any infrastructure or application at scale. Get access to the Salt software package repository here:
dapr - Dapr is a portable, event-driven, runtime for building distributed applications across cloud and edge.
serf - Service orchestration and management tool.
podman - Podman: A tool for managing OCI containers and pods.
consul - Consul is a distributed, highly available, and data center aware solution to connect and configure applications across dynamic, distributed infrastructure.
Juju - Universal Operator Lifecycle Manager (OLM) for Kubernetes operators, and operators for traditional Linux and Windows apps, with declarative integration between operators for automated microservice integration.