swarmkit VS traefik

It's supported, though the development pace is rather slow. The are new features (the latest release brought support for the Container Storage Interface) and bugs and issues are worked on by the few maintainers the project has. You can check the repo here: https://github.com/moby/swarmkit

So the thing is support for Swarm was delegated to Mirantis, https://www.mirantis.com/blog/mirantis-will-continue-to-support-and-develop-docker-swarm/ since it was delegated very little was done to move forward swarm _> https://github.com/moby/swarmkit/commits/master , docker swarm itself (docker the company) is deprecated https://github.com/docker-archive/classicswarm . I think because there's no way to monetize swarm there's no real push for new features hence my assumption of deprecation.

Feature request: Enable "--device" in "stack deploy" for Confidential Computing

This doesn't look that abandoned? https://github.com/moby/swarmkit

Or are you talking about swarm the product (versus docker swarm mode)

I don’t feel a momentum in Docker Swarm development, seeing pull requests like #3072 sitting idle for half a year, originally from 2016.

privileged not being supported is problematic, but there are PRs for it on swarmkit, see https://github.com/moby/swarmkit/pull/3072 - let's see if that gets in.

swarm ha placement

It is already in a different repo: moby/swarmkit

Docker Swarm is dead. It should not be used for new projects because the competitive products are much better and more optimal. Check their repo bro - last commit 3months ago. https://github.com/docker/swarmkit https://www.reddit.com/r/docker/comments/ituysl/why_people_are_saying_docker_swarm_is_in_life/ Why would you start a project with a tool which got no future? Let's then use Silverlight or any shit like that.

Mostly it just needs resource defaults merged and some abstract type support so load balancer config doesn't have to be entirely by labels and I would never shift from it.

Pronounced "traffic", Traefik is a modern HTTP reverse proxy and load balancer aimed at making deploying microservices easier. It integrates with your existing infrastructure components such as Docker, Kubernetes, and others, and configures itself automatically and dynamically. The latest version adds lots of new options and enhancements such as adding healthcheck options, support for custom headers, and more. Read the migration guide on how to update to the latest version which is now required due to breaking changes.

> I think etcd is basically a k8s only project now

I hate etcd with the best of them, but etcd is used in a lot more places than just kubernetes:

https://github.com/apache/apisix/blob/master/docs/en/latest/...

https://github.com/traefik/traefik#:~:text=Etcd,

https://github.com/zalando/patroni#patroni-a-template-for-po...

https://github.com/purpleidea/mgmt/tree/0.0.26/etcd (this one shows up on HN quite a bit)

https://github.com/sorintlab/stolon#features

It's actually one of the major reasons I wouldn't touch those projects

However, it's very unlikely that .NET developers will directly expose their Kestrel-based web apps to the internet. Typically, we use other popular web servers like Nginx, Traefik, and Caddy to act as a reverse-proxy in front of Kestrel for various reasons:

Not as good though. Case in point: https://github.com/traefik/traefik/issues/5472#issuecomment-... (that's just from this morning)

I'm speak objectively here. Of course, any built-in auto HTTPS that works (more or less) is better than none. Traefik uses an ACME library that was originally written for Caddy. After the original author left that project, Traefik team started maintaining it. Caddy's users' requirements exceeded what the library was capable of, but unfortunately there was friction in getting it to achieve our requirements. So I ended up writing a new ACME client library in Go and, together with upgrades in CertMagic (Caddy's auto-TLS lib), Caddy has the more flexible, robust, and capable auto-HTTPS functionality.

That is to say, not all auto-HTTPS functionalities are the same.

We'll use Traefik, an open source cloud native gateway that can plug into a Kubernetes cluster. It has the concept of "middleware" that can process API requests before passing them through to a backend. We can configuring a rate limit for all of our API endpoints by matching on the request path:

I did the same question here and here

Sadly there is currently no way of doing so. https://github.com/traefik/traefik/issues/6999