Releases: Azure/azure-container-networking
Releases · Azure/azure-container-networking
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
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
azure-vnet v1.0.6
azure-vnet v1.0.5
The release contains the following changes
- Generate vethname based on supplied key. In CNI, the key will be "podname.podnamespace"
- Changed prefix from azveth to azv
azure-vnet v1.0.4
This release contains the following changes:
- Support DNS configuration in Windows CNI.
- Support HNS policy configuration in Windows CNI.
azure-vnet v1.0.3
This release does the following
- Handle reboot scenario in CNM and CNS. It will recreate the network that existed before reboot
- Separated state store location for CNI and CNM
- Fixed reservation id issue
- Removed reservation id as default from CNI
- Added azure-cns as part of azure-container-networking build
azure-vnet v1.0.2
This release fixes cni config for windows platform.