<p>I need to use best-suited cni for Dotnet core with SQL server(Same Network but different IP)  Kubernetes deployment.</p>

<p>CNI's are made in a way that they abstract network logic from apps. This allows us to use CNI's without worrying too much about the details.</p>

<p>If you are getting started with CNI, you could use pretty much any CNI you like, as your apps will use the network as usual. </p>

<p>It does not matter which app / language / framework / database you use, the CNI only takes care of networking which your app will never know anything about. </p>

<p>CNI is mainly there to allow network policies and manage node networking. </p>

<p>If you want to see a great post about CNI outside Kubernetes (<a href="https://medium.com/@vikram.fugro/project-calico-the-cni-way-659d057566ce" rel="nofollow noreferrer">This</a> will give you a idea of what CNI actually is and does). 
*Not written by me, but a great post to understand CNI.</p>

<p>So whichever you choose, will be purely merited by the CNI and not how it works with your app. </p>

<p>For a start, Calico is a good choice as it's simple to deploy and use, and allows Networking policies. </p>
