e2e tests for multiple NodePool scenarios

[dontkillmyromance]

Test scenarios where customers run multiple NodePools simultaneously:
Multiple NodePools with different instance type requirements
Workloads that could be satisfied by multiple NodePools
Resource competition between NodePools
NodePool priority/selection behaviour

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[pfeifferj]

/unassign

[pfeifferj]

/remove-lifecycle stale