-
Notifications
You must be signed in to change notification settings - Fork 8.5k
[CI] Add preferCached for docker-startup commands
#244766
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
base: main
Are you sure you want to change the base?
[CI] Add preferCached for docker-startup commands
#244766
Conversation
|
Pinging @elastic/kibana-operations (Team:Operations) |
|
Pinging @elastic/fleet (Team:Fleet) |
|
Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services) |
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
|
Pinging @elastic/obs-presentation-team (Team:obs-presentation) |
|
/ci |
💚 Build Succeeded
Metrics [docs]Public APIs missing comments
History
|
Summary
Add
preferCachedas an option in the test util for starting docker images, turn it on for all EPR image pulls, in order to prevent costly docker pulls in FTRs/integration tests.After #244517 we still have a small temporal zone in between an agent being provisioned and the tests being ran, where a promotion would trigger a docker pull, that depletes disk space, it also would make pulls slow, and potentially time out tests.
This PR suggests, we should always use the cached variant (for EPR at least). With this, the above risk zone is no longer causing pulls, it's just that we are still testing the previously promoted and cached image, probably not risky.