plural
swarmsible
Our great sponsors
plural | swarmsible | |
---|---|---|
21 | 11 | |
1,304 | 54 | |
2.0% | - | |
9.1 | 5.6 | |
3 days ago | 2 days ago | |
TypeScript | Shell | |
GNU General Public License v3.0 or later | 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.
plural
-
Curious if anyone has adopted a stack to do raw data ingestion in Databricks?
I’ve just recently found out about plural. Perhaps give them a try? I think they have a cool idea for quickly deploying an ELT infrastructure. Perhaps check them out?
- Self-Hosted Open-Source Alternative to a Managed Service
- Plural - An open-source alternative to managed services
- An open-source alternative to managed services
- GitHub - pluralsh/plural: Deploy open source software on Kubernetes in minutes
- Deploy open-source software on Kubernetes in record time.
- OSS Kubernetes App deployment platform
- Show HN: Plural.sh-Deploy, secure and scale open-source apps on your cloud
- OSS Kubernetes App Deployment platform built on Elixir
- Deploy open-source software in your own Kubernetes cluster within minutes.
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
- 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?
werf - A solution for implementing efficient and consistent software delivery to Kubernetes facilitating best practices.
swarmsible-hetzner - Companion repository for https://github.com/neuroforgede/swarmsible with a focus on usage in the Hetzner cloud
kube-fledged - A kubernetes operator for creating and managing a cache of container images directly on the cluster worker nodes, so application pods start almost instantly
nydus - Nydus - the Dragonfly image service, providing fast, secure and easy access to container images.
nixery - Container registry which transparently builds images using the Nix package manager. Canonical repository is https://cs.tvl.fyi/depot/-/tree/tools/nixery
terraform-hcloud-kube-hetzne
kraken - P2P Docker registry capable of distributing TBs of data in seconds
docker-stack-deploy - Utility to improve docker stack deploy
k8s-config-connector - GCP Config Connector, a Kubernetes add-on for managing GCP resources
Netdata - The open-source observability platform everyone needs
helm - The Kubernetes Package Manager