Migrate fn images to ghcr

[efiacor]

Release process doc has been removed. Intentional?

kptdev/krm-functions-catalog@0985682

https://github.com/kptdev/krm-functions-catalog/blob/render-helm-chart/v0.3/RELEASING.md

• New branch and tag for each image release.
• Update docs script which patches the branch.

fn docs URL. Where is this hosted?

• https://catalog.kpt.dev/

Existing gh action workflow in place to push to ghcr

• https://github.com/kptdev/krm-functions-catalog/actions/runs/15506571982/job/43662175763

Which executes this script - https://github.com/kptdev/krm-functions-catalog/blob/master/dev/cd/after-push-to-branch#L41

One fn currently setup to push to ghcr:

NOTE: Uses a local Makefile which executes a custom google image build tool - https://github.com/ko-build/ko?tab=readme-ov-file

• https://github.com/kptdev/krm-functions-catalog/tree/master/functions/go/set-name-prefix

Current images in the registry: (The registry seems to be private. Should this be public?)

• https://github.com/kptdev/krm-functions-catalog/pkgs/container/krm-functions-catalog%2Fset-name-prefix

set-name-prefix has no associated docs and is not included in the catalog - https://catalog.kpt.dev/

The image also gets pushed to gcr.io from some other CI system.
https://console.cloud.google.com/artifacts/docker/kpt-fn/us/gcr.io/set-name-prefix?inv=1&invt=AbzmhQ

Release gh action has no runs yet. Not sure why as should have been triggered when tags are pushed.

• https://github.com/kptdev/krm-functions-catalog/blob/master/.github/workflows/after-tag-with-version.yaml#L20

Migration plan?

• Convert all metadata.yaml to krm-fn-metadata.yaml?

  • Do we need to maintain the gcr.io pushes?

• Branching/tagging? Do we stick with that process?

• How to handle doc updates/creation?

  • Existing process isn't viable - https://github.com/kptdev/krm-functions-catalog/blob/render-helm-chart/v0.3/RELEASING.md#updating-function-docs

[CsatariGergely]

• Convert all metadata.yaml to krm-fn-metadata.yaml?

  • This is the quick and dirty process
  • Do we need to maintain the gcr.io pushes?
    • No we should not. We should push only to ghcr.
    • We should make the ghcr repo public.

• We should have a separate cadence for all the images

• We should build automation for update-function-docs

• Branching/tagging? Do we stick with that process?

  • Follow the deleted process from here

• How to handle doc updates/creation?

  • We need to understand what is happening in this step