Document how to use `kbld` with `kind`?

[evankanderson]

Kind is a popular local development option. Unfortunately, the default configuration of kind requires running kind load docker-image $IMAGENAME.

It's hard to extract the built image names to kind load docker-image. It would be nice to have something like a --kind flag to do this step as long as Kind needs it. (The other option is to run a local registry, but this is harder than needed, especially with additional tools like pack or ko that may need flags about trusting the registry.)

[pivotaljohn]

Making sure we got this...

1. you're using kbld to orchestrate some image builds, including configuration for ko and/or pack (or others...)
2. OOTB, kbld will push built images to your configured Destination(s); this request is to be able to instead "load" to a local kind cluster.
3. you're asking for this because in the local development situation, standing up a local registry is kindofa pain; this feature would close the loop with the kind cluster, faster, with few moving parts.

Did we get that right?

[pivotaljohn]

An alternative thought...

Not unlike the Buildkit for kubectl builder...

• when kbld creates images, those are initially stored in the local image cache.
• if we were to run kbld in cluster (i.e. a pod with kbld, dependencies, with access to the container runtime), that local image cache is likely the same place where kind load ... puts images.
• if the kind cluster were a single node, then the image might just be "automatically" available, locally. ... ?

[pivotaljohn]

Looking into whether it's more supportable/useful to enhance kbld itself (e.g. give the user control over where built images are published) vs. documenting/providing a configuration for a local workflow using kind.

[cppforlife]

this seems like a pretty reasonable extension to various builders that use docker build. question is how to best configure this... could be a flag, or could be some configuration on builders.