Wanted to document the logistics behind my KubeCon 2022 live-cluster demonstration of Lula. I'll consider it a success if even one person finds the process valuable or enables them to also created offline kubernetes demonstrations without worry.
I used Rancher Desktop do to it's innate ability to treat air gap as a first class citizen. Once kubernetes is enabled, Rancher Desktop downloads the required artifacts and stores them locally such that internet connecitivty is no longer required to setup kubernetes - even if you reset your cluster.
My demonstration was requiring istio service mesh as a pre-deployed system. As such, I needed to ensure I could repeatably deploy istio to my local cluster offline. I then created a zarf package for istio base and istiod helm orchestration with the required images and performed a zarf package create in the istio directory to produce the zarf package zarf-packge-istio-package-amd64.tar.zst.
I wanted to deploy simple workloads without dependencies on other services. I used nginx with a simple deployment.yaml manifest and the nginx image. The manifest contains a variable that can be modified imperatively during deployment in a format that zarf understands. Performing the zarf package create from the project root produced the zarf package zarf-package-compliance-demo-amd64.tar.zst.
- I had previously performed a
zarf initwhich downloads and caches the init package for future use. - I built the lula binary from the repository
- Rancher Desktop
- Reset Cluster
zarf init- uses a local cache of the init package
zarf package deploy zarf-packge-istio-package-amd64.tar.zst --confirmzarf package deploy zarf-package-compliance-demo-amd64.tar.zst --confirm --set INJECT=truelula execute oscal-component.yaml- This produces a passing result
zarf package deploy zarf-package-compliance-demo-amd64.tar.zst --confirm --set INJECT=falselula execute oscal-component.yaml- This produces a failing result
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent