Skip to content
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

Stop using projects.registry.vmware.com for user-facing images #6073

Conversation

antoninbas
Copy link
Contributor

We stop referencing the VMware Harbor registry
(projects.registry.vmware.com) in the Helm charts and K8s manifests that we release to users, with the expectation that images for future releases will not be available from that registry, as it is scheduled to be EOL'd and we won't be mirroring them there.

Because the antrea DockerHub organization is part of the "Sponsored OSS" program, there should be no concern about users running into issues because of DockerHub rate-limits. We could also consider mirroring these images to ghcr.io in the future, to offer users an alternative.

At the moment, we do not update references to other images in the projects.registry.vmware.com/antrea project (images used for testing), with the expectation that they will remain available for the foreseeable future. In other words, while we will no longer be publishing new images to projects.registry.vmware.com, we expect that existing images will remain available through the same URLs.

For #6003

@antoninbas antoninbas added area/build-release Issues or PRs related to building and releasing action/backport Indicates a PR that requires backports. action/release-note Indicates a PR that should be included in release notes. labels Mar 6, 2024
@antoninbas antoninbas requested review from tnqn and luolanzone March 6, 2024 19:31
We stop referencing the VMware Harbor registry
(projects.registry.vmware.com) in the Helm charts and K8s manifests that
we release to users, with the expectation that images for future
releases will not be available from that registry, as it is scheduled to
be EOL'd and we won't be mirroring them there.

Because the antrea DockerHub organization is part of the "Sponsored OSS"
program, there should be no concern about users running into issues
because of DockerHub rate-limits. We could also consider mirroring these
images to ghcr.io in the future, to offer users an alternative.

At the moment, we do not update references to other images in the
projects.registry.vmware.com/antrea project (images used for testing),
with the expectation that they will remain available for the foreseeable
future. In other words, while we will no longer be publishing new images
to projects.registry.vmware.com, we expect that existing images will
remain available through the same URLs.

For antrea-io#6003

