azure-container-networking
azure-container-networking copied to clipboard
Azure Container Networking Solutions for Linux and Windows Containers
Added 2 API on CNS: 1. Check if Network Container from DNC exist in CNS. (If not existing, means refresh association is needed) 2. If the Network Container does not...
**What happened:** Cannot establish a TCP connection (port 2228) with the windows container's endpoint from another subnet (ping works). But the same communication can be established with a Linux container...
**Reason for Change**: Easier to get going with Azure NPM debug tooling **Issue Fixed**: **Requirements**: - [ ] uses [conventional commit messages](https://www.conventionalcommits.org/) - [ ] includes documentation - [ ]...
**What happened:** Connections to a loadbalancer service, which is routed to pods with networkpolicy restricting ingress traffic, sometimes fail with connection timeout. This happens only when the pods are deployed...
**Reason for Change**: If one of the job fails, then the other jobs are getting cancelled. `fail-fast: false` will let other jobs in an action run until completion. **Issue Fixed**:...
**Reason for Change**: Current state of e2e tests changes to dropgz/azure-ipam on every run regardless of whether or not change is present. Adding submodule pipeline that will only trigger runs...
**Reason for Change**: To enable AZR , dnc need to call CNS to get home az infos from NMAgent. This PR is for exposing the getHomeAzInfo api in cns to...
The NMAgent client used previously in CNS is older, and a duplication of the one added in `nmagent/`. In order to maintain one nmagent client and prevent duplication / wasted...
First version of 15415401, changes include: * CNI * CNS
Bumps [github.com/spf13/cobra](https://github.com/spf13/cobra) from 1.5.0 to 1.6.0. Release notes Sourced from github.com/spf13/cobra's releases. v1.6.0 Summer 2022 Release Some exciting changes make their way to Cobra! Command completions continue to get better...