plural
docker-volume-hetzner
Our great sponsors
plural | docker-volume-hetzner | |
---|---|---|
21 | 5 | |
1,306 | 102 | |
2.3% | - | |
8.9 | 7.5 | |
2 days ago | 27 days ago | |
TypeScript | Go | |
GNU General Public License v3.0 or later | MIT License |
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.
docker-volume-hetzner
-
Can any Hetzner user, please explain there workflow on Hetzner?
we use https://github.com/costela/docker-volume-hetzner which is really stable.
CSI support for Swarm is in beta as well and already merged in the Hetzner CSI driver (https://github.com/hetznercloud/csi-driver/tree/main/deploy/...). There are some rough edges atm with Docker + CSI so I would stick with docker-volume-hetzner for now for prod usage.
Disclaimer: I contributed to both repos.
- Hetzner Cloud - is Volumes reliable? With Volumes mounted as /var/lib/docker for example
-
For Swarm mode users: What features do you miss/need from Kubernetes ecosystem?
The big one which would be nice: CSI support. This is currently being worked on, though. This said the current volume plugin landscape is not that dire once you realize that the local volume driver which arguably has a confusing name can work with NFS,CIFS,etc. out of the box as long as you can use fuse mounts. Besides that, we are quite happy with our setup where we use the community volume driver for our cloud provider - https://github.com/costela/docker-volume-hetzner/
-
Ask HN: Have You Left Kubernetes?
6. Volumes: Hetzner Cloud Plugin, see https://github.com/costela/docker-volume-hetzner
Reasons that we would dabble in k8s again:
1. A lot of projects are k8s only (see OpenFaaS for example)
- I do like it
What are some alternatives?
werf - A solution for implementing efficient and consistent software delivery to Kubernetes facilitating best practices.
awesome-hcloud - A curated list of awesome libraries, tools, and integrations for 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
crossplane - The Cloud Native Control Plane
nixery - Container registry which transparently builds images using the Nix package manager. Canonical repository is https://cs.tvl.fyi/depot/-/tree/tools/nixery
nydus - Nydus - the Dragonfly image service, providing fast, secure and easy access to container images.
kraken - P2P Docker registry capable of distributing TBs of data in seconds
cli - A command-line interface for Hetzner Cloud
k8s-config-connector - GCP Config Connector, a Kubernetes add-on for managing GCP resources
docker-volume-sshfs - sshfs docker volume plugin
helm - The Kubernetes Package Manager
swarmsible-hetzner - Companion repository for https://github.com/neuroforgede/swarmsible with a focus on usage in the Hetzner cloud