spire
kraken
Our great sponsors
| spire | kraken | |
|---|---|---|
| 1 | 14 | |
| 4 | 5,820 | |
| - | 0.9% | |
| 6.9 | 4.0 | |
| 8 months ago | 3 months ago | |
| Python | Go | |
| Apache License 2.0 | Apache 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.
spire
-
Ask HN: Have You Left Kubernetes?
CI/CD pipeline is GitHub Actions which run SSH commands on our servers that execute deployment scripts: https://github.com/bugout-dev/spire/blob/main/deploy/deploy....
We use systemd to manage services.
We use Ansible to set up servers.
Our infrastructure spans AWS, Google Cloud, and servers in a datacenter.
kraken
-
BTFS (BitTorrent Filesystem)
https://github.com/uber/kraken?tab=readme-ov-file#comparison...
"Kraken was initially built with a BitTorrent driver, however, we ended up implementing our P2P driver based on BitTorrent protocol to allow for tighter integration with storage solutions and more control over performance optimizations.
Kraken's problem space is slightly different than what BitTorrent was designed for. Kraken's goal is to reduce global max download time and communication overhead in a stable environment, while BitTorrent was designed for an unpredictable and adversarial environment, so it needs to preserve more copies of scarce data and defend against malicious or bad behaving peers.
Despite the differences, we re-examine Kraken's protocol from time to time, and if it's feasible, we hope to make it compatible with BitTorrent again."
It's not an overlay provider itself, but uber/kraken is a "P2P Docker registry capable of distributing TBs of data in seconds". It uses the bittorrent protocol to deliver docker images to large clusters.
-
Resilient image cache/mirror
https://github.com/uber/kraken is promising, still new but it's not that complicated to go awry
Kraken seems unmaintained: https://github.com/uber/kraken/issues/313
-
DockerHub replacement stratagy and options
For within your boundary of control, whether that be r/selfhosting, r/homelab, or enterprise a small registry or something like uber's kraken registry makes more sense.
-
MinIO passes 1B cumulative Docker Pulls
Uber Engineering open-sourced Kraken [1], their peer-to-peer docker registry. I remember it originally using the BitTorrent protocol but in their readme they now say it is "based on BitTorrent" due to different tradeoffs they needed to make.
As far as I know there aren't any projects doing peer-to-peer distribution of container images to servers, probably because it's useful to be able to use a stock docker daemon on your server. The Kraken page references Dragonfly [2] but I haven't grokked it yet, it might be that.
It's also possible that in practice you'd want your CI nodes optimized for compute because they're doing a lot of work, your registry hosts for bandwidth, and your servers again for compute, and having one daemon to rule them all seems elegant but is actually overgeneralized, and specialization is better.
-
Ask HN: Have You Left Kubernetes?
If you're pulling big images you could try kube-fledged (it's the simplest option, a CRD that works like a pre-puller for your images), or if you have a big cluster you can try a p2p distributor, like kraken or dragonfly2.
Also there's that project called Nydus that allows starting up big containers way faster. IIRC, starts the container before pulling the whole image, and begins to pull data as needed from the registry.
https://github.com/senthilrch/kube-fledged
https://github.com/dragonflyoss/Dragonfly2
-
Kube-fledged: Cache Container Images in Kubernetes
Uber Kraken: Kraken is a P2P Docker registry capable of distributing TBs of data in seconds (URL: https://github.com/uber/kraken)
-
How to handle registry outages ? Registry outage contingency plans ?
Might want to consider a private p2p solution like https://github.com/uber/kraken or similar.
-
How to handle locally build container images across nodes? Container Registry the only way?
Cost, availability, upkeep. Same as any other service. There are alternatives… https://github.com/uber/kraken
What are some alternatives?
Dragonfly - This repository has be archived and moved to the new repository https://github.com/dragonflyoss/Dragonfly2.
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
containers-roadmap - This is the public roadmap for AWS container services (ECS, ECR, Fargate, and EKS).
deckschrubber - Deckschrubber inspects images of a Docker Registry and removes those older than a given age. :high_brightness::ship:
image-cache-daemon
ipdr - 🐋 IPFS-backed Docker Registry
tagger - Kubernetes container image orchestration.
ImageWolf - Fast Distribution of Docker Images on Clusters
docker-registry.helm - Helm chart for a Docker registry. Successor to stable/docker-registry chart.
s3proxy - Access other storage backends via the S3 API
plural - Deploy open source software on Kubernetes in record time. 🚀
kraken - Kraken CI is a continuous integration and testing system.