-
Notifications
You must be signed in to change notification settings - Fork 431
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
Accelerated networking test should handle VMSS instances #1015
Comments
/help |
@CecileRobertMichon: Please ensure the request meets the requirements listed here. If this request no longer meets these requirements, the label can be removed In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@mboersma @CecileRobertMichon |
@surajrana93 go for it. I saw you also commented on #497. Both of these are up for grabs. Make sure you comment |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
/remove-lifecycle stale |
/assign |
/kind bug
What steps did you take and what happened:
The test spec in test/e2e/azure_accelnet.go only loops over VMs in the resource group, so it's not testing the accelerated networking property of any VMSS / MachinePool clusters. It should be expanded and added to cover the VMSS spec that's now in azure_test.go.
What did you expect to happen:
e2e tests validate the accelerated networking property on VMSS instances is set as expected (
true
if it's available for the SKU).Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:
kubectl version
):/etc/os-release
):The text was updated successfully, but these errors were encountered: