mizu
kube-fledged
| mizu | kube-fledged | |
|---|---|---|
| 40 | 10 | |
| 4,543 | 1,204 | |
| - | - | |
| 9.7 | 4.7 | |
| over 1 year ago | 3 months ago | |
| C | 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.
mizu
-
The Future of Open Source, or Why Open Core Is Dead
UP9, Founded 2019, 3,743 stars
-
Interesting tools?
API traffic viewer for kubernetes(kinda like wireshark): https://github.com/up9inc/mizu
- Mizu - The API Traffic Viewer for Kubernetes
- PI traffic viewer for Kubernetes enabling you to view all API communication between microservices
- What are Kubernetes developers missing? What tool or library do you wish you had?
-
Hacker News top posts: Apr 12, 2022
Mizu – API traffic viewer for Kubernetes\ (4 comments)
- Up9inc/mizu: API traffic viewer for Kubernetes:view API comms btw microservices
-
Gain Visibility into Istio mTLS Traffic with Mizu
Mizu is an open source multi-protocol traffic viewer for Kubernetes that can be used to view API traffic between microservices communicating over synchronous and message queue protocols.Traffic viewing is essential for troubleshooting bugs, defects, and regressions. It helps developers find the root cause of a problem quicker and therefore deploy faster. Mizu is available to download as an executable binary or as source code directly from its GitHub repository.
-
How do you see TLS traffic on K8's?
As a reminder, Mizu is a lightweight API traffic viewer for Kubernetes that doesn't require any code instrumentation. It provides complete visibility to all API traffic and payloads with support for different protocols and encryption. A short video describing the new feature can be found here [Add link to video].
kube-fledged
-
Musl 1.2.4 adds TCP DNS fallback
Exactly. Part of the appeal to consolidate all of our container images to use Debian-slim is the ability to optimise the caching of layers, both in our container registry but also on our kubernetes cluster’s nodes (which can be done in a consistent manner with kube-fledged[1]).
[1] https://github.com/senthilrch/kube-fledged
-
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
https://github.com/uber/kraken
https://nydus.dev/
-
Interesting tools?
kube fledged - pre pull containes in nodes: https://github.com/senthilrch/kube-fledged
-
Kube-fledged: Cache Container Images in Kubernetes
kube-fledged is a kubernetes add-on or operator for creating and managing a cache of container images directly on the worker nodes of a kubernetes cluster. It allows a user to define a list of images and onto which worker nodes those images should be cached (i.e. pulled). As a result, application pods start almost instantly, since the images need not be pulled from the registry. kube-fledged provides CRUD APIs to manage the lifecycle of the image cache, and supports several configurable parameters in order to customize the functioning as per one’s needs. (URL: https://github.com/senthilrch/kube-fledged)
- Introducing GKE image streaming for fast application startup and autoscaling
-
Can Kubernetes pre-pull and cache images?
I found recently this tool kube-fledged that should do what you want..
- senthilrch/kube-fledged: A kubernetes add-on for creating and managing a cache of container images directly on the cluster worker nodes, so application pods start almost instantly
-
Best way to mirror images to improve their availability for a cluster?
I recommend you also look at kube-fledged this is more appealing IMHO.
What are some alternatives?
s3-proxy - S3 Reverse Proxy with GET, PUT and DELETE methods and authentication (OpenID Connect and Basic Auth)
kraken - P2P Docker registry capable of distributing TBs of data in seconds
easyssh-proxy - easyssh-proxy provides a simple implementation of some SSH protocol features in Go
ImageWolf - Fast Distribution of Docker Images on Clusters
kubernetes - Production-Grade Container Scheduling and Management
image-cache-daemon
GVM - Go Version Manager
containers-roadmap - This is the public roadmap for AWS container services (ECS, ECR, Fargate, and EKS).
Gitea - Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD
Dragonfly - This repository has be archived and moved to the new repository https://github.com/dragonflyoss/Dragonfly2.
Gogs - Gogs is a painless self-hosted Git service
kubefwd - Bulk port forwarding Kubernetes services for local development.