Investigate airgap e2e testing with imgpkg

[johnSchnake]

Right now we use sonobuoy images ... to pull/push/list the images a plugin will use. However, https://carvel.dev/ has imgpkg and kbld which may be extremely useful here.

Perhaps we can use sonobuoy images to list those images and eventually create an image lock file which can be used by others to push/pull those images as necessary. It would be nice if we could (1) be out of the business of having to push/pull images ourselves (2) the process would be more consistent and better supported.

Questions I have though:

• can we create an image lock file without a 'deployment'? All the examples seem to show those two ideas more intertwined but can we just list the images we want and then deal with them as a bundle?
• can we tell imgpkg to use an image lock like the one above to prepull images into the cluster, atleast into the airgapped repo? In their airgap example they show pulling the bundle as a tarball and that moving the actual images as well. However, the images go into the new location as different tags on the bundle name. E2E tests upstream allow us to override the image repos but not the image names themselves. I think

[johnSchnake]

So when we want to specify that the images are in a specific registry (rather than a list of registries) it renames them in a unique way and it does make it problematic for the e2e tests.

imgpkg has a proposal about overriding the tags: https://github.com/vmware-tanzu/carvel-imgpkg/issues/60

Also, I wanted to note that you can list a series of images without them being a part of a deployment, etc. See https://github.com/vmware-tanzu/carvel-kbld/issues/231

[stale[bot]]

There has not been much activity here. We'll be closing this issue if there are no follow-ups within 15 days.