From a078cb3323c58a9c29a316c8558723c1bb1fccef Mon Sep 17 00:00:00 2001 From: antrea-bot Date: Thu, 21 Nov 2024 05:59:00 +0000 Subject: [PATCH] Website update for main --- content/docs/main/docs/api-reference.html | 2 +- .../docs/maintainers/antrea-docker-image.md | 44 ------------------- 2 files changed, 1 insertion(+), 45 deletions(-) delete mode 100644 content/docs/main/docs/maintainers/antrea-docker-image.md diff --git a/content/docs/main/docs/api-reference.html b/content/docs/main/docs/api-reference.html index f77d2c4c..6d5159ed 100644 --- a/content/docs/main/docs/api-reference.html +++ b/content/docs/main/docs/api-reference.html @@ -12571,5 +12571,5 @@

BundleStatus

Generated with gen-crd-api-reference-docs -on git commit 9a45c58. +on git commit becd4ce.

diff --git a/content/docs/main/docs/maintainers/antrea-docker-image.md b/content/docs/main/docs/maintainers/antrea-docker-image.md deleted file mode 100644 index d6ceac65..00000000 --- a/content/docs/main/docs/maintainers/antrea-docker-image.md +++ /dev/null @@ -1,44 +0,0 @@ -# Antrea Docker image - -The main Antrea Docker images (`antrea/antrea-agent-ubuntu` and -`antrea/antrea-controller-ubuntu`) are multi-arch images. For example, the -`antrea/antrea-agent-ubuntu` manifest is a list of three manifests: -`antrea/antrea-agent-ubuntu-amd64`, `antrea/antrea-agent-ubuntu-arm64` and -`antrea/antrea-agent-ubuntu-arm`. Of these three manifests, only the first one -is built and uploaded to Dockerhub by Github workflows defined in the -`antrea-io/antrea` repositories. The other two are built and uploaded by Github -workflows defined in a private repository (`vmware-tanzu/antrea-build-infra`), -to which only the project maintainers have access. These workflows are triggered -every time the `main` branch of `antrea-io/antrea` is updated, as well as every -time a new Antrea Github release is created. They build the -`antrea/antrea-agent-ubuntu-arm64` and `antrea/antrea-agent-ubuntu-arm` Docker -images on native arm64 workers, then create the `antrea/antrea-agent-ubuntu` -multi-arch manifest and push it to Dockerhub. The same goes for the controller -images. They are also in charge of testing the images in a -[K3s](https://github.com/k3s-io/k3s) cluster. - -## Why do we use a private repository? - -The `vmware-tanzu/antrea-build-infra` repository uses self-hosted ARM64 workers -provided by the [Open Source Lab](https://osuosl.org/services/aarch64/) at -Oregon State University. These workers enable us to build, and more importantly -*test*, the Antrea Docker images for the arm64 and arm/v7 architectures. Being -able to build Docker images on native ARM platforms is convenient as it is much -faster than emulation. But if we just wanted to build the images, emulation -would probably be good enough. However, testing Kubernetes ARM support using -emulation is no piece of cake. Which is why we prefer to use native ARM64 -workers. - -Github strongly -[recommends](https://docs.github.com/en/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories) -not to use self-hosted runners with public repositories, for security -reasons. It would be too easy for a malicious person to run arbitrary code on -the runners by opening a pull request. Were we to make this repository public, -we would therefore at least need to disable pull requests, which is sub-optimal -for a public repository. We believe Github will address the issue eventually and -provide safeguards to enable using self-hosted runners with public -repositories, at which point we will migrate workflows from this repository to -the main Antrea repository. - -In the future, we may switch over to ARM hosted Github runners provided by the -CNCF.