Setting up CICD for edge release repo

[pdgetrf]

• [x] Pick a name (Fornax?)
• [x] Pick a KubeEdge base version (preferably newest release)
• [x] Create the release repo (Peng)
• [x] Baseline tests (tests that come from KubeEdge should pass CI)

[pdgetrf]

@chenqianfzh for item 3, can we reused the existing fornax repo? I checked that we all have admin access.

[chenqianfzh]

I updated the main branch in our fornax repo (https://github.com/CentaurusInfra/fornax) so that the CI/CD are running. A successful CI running is seen in https://github.com/CentaurusInfra/fornax/pull/19.

This repo is ready to take in more code changes from us now.

The main branch is aligned with the latest master branch in official kubeedge repo. I did not align with the recent release branches/tags as none of them gives a successful e2e test ( I tried 1.7.1, 1.7.0 and 1.6.0). I might rebase our repo to 1.8.0 if necessary.

BTW, the PoC code change is saved in branch https://github.com/CentaurusInfra/fornax/tree/backup-main.

[pdgetrf]

I updated the main branch in our fornax repo (https://github.com/CentaurusInfra/fornax) so that the CI/CD are running. A successful CI running is seen in CentaurusInfra/fornax#19.

This repo is ready to take in more code changes from us now.

The main branch is aligned with the latest master branch in official kubeedge repo. I did not align with the recent release branches/tags as none of them gives a successful e2e test ( I tried 1.7.1, 1.7.0 and 1.6.0). I might rebase our repo to 1.8.0 if necessary.

BTW, the PoC code change is saved in branch https://github.com/CentaurusInfra/fornax/tree/backup-main.

Great work! Feel free to close the issue. Thanks!