Skip to content

Commit 9cfe8f8

Browse files
Update readme.md
1 parent 59e9d9f commit 9cfe8f8

1 file changed

Lines changed: 5 additions & 2 deletions

File tree

  • deploy/az/servicefabric/LinuxContainers

deploy/az/servicefabric/LinuxContainers/readme.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,7 @@
1-
# Deploying a Service Fabric cluster based on Linux nodes (No Secured)
1+
# Deploying a Service Fabric cluster based on Linux nodes
2+
3+
## A. Not secured cluster (SF Linux cluster)
4+
For a secured cluster, see option B. below.
25
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
36

47
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.
@@ -44,7 +47,7 @@ create-resources.cmd servicefabric\LinuxContainers\servicefabricdeploy qa-eshop-
4447

4548
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.
4649

47-
# Deploying Azure Service Fabric (Secured)
50+
## B. Secured cluster (SF Linux cluster)
4851

4952
The ARM template `servicefabricdeploysecured.json` and its parameter file (`servicefabricdeploysecured.parameters.json`) are used to create a service fabric cluster environment for linux containers secured with a certificate.
5053

0 commit comments

Comments
 (0)