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

[chore] Use tagged images in e2e tests to not trigger docker.com rate limit #1499

Merged
merged 1 commit into from
Feb 23, 2023

Conversation

andreasgerstmayr
Copy link
Contributor

Kubernetes uses imagePullPolicy: Always for images with latest or no tag, which can trigger docker.com rate limits if one runs the e2e tests too often.

Kubernetes uses imagePullPolicy: Always for images with latest or no
tag, which can trigger docker.com rate limits if one runs the e2e tests
too often.

Signed-off-by: Andreas Gerstmayr <agerstmayr@redhat.com>
@andreasgerstmayr andreasgerstmayr requested a review from a team February 22, 2023 15:44
@@ -18,6 +18,6 @@ spec:
spec:
containers:
- name: myapp
image: docker.io/avadhutp123/aspnetapp:latest # source code of the application: https://github.com/dotnet/dotnet-docker/tree/main/samples/aspnetapp
image: docker.io/avadhutp123/aspnetapp@sha256:d2e8d3415f6f12efae0369aa0a9777a58583841fb133f33e10a73adb9fb392da # source code of the application: https://github.com/dotnet/dotnet-docker/tree/main/samples/aspnetapp
Copy link
Contributor

Choose a reason for hiding this comment

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

@pavolloffay do you know why we're not using the dotnet images from microsoft? i.e. mcr.microsoft.com/dotnet/samples:aspnetapp?

Copy link
Contributor

Choose a reason for hiding this comment

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

@jaronoff97 The reason is described in #1151

@andreasgerstmayr andreasgerstmayr changed the title Use tagged images in e2e tests to not trigger docker.com rate limit [chore] Use tagged images in e2e tests to not trigger docker.com rate limit Feb 22, 2023
@@ -18,6 +18,6 @@ spec:
spec:
containers:
- name: myapp
image: docker.io/avadhutp123/aspnetapp:latest # source code of the application: https://github.com/dotnet/dotnet-docker/tree/main/samples/aspnetapp
image: docker.io/avadhutp123/aspnetapp@sha256:d2e8d3415f6f12efae0369aa0a9777a58583841fb133f33e10a73adb9fb392da # source code of the application: https://github.com/dotnet/dotnet-docker/tree/main/samples/aspnetapp
Copy link
Contributor

Choose a reason for hiding this comment

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

@jaronoff97 The reason is described in #1151

@@ -20,4 +20,4 @@ spec:
- name: myapp
image: ghcr.io/anuraaga/flask-hello-world:latest
Copy link
Contributor

Choose a reason for hiding this comment

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

I know the problem is related to the Docker Hub images but... should we apply the same philosophy to all the images?

@pavolloffay pavolloffay added the Skip Changelog PRs that do not require a CHANGELOG.md entry label Feb 23, 2023
@pavolloffay pavolloffay merged commit 0067c35 into open-telemetry:main Feb 23, 2023
ItielOlenick pushed a commit to ItielOlenick/opentelemetry-operator that referenced this pull request May 1, 2024
…pen-telemetry#1499)

Kubernetes uses imagePullPolicy: Always for images with latest or no
tag, which can trigger docker.com rate limits if one runs the e2e tests
too often.

Signed-off-by: Andreas Gerstmayr <agerstmayr@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Skip Changelog PRs that do not require a CHANGELOG.md entry
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants