search

microsoft / service-fabric

Service Fabric is a distributed systems platform for packaging, deploying, and managing stateless and stateful distributed applications and containers at large scale.
https://docs.microsoft.com/en-us/azure/service-fabric/
MIT License
3.03k stars 399 forks source link

Please implement Container Networking Interface (CNI) #850

Open AceHack opened 6 years ago

AceHack commented 6 years ago

Most container orchestrators have started using CNI, please follow suit. https://github.com/containernetworking/cni

Calico would be a great provider of CNI to use as a first class plugin https://www.projectcalico.org/

RajeetN commented 6 years ago

Yes this is in the works. Is this an on premise (standalone) deployment you need this for?

AceHack commented 6 years ago

Why is this closed if it's in the works? Is there some way to track it, should this be labeled roadmap? I don't understand why this was closed. It's for both, some deployments are on-premise and some are in Azure.

RajeetN commented 6 years ago

Could you elaborate on the scenario where you need it to be CNI on Azure?

AceHack commented 6 years ago

Yes, looking to allow for automation of infrastructure as native part of app development, using native app development tools to express repeatable, re-deployable, networking topologies. Auto setting up LB rules, multiple different ingresses with different routing rules, powerful label based network policy, cryptographic node, container, service, network namespace based identity, service mesh, automatic fast kernel level iptables like routing of services with consistent immutable IPs, automatic correlated tracing of communications, network namespaces that can be shared by multiple containers i.e. pods, immutable infrastructure, software-defined networking (SDN), software load balancers inside the cluster that don't need any Azure or external load balancers, consistency between on-premises and Azure environment, software-defined security, cheap, external resource discovery, egress, host protection, ability to use standard tools like wireshare for debugging container network traffic, the list goes on and on.

AceHack commented 6 years ago

Also, I would just like to say I don't care if in Auze there is an azure specific CNI plugin used and on-premises I use a calico based CNI plugin, I just want to have a consistent application development, deployment, and management experience no matter where I run my portable application. The Azure-based CNI plugin should not overuse cloud infrastructure and make it more expensive than needed, wherever an in cluster solution makes sense it should be used instead, like in cluster load balancing. Basically, I want Layer 2-7 SDN built-in Service Fabric that only calls out to external out of cluster devices where absolutely necessary but all of that should be automated through a consistent development experience.

AceHack commented 6 years ago

Oh, I hope it all goes without saying but all of this needs to support IPv6 not just IPv4 since we are in the IoT age. :)