Bug Report: Policy initiative for HDInsight private endpoints uses "cluster" groupId, when available ones are "headnode" and "gateway"

Open juanandmsft opened this issue 7 months ago • 1 comments

Revisiting this issue as follow-up on #1510 ... The built-in policy PrivateDNSZone_DINE.json uses a parameter for groupId, it is not hardcoded in the policy.

The issue is that the custom initiative specifies "cluster" for the parameter value, when the acceptable values are "gateway" and "headnode".

The initiative would also need two policyDefinitionReferenceIds, i.e. "DINE-Private-DNS-Azure-HDInsightHeadnode" and "DINE-Private-DNS-Azure-HDInsightGateway" or similar.

It is noticeable, however, that during my tests assigning the built-in policy with the correct groupId values, the zone is correctly associated with both gateway and headnode PEs, but no records are populated in them.

According to documentation, DNS entries are manual.

Cheers.

Jun 28 '25 09:06 juanandmsft

@juanandmsft thanks for reporting. I'll add to the backlog to change HDInsights pDNS to use the two groupIds instead of "cluster".

Jul 01 '25 10:07 Springstone