Signed-off-by: Antonin Bas <antonin.bas@broadcom.com>
@antoninbas antoninbas force-pushed the stop-using-projects.registry.vmware.com-for-user-facing-images branch from f9740b3 to e8aabf3 Compare March 7, 2024 00:19
@@ -152,10 +152,10 @@ function version_lt() { test "$(printf '%s\n' "$@" | sort -rV | head -n 1)" != "

DOCKER_IMAGES=()
if version_lt "$FROM_TAG" v1.15; then
DOCKER_IMAGES+=("projects.registry.vmware.com/antrea/antrea-ubuntu:$FROM_TAG")
DOCKER_IMAGES+=("antrea/antrea-ubuntu:$FROM_TAG")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we keep this as before considering it's only for testing? I am thinking the test may fail more frequently due to Docker rate limit.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Another question is should we release a new patch release after the backport? cc @tnqn

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't have rate-limit as explained in the PR description.
Yes, we should release new patch releases, there has been some bugfixes accumulated.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not getting that why we change the images from Dockerhub to Harbor registry at the first place? I recalled it was because of rate limits? Or Antrea wasn't a part of the "Sponsored OSS" programs when the registry is changed?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right

Copy link
Member

@tnqn tnqn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@@ -152,10 +152,10 @@ function version_lt() { test "$(printf '%s\n' "$@" | sort -rV | head -n 1)" != "

DOCKER_IMAGES=()
if version_lt "$FROM_TAG" v1.15; then
DOCKER_IMAGES+=("projects.registry.vmware.com/antrea/antrea-ubuntu:$FROM_TAG")
DOCKER_IMAGES+=("antrea/antrea-ubuntu:$FROM_TAG")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't have rate-limit as explained in the PR description.
Yes, we should release new patch releases, there has been some bugfixes accumulated.

@tnqn

This comment was marked as off-topic.

@antoninbas

This comment was marked as off-topic.

@tnqn

This comment was marked as off-topic.

@antoninbas
Copy link
Contributor Author

/test-all

@antoninbas antoninbas merged commit e16e6b6 into antrea-io:main Mar 7, 2024
51 of 55 checks passed
@antoninbas antoninbas deleted the stop-using-projects.registry.vmware.com-for-user-facing-images branch March 7, 2024 21:50
antoninbas added a commit to antoninbas/antrea that referenced this pull request Mar 7, 2024
…a-io#6073)

We stop referencing the VMware Harbor registry
(projects.registry.vmware.com) in the Helm charts and K8s manifests that
we release to users, with the expectation that images for future
releases will not be available from that registry, as it is scheduled to
be EOL'd and we won't be mirroring them there.

Because the antrea DockerHub organization is part of the "Sponsored OSS"
program, there should be no concern about users running into issues
because of DockerHub rate-limits. We could also consider mirroring these
images to ghcr.io in the future, to offer users an alternative.

At the moment, we do not update references to other images in the
projects.registry.vmware.com/antrea project (images used for testing),
with the expectation that they will remain available for the foreseeable
future. In other words, while we will no longer be publishing new images
to projects.registry.vmware.com, we expect that existing images will
remain available through the same URLs.

For antrea-io#6003

Signed-off-by: Antonin Bas <antonin.bas@broadcom.com>
antoninbas added a commit to antoninbas/antrea that referenced this pull request Mar 7, 2024
…a-io#6073)

We stop referencing the VMware Harbor registry
(projects.registry.vmware.com) in the Helm charts and K8s manifests that
we release to users, with the expectation that images for future
releases will not be available from that registry, as it is scheduled to
be EOL'd and we won't be mirroring them there.

Because the antrea DockerHub organization is part of the "Sponsored OSS"
program, there should be no concern about users running into issues
because of DockerHub rate-limits. We could also consider mirroring these
images to ghcr.io in the future, to offer users an alternative.

At the moment, we do not update references to other images in the
projects.registry.vmware.com/antrea project (images used for testing),
with the expectation that they will remain available for the foreseeable
future. In other words, while we will no longer be publishing new images
to projects.registry.vmware.com, we expect that existing images will
remain available through the same URLs.

For antrea-io#6003

Signed-off-by: Antonin Bas <antonin.bas@broadcom.com>
antoninbas added a commit to antoninbas/antrea that referenced this pull request Mar 7, 2024
…a-io#6073)

We stop referencing the VMware Harbor registry
(projects.registry.vmware.com) in the Helm charts and K8s manifests that
we release to users, with the expectation that images for future
releases will not be available from that registry, as it is scheduled to
be EOL'd and we won't be mirroring them there.

Because the antrea DockerHub organization is part of the "Sponsored OSS"
program, there should be no concern about users running into issues
because of DockerHub rate-limits. We could also consider mirroring these
images to ghcr.io in the future, to offer users an alternative.

At the moment, we do not update references to other images in the
projects.registry.vmware.com/antrea project (images used for testing),
with the expectation that they will remain available for the foreseeable
future. In other words, while we will no longer be publishing new images
to projects.registry.vmware.com, we expect that existing images will
remain available through the same URLs.

For antrea-io#6003

Signed-off-by: Antonin Bas <antonin.bas@broadcom.com>
antoninbas added a commit that referenced this pull request Mar 8, 2024
#6082)

We stop referencing the VMware Harbor registry
(projects.registry.vmware.com) in the Helm charts and K8s manifests that
we release to users, with the expectation that images for future
releases will not be available from that registry, as it is scheduled to
be EOL'd and we won't be mirroring them there.

Because the antrea DockerHub organization is part of the "Sponsored OSS"
program, there should be no concern about users running into issues
because of DockerHub rate-limits. We could also consider mirroring these
images to ghcr.io in the future, to offer users an alternative.

At the moment, we do not update references to other images in the
projects.registry.vmware.com/antrea project (images used for testing),
with the expectation that they will remain available for the foreseeable
future. In other words, while we will no longer be publishing new images
to projects.registry.vmware.com, we expect that existing images will
remain available through the same URLs.

For #6003

Signed-off-by: Antonin Bas <antonin.bas@broadcom.com>
tnqn pushed a commit that referenced this pull request Mar 11, 2024
#6083)

We stop referencing the VMware Harbor registry
(projects.registry.vmware.com) in the Helm charts and K8s manifests that
we release to users, with the expectation that images for future
releases will not be available from that registry, as it is scheduled to
be EOL'd and we won't be mirroring them there.

Because the antrea DockerHub organization is part of the "Sponsored OSS"
program, there should be no concern about users running into issues
because of DockerHub rate-limits. We could also consider mirroring these
images to ghcr.io in the future, to offer users an alternative.

At the moment, we do not update references to other images in the
projects.registry.vmware.com/antrea project (images used for testing),
with the expectation that they will remain available for the foreseeable
future. In other words, while we will no longer be publishing new images
to projects.registry.vmware.com, we expect that existing images will
remain available through the same URLs.

For #6003

Signed-off-by: Antonin Bas <antonin.bas@broadcom.com>
tnqn pushed a commit that referenced this pull request Mar 11, 2024
#6084)

We stop referencing the VMware Harbor registry
(projects.registry.vmware.com) in the Helm charts and K8s manifests that
we release to users, with the expectation that images for future
releases will not be available from that registry, as it is scheduled to
be EOL'd and we won't be mirroring them there.

Because the antrea DockerHub organization is part of the "Sponsored OSS"
program, there should be no concern about users running into issues
because of DockerHub rate-limits. We could also consider mirroring these
images to ghcr.io in the future, to offer users an alternative.

At the moment, we do not update references to other images in the
projects.registry.vmware.com/antrea project (images used for testing),
with the expectation that they will remain available for the foreseeable
future. In other words, while we will no longer be publishing new images
to projects.registry.vmware.com, we expect that existing images will
remain available through the same URLs.

For #6003

Signed-off-by: Antonin Bas <antonin.bas@broadcom.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
action/backport Indicates a PR that requires backports. action/release-note Indicates a PR that should be included in release notes. area/build-release Issues or PRs related to building and releasing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants