We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
What would you like to be added:
Currently we only have a sanity e2e tests for TAS using a single node. Also, we should use JobSet & Job, as JobSet let's us have multiple pods.
For the started I think we can have 4 nodes: 2 blocks divided into 2 racks each, two nodes per rack.
I think we can have another job on test-infra for that, analogous as we do for multikueue.
Why is this needed:
With the current sanity tests we cannot test more complex scenarios. This is particularly important as users start report issues: #3211 (comment)
This is a follow up discussed under: #3284 and captured in the spreadsheet
The text was updated successfully, but these errors were encountered:
/assign @mszadkow tentatively /cc @mbobrovskyi @tenzen-y
Sorry, something went wrong.
I assume all of the nodes are part of 1 cluster. There other options to consider, but I don't think it's the matter of this issue.
Yes, one cluster
mszadkow
Successfully merging a pull request may close this issue.
What would you like to be added:
Currently we only have a sanity e2e tests for TAS using a single node.
Also, we should use JobSet & Job, as JobSet let's us have multiple pods.
For the started I think we can have 4 nodes: 2 blocks divided into 2 racks each, two nodes per rack.
I think we can have another job on test-infra for that, analogous as we do for multikueue.
Why is this needed:
With the current sanity tests we cannot test more complex scenarios.
This is particularly important as users start report issues: #3211 (comment)
This is a follow up discussed under: #3284
and captured in the spreadsheet
The text was updated successfully, but these errors were encountered: