Hello @James Bissett ,
In order for the AKS POD container to communicate to a PAAS SQL Service , it needs a VNET service endpoint followed by a vnet-rule which needs to be added .
I just tried below git hub document successfully , which talks about an AKS POD communication to MySQL PAAS Service.
https://github.com/yoshioterada/k8s-Azure-Container-Service-AKS--on-Azure/blob/master/Kubernetes-Workshop9.md
Able to login to the pod container and perform mysql operations.
Kindly let me know if you have additional questions.
When trying to add the subnet to the mysql instance,
az mysql server vnet-rule create \
-n k8sRule \
-g myResGroup \
-s myDB \
--subnet /subscriptions/{mysub|/resourceGroups/{myResGroup}/providers/Microsoft.Network/virtualNetworks/{myvnet}/subnets/{mysubvnet}
i get the following error
Deployment failed. Correlation ID: d0b49788-a3bb-402a-81e5-888092148298. This feature is not available for the selected edition 'Basic'
In the github link you supplied in your answer, the mysql creation is actually creating a tier level "General Purpose" not "Basic:
"administratorLogin": "yoterada",
"earliestRestoreDate": "2018-06-29T12:21:50.183000+00:00",
"fullyQualifiedDomainName": "my-mysqlserver.mysql.database.azure.com",
"id": "/subscriptions/f77aafe8-****-****-****-d0c37687ef70/resourceGroups/MySQL-RG/providers/Microsoft.DBforMySQL/servers/my-mysqlserver",
"location": "japaneast",
"name": "my-mysqlserver",
"resourceGroup": "MySQL-RG",
"sku": {
"capacity": 2,
"family": "Gen4",
"name": "GP_Gen4_2",
"size": null,
"tier": "GeneralPurpose"
},
Hello @James Bissett ,
Apologies for late response. Yeah , you won't be able to add vnet-rule for the basic SKU. I was able to communicate from container pod to the Basic MySQL PAAS instance with out any additional vnet-rule.
Regards,
Shiva.
I solved the problem by adding an entry in private DNS to allow resolution of the URL from the pod. Also worth noting that the userId does require the @dbname to qualify it it in the PaaS connection.
Sign in to comment