Skip to content

Commit 795edef

Browse files
Update readme.md
1 parent ad5b4c5 commit 795edef

1 file changed

Lines changed: 4 additions & 0 deletions

File tree

  • deploy/az/servicefabric/LinuxContainers

deploy/az/servicefabric/LinuxContainers/readme.md

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

33
## A. Not secured cluster (SF Linux 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.
@@ -43,6 +44,9 @@ For example, to deploy the cluster to a new resourcegroup located in westus, go
4344
create-resources.cmd servicefabric\LinuxContainers\servicefabricdeploy qa-eshop-sflinux-resgrp -c westus
4445
```
4546

47+
You should see a similar execution to the following:
48+
![image](https://user-images.githubusercontent.com/1712635/31638180-15da9f84-b287-11e7-9d4e-604f33690198.png)
49+
4650
## Deploy eShopOnServiceFabric with Visual Studio.
4751

4852
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.

0 commit comments

Comments
 (0)