kitops
distribution-spec
kitops | distribution-spec | |
---|---|---|
6 | 55 | |
188 | 749 | |
82.9% | 3.6% | |
9.7 | 7.8 | |
3 days ago | 4 days ago | |
Go | 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.
kitops
- The Docker build – Docker run workflow missing from AI/ML?
-
KitOps Release v0.2–Introducing Dev Mode and the ability to chain ModelKits
Currently dev mode is only available on MacOS, although we plan to expand it to additional platforms and include more inference runtimes and utilities for models, data, and code. File an issue in our GitHub repository telling us what platform we should tackle next, or how to improve the Kit dev command in general - we love community feedback!
-
Streamlining AI/ML Deployment with ModelKits: Innovations and Future Directions
Yesterday, Brad Micklea, Jozu CEO and KitOps maintainer, was a guest on the Partially Redacted podcast hosted by Sean Falconer. The 45-minute conversation (which you can listen to here) covered a lot of ground. Specifically, they discussed the current state of the KitOps project, where the project is headed, and some of our early ideas for productizing and releasing Jozu, which builds on top of KitOps.
-
Introducing the New GitHub Action for using Kit CLI on MLOps pipelines
As we continue to innovate and improve KitOps, your feedback is invaluable to us. Whether you're encountering challenges, have suggestions for new features, or simply want to share your success stories, we're all ears. You can provide feedback on our GitHub repo or our Discord channel.
-
Say hello to Kit–An open source solution to MLOps complexity
You can learn more about Kit here: https://kitops.ml, and support us by [giving Kit a star on GitHub]!(https://github.com/jozu-ai/kitops)
-
The transitory nature of MLOps: Advocating for DevOps/MLOps coalescence
And checkout the source code here: https://github.com/jozu-ai/kitops
distribution-spec
-
The transitory nature of MLOps: Advocating for DevOps/MLOps coalescence
Back in 2013, a little company called Docker made it really easy to start using containers to package up applications. A big key to their success was the OCI (you can learn about that here), an industry wide initiative to have standards around how we package up our applications. Because of OCI standards, we have hundreds (maybe thousands?) of tools that can be combined to manage and deploy applications. So why aren’t we using this for packaging up Notebooks and AI models as well? It would make deploying, sharing, and managing our models easier for everyone involved.
-
The Road To Kubernetes: How Older Technologies Add Up
Kubernetes on the backend used to utilize docker for much of its container runtime solutions. One of the modular features of Kubernetes is the ability to utilize a Container Runtime Interface or CRI. The problem was that Docker didn't really meet the spec properly and they had to maintain a shim to translate properly. Instead users could utilize the popular containerd or cri-o runtimes. These follow the Open Container Initiative or OCI's guidelines on container formats.
-
Coexistence of containers and Helm charts - OCI based registries
OCI stands for Open Container Initiative, and its goal as an organization is to define a specification for container formats and runtime.
-
Bazzite – a Steam0S-like OCI image for desktop, living room, and handheld PCs
https://opencontainers.org/
Here is Containerfile from the repo: https://github.com/ublue-os/bazzite/blob/main/Containerfile
-
Distroless images using melange and apko
apko allows us to build OCI container images from .apk packages.
- OCI image from dockerfile
- Fat OCI images are a cultural problem
-
Progressive Delivery on AKS: A Step-by-Step Guide using Flagger with Istio and FluxCD
Flagger's load testing service can be installed via a Kustomization resource based on manifests packaged as an artifact in an Open Container Initiative (OCI) registry
-
Creating Kubernetes Cluster With CRI-O
CRI-O is a lightweight container runtime for Kubernetes. It is an implementation of Kubernetes CRI to use Open Container Initiative (OCI) compatible runtimes for running pods. It supports runc and Kata Containers as the container runtimes, but any OCI-compatible runtime can be integrated.
-
What is the current status of Docker and how far is it from getting ported?
So somebody else created runj (runj is an experimental, proof-of-concept OCI-compatible runtime for FreeBSD jails.) https://github.com/samuelkarp/runj
What are some alternatives?
aqueduct - Aqueduct is no longer being maintained. Aqueduct allows you to run LLM and ML workloads on any cloud infrastructure.
jib - 🏗 Build container images for your Java applications.
glide - 🐦 A open blazing-fast simple model gateway for rapid development of production GenAI apps
spin - Spin is the open source developer tool for building and running serverless applications powered by WebAssembly.
proxmox-lxc-idmapper - Proxmox unprivileged container/host uid/gid mapping syntax tool.
appleprivacyletter - An open letter against Apple's new privacy-invasive client-side content scanning.
dive - A tool for exploring each layer in a docker image
bartholomew - The Micro-CMS for WebAssembly and Spin
runc - CLI tool for spawning and running containers according to the OCI specification
skopeo - Work with remote images registries - retrieving information, images, signing content
containerd - An open and reliable container runtime
crun - A fast and lightweight fully featured OCI runtime and C library for running containers