"No such host is known" when interacting with a branch versioned feature service via Workflow Manager in a Kubernetes deployment

Error Message

If Workflow Manager Server is federated with ArcGIS Enterprise on Kubernetes, steps that interact with branch-versioned feature services hosted on the Kubernetes portal may return a "no such host is known" error followed by a URL ending in .local. Affected steps include the Claim Version, Create Version, Create Replica, Evaluate Data Quality, and Reconcile and Post steps.

An example error message in the log files may appear as follows:

Failed to create version JOB_1 on data source Map1 for job vh1JpeF2RGu-H69nSpUShA with error message: 
No such host is known (arcgis-private-ingress.endeavour-daily.svc.cluster.local): No such host is known 
(arcgis-private-ingress.endeavour-daily.svc.cluster.local)

Cause

The administrative URLs used by Workflow Manager end in .local, which isn’t accessible outside the Kubernetes cluster.

For example, the following snippet of a portal item's JSON with an invalid privateUrl:

"numViews": 22,
"itemControl": "admin",
"privateUrl": "https://arcgis-private-ingress.endeavour-daily.svc.cluster.local/gis/rest/services/Map1/FeatureS
"scoreCompleteness": 25,

Solution or Workaround

Update the privatePortalURL and the administrative URLs with the front-facing URLs to allow Workflow Manager access to the branch-versioned feature services hosted on the Kubernetes portal.

See: Update (Organization Properties) | ArcGIS REST APIs | ArcGIS Developers