azure-container-networking
azure-container-networking copied to clipboard
[NPM] L1Vh Endpoints Fix for NPM Lite
β¦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:
- [ ] uses conventional commit messages
- [ ] includes documentation
- [ ] adds unit tests
- [ ] relevant PR labels added
Notes: