kong-pongo Upload Pongo images instead of rebuilding them

Currently Pongo builds images locally after installation. We can probably reduce test times in CI if we upload the images to a docker repo and just pull them. This will also improve the experience for users behind corporate proxies and curated repositories.

2 issues I can see for now;

since they are development images, they'll probably be flagged for security issues, do we want to maintain this? (or don't we care about the red flags?)
Pongo itself is not versioned. But the images are somewhat tightly coupled to the Pongo version that build it.

Oct 01 '21 11:10 Tieske

you can release pongo aligned with Kong Gateway release schedule, so your pongo docker image version is interlinked with Kong version?

Oct 01 '21 11:10 kongguogang

I was thinking about including the Pongo version that created the image, inside the image. Such that a user can extract it and use it as intended.

Oct 01 '21 14:10 Tieske

I think it would be more user friendly to let it be a separate image.

Dec 01 '21 18:12 esatterwhite

I was thinking about including the Pongo version that created the image, inside the image. Such that a user can extract it and use it as intended.

It would be nice to have an image that was tagged with the highest version of kong that it supported. Right now pongo doesn't have any versioning associated with as far as I can tell. That a little troublesome with the documented installation process of just cloning the repo. I don't have much control over one install to the next.

I could pin git hashes, but that is a bit difficult to maintain and reason about.

Dec 02 '21 21:12 esatterwhite