Enhancement
Use application/vnd.oci.image.layer.v1.tar+gzip for layers instead of plain .tar.
Why?
Although KCL code is quite small, so the savings are negligible, many tools will only work with GZIP'd layers.
For example, the Flux OCIRepository:
Note that the selected OCI layer must be compressed in the tar+gzip format.
Specifically, I am publishing KCL modules that have both KCL source as well as the raw CRD YAML for Kubernetes. This way, I can actually use that same OCI bundle to create the types on the cluster as I use to template objects of those types w/ KCL!
Enhancement
Use
application/vnd.oci.image.layer.v1.tar+gzipfor layers instead of plain.tar.Why?
Although KCL code is quite small, so the savings are negligible, many tools will only work with GZIP'd layers.
For example, the Flux
OCIRepository:Specifically, I am publishing KCL modules that have both KCL source as well as the raw CRD YAML for Kubernetes. This way, I can actually use that same OCI bundle to create the types on the cluster as I use to template objects of those types w/ KCL!