This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I have a service deployed in Private AKS cluster and database is SQL server in Azure VM, both AKS and SQL server are in different VNET. We can't go with VNET peering since there is IP range conflicts between vnets. Creating private endpoint also won't work since Azure VM are PaaS? Please suggest other options to connect private aks cluster with Azure SQL server.
Azure VM is not PaaS (Platform-as-a-Service), but IaaS (Infrastructure-as-a-Service). Whether this affects the possibility to create private endpoints, I don't know. Or are you actually using Azure SQL Database (which is PaaS)?
Sorry, I was to mention Azure VM are not PaaS. I am using Azure VM(SQL server).
Hello @Gnanasoundari
Thank you for reaching out to the Microsoft Q&A platform.
If VNET peering and private endpoints are not feasible options for connecting your Private AKS cluster with your Azure SQL Server, you can consider using Azure ExpressRoute or VPN Gateway to establish a secure connection between the two networks.
You can use ExpressRoute to establish a private connection between your Private AKS cluster and your Azure SQL Server. This will allow you to securely access your SQL Server from your AKS cluster without exposing it to the public internet.
Alternatively, you can use Azure VPN Gateway to create a site-to-site VPN connection between your Private AKS cluster and your Azure SQL Server. This will allow you to securely access your SQL Server from your AKS cluster over the public internet.
Both ExpressRoute and VPN Gateway provide secure and reliable connectivity options for connecting your Private AKS cluster with your Azure SQL Server. You can choose the option that best fits your requirements and budget.
I hope this helps you find a suitable solution for your scenario. Let me know if you have any further questions or if there's anything else I can help you with.