Skip to content

Commit fa92ab0

Browse files
Update readme.md
1 parent 0e855cd commit fa92ab0

1 file changed

Lines changed: 9 additions & 2 deletions

File tree

  • deploy/az/servicefabric/WindowsContainers

deploy/az/servicefabric/WindowsContainers/readme.md

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ However, when creating a cluster, there are quite a few configurations to take i
99

1010
Because of those reasons, we have created a set of ARM templates and scripts so you can create, re-create and configure the SF clusters much faster, as explained below:
1111

12-
Within eShopOnContainers root folder, at the folder [..\deploy\az\servicefabric\WindowsContainers](https://github.com/dotnet-architecture/eShopOnContainers/tree/dev/deploy/az/servicefabric/WindowsContainers), you can find the ARM template `servicefabricdeploy.json` and its parameters file (`servicefabricdeploy.parameters.json`) to create a Service Fabric cluster environment for Windows Containers.
12+
Within eShopOnContainers root folder, at the folder [..\deploy\az\servicefabric\WindowsContainers](https://github.com/dotnet-architecture/eShopOnContainers/tree/dev/deploy/az/servicefabric/WindowsContainers), you can find the ARM template `servicefabricdeploy.json` and its parameters file (`servicefabricdeploy.parameters.json`) to create a Service Fabric cluster environment for Windows Containers (NOT SECURED CLUSTER).
1313

1414
## Edit the servicefabricdeploy.parameters.json file
1515

@@ -44,11 +44,18 @@ create-resources.cmd servicefabric\WindowsContainers\servicefabricdeploy qa-esho
4444
```
4545

4646
You should see a similar execution to the following:
47+
++++++++++++ IMAGE TBD ++++++++++++++
48+
49+
Now, if you go to your subscription in Azure, you should be able to see the SF cluster already created and available, like in the following image:
50+
51+
++++++++++++ IMAGE TBD ++++++++++++++
52+
53+
In this case, this is an unsecured SF cluster with a single Windows node, good for initial tests and getting started with SF.
4754

4855

4956
## B. Secured cluster (SF Windows cluster)
5057

51-
The ARM template `servicefabricdeploysecured.json` and its parameter file (`servicefabricdeploysecured.parameters.json`) are used to create a service fabric cluster environment for windows containers secured with a certificate.
58+
Within eShopOnContainers root folder, at the folder [..\deploy\az\servicefabric\WindowsContainers](https://github.com/dotnet-architecture/eShopOnContainers/tree/dev/deploy/az/servicefabric/WindowsContainers), you can find the ARM template `servicefabricdeploysecured.json` and its parameter file (`servicefabricdeploysecured.parameters.json`) to create a secured Service Fabric cluster environment for Windows Containers (IN THIS CASE, IT IS A SECURED CLUSTER USING A CERTIFICATE).
5259

5360
## Create Azure Keyvault service
5461
Go to PortalAzure and create a Keyvault service. Make sure Enable access for deployment checkboxes are selected.

0 commit comments

Comments
 (0)