[NPM] L1Vh Endpoints Fix for NPM Lite #3067
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…in l1vh node
Reason for Change:
Currently when npm lite is enabled and running on an l1vh node, in the npm daemon set logs we see a log stating "ignoring pod update since there is no corresponding endpoints". The endpoints of the pods do exist in the HNS network itself; however, the logs are not able to find them.
Issue Fixed:
The state of the endpoints in HNS network in L1VH node is 2 which corresponds to state "hcnEndpointStateAttached". In the original windows NPM setup, the state of the endpoints in non-L1VH nodes is 3 which corresponds to state "hcnEndpointStateAttachedSharing". This pr adds a statement which checks if npm lite is enabled and running on L1VH node and if so, the endpoints are filter based on "hcnEndpointStateAttached" rather than "hcnEndpointStateAttachedSharing".
Requirements:
Notes: