[feature] move manifest image references to ghcr

[mahdikhashan]

What this PR does / why we need it:

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
part of #2520

Checklist:

• Docs included if any changes are user facing

[juliusvonkohout]

/retest

[Electronic-Waste]

@mahdikhashan Thanks for creating this. Maybe we should first update the build-and-publish CI and then update the image in manifests:)

[mahdikhashan]

@mahdikhashan Thanks for creating this. Maybe we should first update the build-and-publish CI and then update the image in manifests:)

yes, you are right, we have the pr here: #2520

[saileshd1402]

Should we update the images for the examples yamls as well?

[andreyvelich]

Yes, @mahdikhashan @saileshd1402 please help us to update all examples and references where we use DockerHub to GHCR.

[mahdikhashan]

yes, i'll do so, i may be slow to respond today and tomorrow. thanks

[andreyvelich]

@mahdikhashan Did you get a chance to update it since we would like to release Katib tomorrow morning

[review-notebook-app]

Check out this pull request on 

See visual diffs & provide feedback on Jupyter Notebooks.

---

Powered by ReviewNB

[mahdikhashan]

@mahdikhashan Did you get a chance to update it since we would like to release Katib tomorrow morning

sry for the delay, please take a look, it should be ready now. thanks for your time

[mahdikhashan]

cc: @saileshd1402 please take a look when you have time
@kubeflow/wg-automl-leads

[saileshd1402]

Thanks for this!, minor fixes migth be required:

• https://github.com/mahdikhashan/katib/blob/7e70e89019c532964d97e2695b9e3ec75b6ba771/manifests/v1beta1/installs/katib-standalone-postgres/kustomization.yaml#L24
• https://github.com/mahdikhashan/katib/blob/7e70e89019c532964d97e2695b9e3ec75b6ba771/examples/v1beta1/metrics-collector/custom-metrics-collector.yaml#L29

[mahdikhashan]

Thanks for this!, minor fixes migth be required:

• https://github.com/mahdikhashan/katib/blob/7e70e89019c532964d97e2695b9e3ec75b6ba771/manifests/v1beta1/installs/katib-standalone-postgres/kustomization.yaml#L24
• https://github.com/mahdikhashan/katib/blob/7e70e89019c532964d97e2695b9e3ec75b6ba771/examples/v1beta1/metrics-collector/custom-metrics-collector.yaml#L29

should be fixed now. thank for your attention.

[andreyvelich]

Thank you for this @mahdikhashan!
/lgtm
/approve

[google-oss-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andreyvelich

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [andreyvelich]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[andreyvelich]

/cherry-pick release-0.18

[google-oss-robot]

@andreyvelich: #2529 failed to apply on top of branch "release-0.18":

Applying: move to ghcr
Using index info to reconstruct a base tree...
M	manifests/v1beta1/components/controller/trial-templates.yaml
Falling back to patching base and 3-way merge...
Auto-merging manifests/v1beta1/components/controller/trial-templates.yaml
CONFLICT (content): Merge conflict in manifests/v1beta1/components/controller/trial-templates.yaml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 move to ghcr
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-0.18

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[andreyvelich]

@mahdikhashan @saileshd1402 Please can someone help to cherry-pick this PR to the release-0.18 branch ?