Move from gcr to ghcr for the router and examples

[dolfolife]

Summary

The intent of these changes is to move the registry from GCR to GHCR.

TODO

• Router
• Examples
• Update the veba.sbom file with the new urls

Change Type

What type of changes does your code introduce to the VMware Event Broker Appliance?

Put an x in all boxes that apply

Please check the types of change your PR introduces:

• Bugfix (non-breaking change which fixes an issue)
• Feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality not to work as expected)
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no API changes)
• Build related changes
• Documentation changes
• Other (please describe): Image location

Additional Context

I do not have much context where most of the images are built. I took a look at the Github Action and found that the router is built there but none of the examples are. I am working on deleting the dependency of VEBA from GCR and moving to the GitHub registry since it is free for public repositories.

[vmwclabot]

@dolfolife, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <[email protected]> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit 23e328c must be signed by [email protected]

[vmwclabot]

@dolfolife, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <[email protected]> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit 23e328c must be signed by [email protected]

[vmwclabot]

@dolfolife, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <[email protected]> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit 23e328c must be signed by [email protected]

[dolfolife]

@lamw I am ready to review these changes.

The main review would be to push all examples and the router using ghcr to this repository using the documentation I added in the PR.

Notes:

• There was a FROM lamw/<repo> in one of the dockerfile on the example templates of a private repo that I deleted to make the build work.
• Some of the python examples had a conflict on the requirements.txt that required a upgrade of a min version of a dependency.
• I had to run go mod tidy in some of golang examples that made some changes.
• There is still a case of images and labels with ghcr.io that when done manually it adds the image to the right repository but keeps it private. This step of making images public and maybe attach them to this repo might not work in all case scenarios.

[dolfolife]

@embano1 made some changes. I hope I understood your change requests, but if I miss something please send me a message. Happy to continue reviewing this.

[embano1]

@embano1 made some changes. I hope I understood your change requests, but if I miss something please send me a message. Happy to continue reviewing this.

Yeah, mostly the Docker login stuff which can go away in all workflows since we're using ko defaults

[embano1]

@dolfolife good job! Don't worry about the integration test (OpenFaaS): I'll fix later. Can you please squash your commits?

[embano1]

Is @lamw going to rebuild all images?

[embano1]

Thx a ton @dolfolife