Skip to content

Commit 181efb3

Browse files
Update readme.md
1 parent 3249ce3 commit 181efb3

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

  • deploy/az/servicefabric/WindowsContainers

deploy/az/servicefabric/WindowsContainers/readme.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,7 @@
22

33
## A. Not secured cluster (SF Windows cluster)
44
For a secured cluster, see option B. below.
5+
56
You can always deploy a SF cluster through the Azure portal, as explained in this article: https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-get-started-azure-cluster
67

78
However, when creating a cluster, there are quite a few configurations to take into account, like enabling the internal DNS service or Reverse Proxy service, choosing between Linux/Windows, open/publish your application ports in the load-balancer and most of all (the most complex setup) how to create a secure cluster.
@@ -42,9 +43,8 @@ For example, to deploy the cluster to a new resourcegroup located in westus, usi
4243
create-resources.cmd servicefabric\WindowsContainers\servicefabricdeploy qa-eshop-sfwin-resgrp -c westus
4344
```
4445

45-
## Deploy eShopOnServiceFabric with Visual Studio.
46+
You should see a similar execution to the following:
4647

47-
Alternatively, instead of using ARM templates, you can deploy eShop on service fabric directly by publishing the project eShopOnServiceFabric in eShopOnContainers-ServicesAndWebApps.sln with Visual Studio publish tool.
4848

4949
## B. Secured cluster (SF Windows cluster)
5050

0 commit comments

Comments
 (0)