build: added github registry

[siredmar]

What type of PR is this?

/kind enhancement

What this PR does / why we need it:

Adds support for pushing to github container registry to avoid docker hub rate limits.

Which issue(s) this PR fixes:

Fixes #1575

Special notes for your reviewer:

Does this PR introduce a user-facing change?

OCI images can now also be found on Github

other Note

[openyurt-bot]

@siredmar: GitHub didn't allow me to assign the following users: your_reviewer.

Note that only openyurtio members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

What type of PR is this?

/kind enhancement

What this PR does / why we need it:

Adds support for pushing to github container registry to avoid docker hub rate limits.

Which issue(s) this PR fixes:

Fixes #1575

Special notes for your reviewer:

Does this PR introduce a user-facing change?

OCI images can now also be found on Github

other Note

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.

[openyurt-bot]

Welcome @siredmar! It looks like this is your first PR to openyurtio/openyurt 🎉

[siredmar]

@rambohe-ch you need to provide two repository secrets called
GITHUB_REGISTRY_USERNAME and GITHUB_REGISTRY_USERNAME containing the username that pushes and a PAT (private access token) from github described in the following docs: https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-container-registry#authenticating-to-the-container-registry

[rambohe-ch]

@rambohe-ch you need to provide two repository secrets called GITHUB_REGISTRY_USERNAME and GITHUB_REGISTRY_USERNAME containing the username that pushes and a PAT (private access token) from github described in the following docs: https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-container-registry#authenticating-to-the-container-registry

@siredmar Very appreciate for your pull request. Because secrets are allowed start with GITHUB_, so i have created two secrets named as GH_REGISTRY_USERNAME and GH_REGISTRY_PASSWORD, please update your pull request with these two secrets.

[rambohe-ch]

@siredmar please fix the conflicting files. and the changes in this pull request should be merged into registry.yaml.

[siredmar]

@rambohe-ch done

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[codecov]

Codecov Report

Merging #1578 (915c0c5) into master (41647c4) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1578   +/-   ##
=======================================
  Coverage   51.43%   51.43%           
=======================================
  Files         134      134           
  Lines       15947    15947           
=======================================
  Hits         8202     8202           
  Misses       7000     7000           
  Partials      745      745           

Flag	Coverage Δ
unittests	51.43% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

[openyurt-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rambohe-ch, siredmar

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 [rambohe-ch]

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

[rambohe-ch]

/lgtm