Граф коммитов

7 Коммитов

Автор SHA1 Сообщение Дата
tamilmani1989 6ac5e8c9f0
CNI Ipv6 Dualstack Support (#538)
* added cniv6 plugin

* cni ipv6 base framework

* removed unwanted changes

* added ipv6 change

* added cni ipv6 changes

* drop neighbor discovery messages to other VMs

* fixed issues

* fixed unit tests

* fix nil dereference

* addressed comments

* ipv6 fixes and changes

* addressed comments
2020-04-15 22:30:48 -07:00
Paul Johnston a01afb7a93
Added EB rule for ip addresses in conflist for linux (#505)
* Added EB rule for ip addresses in conflist for linux

* Made methods more generic and removed line from endpoint struct

* Adding log statement

* Fixed syntax error

* Made review2 changes

* Made review3 changes

* Made method lowercase
2020-02-21 14:35:37 -08:00
tamilmani1989 edabc6dd39
Added Host NC communication support in Linux (#374)
* allow inbound connection to container from host if the feature is enabled

* Allowinbound from host to NC if flag is enabled

* fixed old changes

* minor fixes

* added NC to host commn support

* added NCToHostCommunication field in cns contract

* addressed review comments

* addressed review comments

* addressed review comments

* address comments

* fixed space damage
2019-07-16 17:09:34 -07:00
tamilmani1989 a1b4da1b90 Adding/Remove static arp entry for pod IP in VM (#273)
* add static arp entry in vm (for bridge mode and singletenancy) whenever pod created and remove when its deleted
2018-12-11 11:18:11 -08:00
tamilmani1989 1b821feb3d Fix for Pod Connecting to itself via ServiceIP (#248)
* Enable hairpin for veth interface connecting to container interface. This fixes pod connecting to itself via service IP
2018-10-02 22:07:09 -07:00
tamilmani1989 9a9c2cd8d4 Added support for InfraVnet connectivity in multitenancy CNI (#234)
* Added infravnet connectivity support for multitenancy CNI
2018-08-18 14:50:49 -07:00
tamilmani1989 147c4388c8 Multitenancy Support for Linux (#156)
This PR adds the following capabilities
1. Support to create and connect containers to different Azure Vnets. Every VlanId corresponds to a different Azure Vnet.
2. SNAT support for containers to reach Internet using the container's host IP as the SNAT address.

Both the above options are controlled by the config parameters in Azure CNI.
2018-07-06 11:45:47 -07:00