Anyscale private cluster: Operator cannot reach the control plane over Private Link

TL;DR

Private Blob and DFS endpoints resolve and route inside the VNet, so run proof uploads from the Linux jump host rather than the workstation. Confirm the Private Link endpoint approval, private DNS resolution, and the anyscaleplatform operatorcontrolplaneurl setting.

The error

Operator cannot reach the control plane over Private Link

Fix

1. Private Blob and DFS endpoints resolve and route inside the VNet, so run proof uploads from the Linux jump host rather than the workstation. Expected: You get the expected result; the problem is gone.

2. Re-run the original operation and confirm the error is gone. Expected: no error, normal output.

When to use

• You hit this exact error with Anyscale private cluster.
• The symptom matches: Operator cannot reach the control plane over Private Link.

When NOT to use

• A different error message from Anyscale private cluster; the cause here is specific to this error.
• Unrelated Anyscale private cluster issues (different feature, different failure).
• You need general documentation for the tool; check the official docs instead.

Compatibility

Reported against Anyscale private cluster. Source: https://github.com/kenkilty/aks-anyscale-private-cluster-sample/blob/HEAD/docs/modules/module-3-lab-workload.md.

Variant phrasings

Operator cannot reach the control plane over Private Link

Why it happens

In a private AKS cluster the Anyscale Operator must reach the control plane through Private Link. A silent connectivity gap stops everything.

Edge cases

• If your error message differs even slightly, this is probably a different issue; search the exact text.
• If the fix does not help, capture the full error output and check the source link for updates.

Source

https://github.com/kenkilty/aks-anyscale-private-cluster-sample/blob/HEAD/docs/modules/module-3-lab-workload.md

Source: In a private AKS cluster the Anyscale Operator must reach the control plane through Private Link. A silent connectivity gap stops everything.

Verified resolution: [kenkilty/aks-anyscale-private-cluster-sample]: confirm the Private Link endpoint approval, private DNS resolution, and the anyscaleplatform operatorcontrolplaneurl setting. Private Blob and DFS endpoints resolve and route inside the VNet, so run proof uploads from the Linux jump host rather than the workstation. If bootstrap steps fail, verify the managed identity is present in the configured AKS admin principal map before chasing Terraform errors.

Source URL: https://github.com/kenkilty/aks-anyscale-private-cluster-sample/blob/HEAD/docs/modules/module-3-lab-workload.md