Private link suddenly refusing connections to DB from kubernetes clusters

Question

Hello,

We have been operating private link for some time between our K8S cluster and database. Since today the private link is refusing connections from the cluster.

We had to delete the private link resource in order for our services to connect to the database.

We'd like to open a private ticket for this issue where I can input sensitive details.

Answer 1

Hi Tigrish Chakrabarty

Since you've already restarted the DB server and that temporarily fixed the issue, here are a few things you might want to check:

1. Managed Private Endpoint Approval: Make sure that the managed private endpoint is approved. In the Azure portal, navigate to the Networking section and check if the endpoint status is “Approved.”
2. Network Security Groups (NSGs): Review the inbound rules of the NSGs in the subnet where your private link resource and Kubernetes cluster are deployed. Ensure that there are no rules blocking the connection.
3. Private Link Service Configuration: Double-check that the private link service is properly set up to accept connections from your cluster. This includes confirming that the service is healthy and operational.
4. Port Configuration: If you're using Azure Kubernetes Service (AKS), verify that the port configurations match among your services. This includes checking the monitored service, load balancer, and private link service.
5. DNS Configuration: If you're encountering connectivity issues, check your DNS settings. Ensure it correctly resolves private IP addresses for resources in the private link.

If these suggestions don't resolve your issue, we request you to open a support ticket.

I hope this information is helpful! If my answer helped you resolve your issue, please consider marking it as the correct answer or Upvote. This helps others in the community find solutions more easily. Thanks!