azure-container-networking validate nnc in swift e2e scale/connectivity test

Signed-off-by: Evan Baker [email protected]

Reason for Change:

Adds a validation of the NNC (requested IPs) during the swift e2e. This includes functionality to support testing in subnet scarcity mode, but it is hardcoded to false until the clustersubnetstates are being written by RC.

Issue Fixed:

Requirements:

[ ] uses conventional commit messages
[ ] includes documentation
[ ] adds unit tests

Notes:

Sep 21 '22 20:09 rbtr

@nairashu

This includes functionality to support testing in subnet scarcity mode, but it is hardcoded to false until the clustersubnetstates are being written by RC.

Once the exhausted state is being written by CRD, that will be passed in to the NNC validation instead of false. Then, we update the test to build this cluster with a smaller subnet/scale the pods up past the exhaustion limit, and it becomes an e2e for CNS scarcity behavior. FWIW I manually validated that the NNC validation is correct with the exhausted bool set to true, so this is ready for those changes as soon as they land.

Sep 22 '22 16:09 rbtr