[DO NOT REVIEW] Target dedicated dind nodes for dev-engine tests #7317
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Matias Pan <matias@dagger.io>
Signed-off-by: Matias Pan <matias@dagger.io>
matipan
force-pushed
the
test-dedicated-dind
branch
from
28dd808
to
eb2365d
Compare
|
Closing this pull request since at the moment we will not be migrating dind runners to the approach being tested here. More details can be found in https://github.com/dagger/dagger.io/pull/3702 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Warning
The goal of the PR is to easily test a new setup were nodes requiring dind run on separate infra. It should be reviewed nor merged