Releases: Azure/azure-container-networking
Releases · Azure/azure-container-networking
v1.0.14
This release contains:
- Fix Endpoint policy regression (#268)
v1.0.13
This release contains:
- Removes HNSNetwork's DNS suffix in Windows. (#254)
- LIFO order for network policies (#258)
- PortMapping support in Azure CNI for Windows (#256)
- Replacing go log with cns log. (#262)
- Implement CNI update for Azure CNI (#265)
- Multi-tenancy support for windows (#259)
- Adding badges to readme (#255)
azure vnet v1.0.12
This release contains following:
- Fix for timed out on locking store, err:Store is locked in windows #242
- Fix for pod cannot connect to itself via service IP #248
- Scripts for installing multi tenancy plugin
azure vnet v1.0.12-rc3
This version blocks APIPA address space reachability from within containers.
azure vnet v1.0.12-rc2
This release contains
- Added support for infravnet connectivity in multitenancy CNI
- Added PrivateIP block support for packets passing through SNAT bridge in multitenancy CNI
- Telemetry report change for DNC
- Enabling CircleCI
azure vnet v1.0.12-rc1
This release changes the way interface names are generated for containers. This release uses the network name, container id, and ifname (#229)
azure vnet v1.0.11
This release contains
- Fix for unparseable error returned by CNI (#195)
- Fix for IP Address leak in HNS failure scenario in windows CNI (#218)
- Added clear container and service fabric orchestrator type in CNS
- Vendored few dependency packages (#124)
azure-vnet v1.0.10
This release contains following changes
- Separated Endpoint creation logic to linux and windows and fixed EndpointId creation in Linux if netns is empty
azure-vnet v1.0.8
This release adds the functionality to connect containers running in a single Azure VM to multiple Azure Virtual Networks. Only Linux VMs are supported. Windows release is coming soon.
azure-vnet v1.0.7
This release contains the following changes
- Locking loggers in case of multi-threaded apps. (#171)
- CNI Plugin nil ref in case of failure (#177 )
- Workaround for windows - delay after network creation, support vswitch creation at vm boot time
- Fixed initializing store in ipam (#188)