azure-container-networking
azure-container-networking copied to clipboard
Accept NNC with no NC as valid and consider pool monitor and reconciler started
Signed-off-by: Evan Baker [email protected]
Reason for Change: Due to superficial usage of the NC in the IPAM Pool Monitor, it was considered un-started until it received an NNC with an NC. This change fixes that and considers the reconciler and monitor started as soon as an NNC is ready, whether or not the NC is ready also.
Issue Fixed:
Requirements:
- [ ] uses conventional commit messages
- [ ] includes documentation
- [ ] adds unit tests
Notes: