aks-store-demo-manifests VS distribution-spec

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

The great thing about Flux is that it can be bootstrapped using GitOps. So we'll point to a branch in my AKS Store Demo Manifests repo which has everything we need to get the cluster setup quickly.

# navigate to the home directory or wherever you want to clone the repo cd ~ # login to GitHub gh auth login --scopes repo,workflow # fork and clone the repo to your local machine gh repo fork https://github.com/pauldotyu/aks-store-demo-manifests.git --clone # make sure you are in the aks-store-demo-manifests directory cd aks-store-demo-manifests # since we are in a forked repo, we need to set the default to be our fork gh repo set-default # merge the "kustomize" branch into "main" git merge origin/kustomize # push the change up to your fork git push # set the repo url export GITHUB_REPO_URL=$(gh repo view --json url | jq .url -r) # set your GitHub username export GITHUB_USER= # set your GitHub personal access token export GITHUB_TOKEN=

gh repo fork https://github.com/pauldotyu/aks-store-demo-manifests.git --clone # change into the repo directory cd aks-store-demo-manifests

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.

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.

OCI stands for Open Container Initiative, and its goal as an organization is to define a specification for container formats and runtime.

https://opencontainers.org/

Here is Containerfile from the repo: https://github.com/ublue-os/bazzite/blob/main/Containerfile

apko allows us to build OCI container images from .apk packages.

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

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.

So somebody else created runj (runj is an experimental, proof-of-concept OCI-compatible runtime for FreeBSD jails.) https://github.com/samuelkarp/runj