UNOFFICIAL/EXPERIMENTAL. This page is generated from a live receipt. Run npm run serverless-oci-gitops:proof to repeat it, or npm run serverless-oci-gitops:proof:verify to check the committed result.
This run started with the public bitnami/nginx@24.0.2 installer package. cub installer pulled it using an empty registry credential file and an isolated cub home with no ConfigHub token. It rendered the http-clusterip configuration as 6 Kubernetes objects.
The same cub installer setup command used --output-oci to package those rendered files as a second OCI artifact. The installer pulled its own output back and checked the object-set digest before returning. Flux then pulled that output digest and applied it to a throwaway cluster. NGINX reached 1/1 ready replicas.
| Check | Result |
|---|---|
| Public installer OCI pulled without registry credentials | pass |
| ConfigHub token present | no |
| Rendered objects | 6: Deployment, Namespace, NetworkPolicy, PodDisruptionBudget, Service, ServiceAccount |
| Rendered OCI written by | cub installer setup --output-oci |
| Output OCI pulled back and compared with the reviewed files | pass |
| Output digest | sha256:ac000807c979534860947ea6876e848fa33af7d09230349fb55fdae91991b02a |
| Flux OCI source | ready |
| Flux Kustomization | ready |
| Flux-observed digest matches output | pass |
| NGINX | 1/1 ready |
| Cleanup | pass |
This proves the temporary, no-account OCI -> work -> OCI -> Flux path for this NGINX configuration. It does not prove a permanently hosted output service, and it does not cover charts whose hooks or CRDs need lifecycle routes.
- Input publication receipt:
runs/installer-oci/bitnami-nginx/24.0.2/installer-package-publication-receipt.yaml - Live receipt:
runs/serverless-oci-gitops-proof/receipt.yaml