push to ghcr.io

[jhrozek]

The intent is for the resulting images to be pushed to ghcr.io instead of quay as the default

[jhrozek]

@RoddieKieley I'm sorry my notes from last week are incomplete, was the intent that we do this (perhaps because of any secrets that might need to be set up or permissions) or were you going to?

No pressure at all, just making sure we're tracking things that need to be helped with.

[RoddieKieley]

@jhrozek I think it was unclear due to the fact that we were focused on the discussion of getting the repo configured and thus just didn't get into the specifics of what happens after that. I was unsure as to the requirements for me to be generating container images related to this repository in this organization and was looking to discuss today. A key question was if we could manually produce the three container images before setting up the automation that would take care of it so that we could both test ghcr.io usage as well as look toward operatorhub.io with the current single version targeted - v0.4.2.

[jhrozek]

I'm going through the notes from our call, I hope that Gemini and I got things right - but according to the notes we agreed that you'll first test your level of privileges by trying to publish the images and if you either need help or more elevated (org-level?) privilegesm then @rdimitrov is here to help.