aks-store-demo
distribution-spec
aks-store-demo | distribution-spec | |
---|---|---|
5 | 55 | |
106 | 749 | |
- | 3.6% | |
9.2 | 7.8 | |
7 days ago | 6 days ago | |
Bicep | Go | |
MIT License | 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.
aks-store-demo
-
Bootstrap your GitOps-enabled AKS cluster with Terraform: A code sample using the Flux v2 K8s Extension
The dev-app Kustomization deploys the GitRepository resource which points to the flux-k8s-ext branch in my AKS Store Demo Manifests repo, and Kustomization resource to deploy the AKS Store Demo application
-
Progressive Delivery on AKS: A Step-by-Step Guide using Flagger with Istio and FluxCD
We'll move really fast through the AKS cluster provisioning, bootstrapping process, and deploying the AKS Store Demo sample app.
-
Automating Image Updates with FluxCD on AKS
# navigate to the home directory or wherever you want to clone the repo cd ~ # fork and clone the repo to your local machine gh repo fork https://github.com/azure-samples/aks-store-demo.git --clone # make sure you are in the aks-store-demo directory cd aks-store-demo # since we are in a forked repo, we need to set the default to be our fork gh repo set-default
-
Git going with GitOps on AKS: A Step-by-Step Guide using FluxCD AKS Extension
We'll deploy my new favorite demo app, AKS Store Demo to our AKS cluster and then make some changes to the application and see how FluxCD handles them.
-
Just Enough Git for GitOps
> git clone https://github.com/smurawski/aks-store-demo > cd aks-store-demo > git checkout origin/helm > git checkout -b helm > git remote add upstream https://github.com/Azure-Samples/aks-store-demo > git fetch upstream > git rebase upstream/main Successfully rebased and updated refs/heads/helm.
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?
aks-store-demo-manifests
jib - π Build container images for your Java applications.
aks-store-demo - Sample microservices app for AKS demos, tutorials, and experiments
spin - Spin is the open source developer tool for building and running serverless applications powered by WebAssembly.
website - π Source code for OpenGitOps website
proxmox-lxc-idmapper - Proxmox unprivileged container/host uid/gid mapping syntax tool.
weave - Simple, resilient multi-host containers networking and more.
appleprivacyletter - An open letter against Apple's new privacy-invasive client-side content scanning.
flux2 - Open and extensible continuous delivery solution for Kubernetes. Powered by GitOps Toolkit.
dive - A tool for exploring each layer in a docker image
helm - The Kubernetes Package Manager
bartholomew - The Micro-CMS for WebAssembly and Spin