Skip to content

Latest commit

 

History

History
55 lines (37 loc) · 3.64 KB

README.md

File metadata and controls

55 lines (37 loc) · 3.64 KB

Microsoft Azure Container Networking

Build Status Go Report Card GitHub release

Azure Network Policy Manager Conformance
Cyclonus Network Policy Suite Cyclonus Network Policy Test
Kubernetes Network Policy E2E Build Status

Overview

This repository contains container networking services and plugins for Linux and Windows containers running on Azure:

The azure-vnet network plugins connect containers to your Azure VNET, to take advantage of Azure SDN capabilities. The azure-vnet-ipam IPAM plugins provide address management functionality for container IP addresses allocated from Azure VNET address space.

The following environments are supported:

Plugins are offered as part of Azure Kubernetes Service (AKS), as well as for individual Azure IaaS VMs. For Kubernetes clusters created by aks-engine, the deployment and configuration of both plugins on both Linux and Windows nodes is automatic and default.

The next generation of Azure CNI Plugin is powered by Cilium. Learn more at Azure CNI Powered By Cilium

Documentation

See Documentation for more information and examples.

Build

This repository builds on Windows and Linux. Build plugins directly from the source code for the latest version.

$ git clone https://github.com/Azure/azure-container-networking
$ cd azure-container-networking
$ make all-binaries

Then follow the instructions for the plugin in Documentation.

Contributions

Contributions in the form of bug reports, feature requests and PRs are always welcome.

Please follow these steps before submitting a PR:

  • Create an issue describing the bug or feature request.
  • Clone the repository and create a topic branch.
  • Make changes, adding new tests for new functionality.
  • Submit a PR.

License

See LICENSE.

Code of Conduct

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.