-
Notifications
You must be signed in to change notification settings - Fork 376
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use the docker.io registry for "latest" antrea images #4235
Use the docker.io registry for "latest" antrea images #4235
Conversation
Codecov Report
@@ Coverage Diff @@
## main #4235 +/- ##
==========================================
- Coverage 64.29% 63.00% -1.29%
==========================================
Files 361 396 +35
Lines 52203 54859 +2656
==========================================
+ Hits 33563 34564 +1001
- Misses 16186 17792 +1606
- Partials 2454 2503 +49
|
d512969
to
1ee04b0
Compare
/test-all |
@@ -316,7 +316,7 @@ function deliver_antrea_windows { | |||
fi | |||
|
|||
cp -f build/yamls/*.yml $WORKDIR | |||
docker save -o antrea-ubuntu.tar projects.registry.vmware.com/antrea/antrea-ubuntu:latest | |||
docker save -o antrea-ubuntu.tar antrea/antrea-ubuntu:latest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The default registry is DOCKER_REGISTRY=$(head -n1 "${WORKSPACE}/ci/docker-registry")
, there are quite a few scripts are using this default registry to build images. I feel you may need to double check it.
Another usage I see is DOCKER_REGISTRY="projects.registry.vmware.com"
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could you clarify your concern? Tagged images, and in particular images used for testing (e.g., nginx) or tagged base images (e.g. antrea/openvswitch) should still be pulled from projects.registry.vmware.com
. The Jenkins test scripts build the antrea image (antrea/antrea-ubuntu:latest
) as part of the test (image is not pulled) and there is no reason to tag it with the registry (projects.registry.vmware.com/antrea/antrea-ubuntu:latest
) any more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I mean there are some images' prefix is ${DOCKER_REGISTRY}
instead of projects.registry.vmware.com
directly. E.g: https://github.com/antrea-io/antrea/blob/main/ci/jenkins/test-mc.sh#L268-L273.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. As far as I can tell, only test-mc.sh needs to be updated.
/test-multicluster-e2e |
It has been observed that pulling projects.registry.vmware.com/antrea/antrea-ubuntu:latest will often fail. This is because the Harbor registry uses a CDN for caching, which doesn't work well at all when tags are being re-used (in our case, we re-use the latest tag all the time). While most users should be installing a released version of antrea (with an immutable tag) and thus should not suffer from this issue, it can be frustrating for users who want to install the latest antrea built from the main branch. As a result, we switch to the docker.io registry whenever the latest tag is used, and in particular for checked-in manifest files. The Harbor registry (projects.registry.vmware.com) is still used for all release assets, and more generally for all images with an immutable tag. We are able to simplify some infrastructure code because of that, as built images no longer need to be tagged with projects.registry.vmware.com. Signed-off-by: Antonin Bas <[email protected]>
Signed-off-by: Antonin Bas <[email protected]>
1ee04b0
to
be38393
Compare
/test-all |
/test-all |
/test-all |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@XinShuYang the tests are still not running, I'll try again |
/test-all |
/test-windows-all |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/test-e2e |
@luolanzone any further comment? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks.
It has been observed that pulling projects.registry.vmware.com/antrea/antrea-ubuntu:latest will often fail. This is because the Harbor registry uses a CDN for caching, which doesn't work well at all when tags are being re-used (in our case, we re-use the latest tag all the time). While most users should be installing a released version of antrea (with an immutable tag) and thus should not suffer from this issue, it can be frustrating for users who want to install the latest antrea built from the main branch. As a result, we switch to the docker.io registry whenever the latest tag is used, and in particular for checked-in manifest files. The Harbor registry (projects.registry.vmware.com) is still used for all release assets, and more generally for all images with an immutable tag. We are able to simplify some infrastructure code because of that, as built images no longer need to be tagged with projects.registry.vmware.com. Signed-off-by: Antonin Bas <[email protected]>
It has been observed that pulling
projects.registry.vmware.com/antrea/antrea-ubuntu:latest will often fail. This is because the Harbor registry uses a CDN for caching, which doesn't work well at all when tags are being re-used (in our case, we re-use the latest tag all the time). While most users should be installing a released version of antrea (with an immutable tag) and thus should not suffer from this issue, it can be frustrating for users who want to install the latest antrea built from the main branch.
As a result, we switch to the docker.io registry whenever the latest tag is used, and in particular for checked-in manifest files. The Harbor registry (projects.registry.vmware.com) is still used for all release assets, and more generally for all images with an immutable tag.
We are able to simplify some infrastructure code because of that, as built images no longer need to be tagged with
projects.registry.vmware.com.