My Experiments with Korifi: Porting Korifi to K3s
summary
Korifi installs on k3s with concrete tweaks: disable Traefik and use Contour for Ingress; write out the kubeconfig with an explicit export because k3s does not create a readable file by default; install cert-manager and kpack, create CF and korifi namespaces, and stage installs to avoid the default load‑balancer flipping on when pods aren’t ready. Use Google Artifact Registry credentials (one long JSON key string) and expect builds to work on x86 but not yet for ARM, with CF push using Paketo buildpacks.
AI-written summary · about
chapters (15)
- 0:00Introduction to Korifi on K3s
- 2:08Why Korifi on K3s
- 3:59Installing K3s locally
- 5:04Prerequisites and setup
- 6:13Installing cert-manager and Kpack
- 7:29Creating namespaces
- 8:11Configuring Contour Ingress
- 8:52Setting up artifact registry
- 10:25Deploying Korifi components
- 11:29Finalizing Korifi setup
- 12:22ARM support limitations
- 13:27Configuring CF API and org
- 14:52Deploying app with CF push
- 15:57Build logs and verification
- 17:47Demo wrap-up and Q&A
related talks
29mK8s in a Submarine: Optimizing Delivery for Some of the Hardest-to-reach Systems on Earth
34mK3s Under the Hood: Building a Product-grade Lightweight Kubernetes Distro
40mBootiful Kubernetes Operators
43mSingle-node Kubernetes Clusters Using K3s with Benefits of GitOps
38mKonveyor: Replatform from Cloud Foundry to Kubernetes
30mCF^3 - Using Kubernetes as the Cloud Foundry IaaS
23mko - zero-config tool for deploying Go app on k8s
34mGitOps and KRO: A New Way to Control Cloud Infra