If I run imagebuilder via argo-workflows, tekton, gitlab (with a gitlab runner in k8s), jenkins with the kubernetes plugin etc … imagebuilder will fail.
This is because somewhere around packer a server is started and there is a callback to that server when the vm is finished building.
Via kubernetes the source can be exposed via a k8s service or ingress … but there is no way to pass this into packer (e.g. via an env var like CALLBACK_URI).
I might be able to submit a pull request but I haven’t been able to locate in which git repo where the server is started up. I’ve submitted issue requests in a few locations without any response.
Could someone who knows point me in the right direction (not guess), or maybe take this one up as a todo item?
Its ironic to me that the tools to build kubernetes images can’t run in kubernetes.
Besides just building images, the ability to run via kubernetes opens up a lot more testing options as the testing of imagebuilder is being revisited.
Do i create a pull request in image builder? Packer? The packer sdk? Every individual provider?