trafficjam
swarmsible
trafficjam | swarmsible | |
---|---|---|
5 | 11 | |
123 | 56 | |
- | - | |
0.0 | 5.6 | |
5 months ago | 24 days ago | |
Shell | Shell | |
- | GNU General Public License v3.0 or later |
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.
trafficjam
-
One traefik network or traefik on every network?
This is always a security vs convenience battle. Some time ago someone mentioned trafficjam https://github.com/kaysond/trafficjam which might be the solution for this. This way you can easily create one traefik network and let trafficjam take care of the firewall rules on this network so you container on that network are only allowed to talk to traefik.
-
Whalewall - easily manage firewall rules for Docker containers
Awesome! I did something similar, for a much more specific use case (isolate containers on a shared reverse proxy network) using bash (makes reading the code very easy). See https://github.com/kaysond/trafficjam
- Beta announcement: trafficjam - a Docker firewall for your reverse proxy network
-
Nginx reverse proxy manager and many docker-compose stacks: Best practices?
Or you can try this containerized firewall I wrote to address this very problem: https://github.com/kaysond/traefikjam You put your reverse proxy and all your web containers on one network, then the firewall daemon adds iptables rules to prevent containers from talking to each other except the reverse proxy can talk to everything.
swarmsible
-
Can any Hetzner user, please explain there workflow on Hetzner?
We use Docker Swarm for our deployments, so I will answer the questions based on that.
We have built some tooling around setting up and maintaining the swarm using ansible [0]. We also added some Hetzner flavour to that [1] which allows us to automatically spin up completely new clusters in a really short amount of time.
deploy from source repo:
- We use Azure DevOps pipelines that automate deployments based on environment configs living in an encrypted state in Git repos. We use [2] and [3] to make it easier to organize the deployments using `docker stack deploy` under the hood.
keep software up to date:
- We are currently looking into CVE scanners that export into prometheus to give us an idea of what we should update
load balancing:
- depending on the project, Hetzner LB or Cloudflare
handle scaling:
- manually, but i would love to build some autoscaler for swarm that interacts with our tooling [0] and [1]
automate backups:
- docker swarm cronjobs either via jobs with restart condition and a delay or [4]
maintain security:
- Hetzner LB is front facing. Communication is done via encrypted networks inside Hetzner private cloud networks
- [0] https://github.com/neuroforgede/swarmsible
- For Swarm mode users: What features do you miss/need from Kubernetes ecosystem?
-
How do you deploy your side-projects?
Pretty much the same as our goto for projects at work: Hetzner + Docker (Swarm) with some Ansible to orchestrate things
We have built some automation around cluster management over at https://github.com/neuroforgede/swarmsible.
I used to do everything in ansible, but Docker Stacks are just so much nicer to use.
In any case automation is king. I don't have to remember stuff if I can just look at some IaC Code :).
-
Docker Swarm with compose
Our tooling can be found here https://github.com/neuroforgede/swarmsible . It is not yet documented tbh, but most things are pretty straight forward to use if you have used ansible, docker etc already.
-
Ask HN: Have You Left Kubernetes?
Story of one of the projects I am involved in:
We came from Ansible managed deployments of vanilla docker with nginx as single node ingress with another load balancer on top of that.
Worked fine, but HA for containers that are only allowed to exist once in the stack was one thing that caused us headaches.
Then, we had a workshop for Rancher RKE. Looked promising at the start, but operating it became a headache as we didn't have enough people in the project team to maintain it. Certificates expiring was an issue and the fact that you actually kinda had to baby-sit the cluster was a turn off.
We killed the switch to kubernetes.
In the meantime we were toying around with Docker Swarm for smaller scale deployments and inhouse infrastructure. We didn't find anything to not like and are currently moving into that direction.
How we do things in Swarm:
1. Monitoring using an updated Swarmprom stack (https://github.com/neuroforgede/swarmsible/tree/master/envir...)
- Container / host monitoring strategy?
- I ported swarmprom to all new docker image versions - It still works just fine!
-
An updated Docker Swarm Monitoring Stack based on the original Swarmprom
For anyone interested in this, check out: https://github.com/neuroforgede/swarmsible/blob/master/environments/test/test-swarm/stacks/02_monitoring/README.md
- Show HN: I ported swarmprom to all new image versions
- Show HN: Swarmsible – Ansible Playbooks to Setup (and Manage) a Docker Swarm
What are some alternatives?
whalewall - Automate management of firewall rules for Docker containers
swarmsible-hetzner - Companion repository for https://github.com/neuroforgede/swarmsible with a focus on usage in the Hetzner cloud
nydus - Nydus - the Dragonfly image service, providing fast, secure and easy access to container images.
terraform-hcloud-kube-hetzne
docker-stack-deploy - Utility to improve docker stack deploy
Netdata - The open-source observability platform everyone needs
k8s-config-connector - GCP Config Connector, a Kubernetes add-on for managing GCP resources
nothelm.py - nothelm.py - opinionated docker stack project tool with templating support
csi-driver - Kubernetes Container Storage Interface driver for Hetzner Cloud Volumes
docker-volume-hetzner - Docker Volume Plugin for accessing Hetzner Cloud Volumes
woodpecker - Woodpecker is a simple yet powerful CI/CD engine with great extensibility.
eks-gha-auto-deploy-fortune - Easy demo of CI/CD of Commit -> GithubActions -> EKS