Can't Publish to Secure Service Fabric Cluster via VSTS

Question

I'm trying to deploy to a secure Service Fabric Cluster, installed on a network server, secured via certificates via VSTS, but I'm unable to.

I can connect via powershell from my dev machine, I can publish via Visual Studio but publishing via VSTS is not working.

I'm fairly sure it's a configuration issue when creating the 'Cluster Connection' in VSTS but not sure why?

The error I get is as follows:

2018-10-10T21:14:35.1844975Z Imported cluster client certificate with 
thumbprint 'd5df1g65d1fg651dfg651df6g51d6fg516d51651'.
2018-10-10T21:15:20.5985717Z ##[warning]Failed to contact Naming Service. 
Attempting to contact Failover Manager Service...
2018-10-10T21:16:00.6325833Z ##[warning]Failed to contact Failover Manager 
Service, Attempting to contact FMM...
2018-10-10T21:16:40.7508422Z ##[warning]No such host is known
2018-10-10T21:16:41.0348119Z Service fabric SDK version: 3.2.176.9494.
2018-10-10T21:16:41.7540933Z ##[error]No cluster endpoint is reachable, 
please check if there is connectivity/firewall/DNS issue.

Hoping someone has seen this before.

EDIT:

Note, I am able to deploy to this server via VSTS directly for IIS deployments, as an agent already exists and has been downloaded and configured with the appropriate proxy settings.

So I'm guessing adding a proxy switch somewhere is not feasible then... or possibly nobody has encountered this issue yet? Befuddling! — Billy Ray Valentine

Diego Mendes Diego Mendes · Accepted Answer · 2018-10-10T22:28:00

As the message suggests:

No cluster endpoint is reachable, please check if there is connectivity/firewall/DNS issue.

If your cluster is hosted on-premises, and the VSTS agent is hosted(Azure), you won't be able to deploy from the hosted agent to your localnetwork.

You will have to create a custom agent in a machine connected to your network.

Can't Publish to Secure Service Fabric Cluster via VSTS

1 Answers