Bug 1990953

Created attachment 1811577 [details]
Pod Menifest

Description of problem:
In a multi-container pod launched with SRIOV networks in the annotation, the first container gets the VF allocated to it, even though the VF resources are not allocated in its specifications.
The second container, which has the VF resources allocation in its specification, gets another set of SRIOV VFs allocated to it, but they are unusable(network unreachable)

Expectation:-
Only the container which has been allocated with the SRIOV resources from container specifications, should be given the VF device. and the corresponding VF device should be able to reach its network.

Version-Release number of selected component (if applicable):


For example if we have 3 container in a pod (A.B.C)



How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
In the problematic scenario -
   * Why is the first container(A) getting the VFs allocated to it even though no SRIOV resource was defined with it in its manifest.
* Why is the Third container(C), which is getting allocated with the container is not usable(not getting any traffic) ?


Expected results:
Only the container which have correct SRIOV configuration, Should attach with the VF .


Additional info:
https://gss--c.visualforce.com/apex/Case_View?id=5002K00000xBXiy&sfdc.override=1

Customer need to have this in detail functionality, Why SRIOV behaving in unexpected way.

Customer is desperately looking for an RCA.