Skip to content

Commit 1498425

Browse files
authored
Merge pull request #42530 from rwike77/certupgrade
adding warning about sharing certs and ports
2 parents c9a1150 + 7231ecb commit 1498425

File tree

2 files changed

+14
-5
lines changed

2 files changed

+14
-5
lines changed

articles/service-fabric/service-fabric-assign-policy-to-endpoint.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -41,6 +41,11 @@ For an HTTPS endpoint, also indicate the name of the certificate to return to th
4141
</Policies
4242
```
4343

44+
> [!WARNING]
45+
> When using HTTPS, do not use the same port and certificate for different service instances (independant of the application) deployed to the same node. Upgrading two different services using the same port in different application instances will result in an upgrade failure. For more information, see [Upgrading multiple applications with HTTPS endpoints
46+
](service-fabric-application-upgrade.md#upgrading-multiple-applications-with-https-endpoints).
47+
>
48+
4449
<!--Every topic should have next steps and links to the next logical set of content to keep the customer engaged-->
4550
For next steps, read the following articles:
4651
* [Understand the application model](service-fabric-application-model.md)

articles/service-fabric/service-fabric-service-manifest-resources.md

Lines changed: 9 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -102,7 +102,11 @@ The HTTPS protocol provides server authentication and is also used for encryptin
102102
> [!NOTE]
103103
> A service’s protocol cannot be changed during application upgrade. If it is changed during upgrade, it is a breaking change.
104104
>
105-
>
105+
106+
> [!WARNING]
107+
> When using HTTPS, do not use the same port and certificate for different service instances (independant of the application) deployed to the same node. Upgrading two different services using the same port in different application instances will result in an upgrade failure. For more information, see [Upgrading multiple applications with HTTPS endpoints
108+
](service-fabric-application-upgrade.md#upgrading-multiple-applications-with-https-endpoints).
109+
>
106110
107111
Here is an example ApplicationManifest that you need to set for HTTPS. The thumbprint for your certificate must be provided. The EndpointRef is a reference to EndpointResource in ServiceManifest, for which you set the HTTPS protocol. You can add more than one EndpointCertificate.
108112

@@ -151,11 +155,11 @@ For Linux clusters, the **MY** store defaults to the folder **/var/lib/sfcerts**
151155

152156
## Overriding Endpoints in ServiceManifest.xml
153157

154-
In the ApplicationManifest add a ResourceOverrides section which will be a sibling to ConfigOverrides section. In this section you can specify the override for the Endpoints section in the resources section specified in the Service manifest. Overriding endpoints is supported in runtime 5.7.217/SDK 2.7.217 and higher.
158+
In the ApplicationManifest add a ResourceOverrides section, which will be a sibling to ConfigOverrides section. In this section, you can specify the override for the Endpoints section in the resources section specified in the Service manifest. Overriding endpoints is supported in runtime 5.7.217/SDK 2.7.217 and higher.
155159

156160
In order to override EndPoint in ServiceManifest using ApplicationParameters change the ApplicationManifest as following:
157161

158-
In the ServiceManifestImport section add a new section "ResourceOverrides"
162+
In the ServiceManifestImport section, add a new section "ResourceOverrides".
159163

160164
```xml
161165
<ServiceManifestImport>
@@ -185,13 +189,13 @@ In the Parameters add below:
185189
</Parameters>
186190
```
187191

188-
While deploying the application now you can pass in these values as ApplicationParameters for example:
192+
While deploying the application you can pass in these values as ApplicationParameters. For example:
189193

190194
```powershell
191195
PS C:\> New-ServiceFabricApplication -ApplicationName fabric:/myapp -ApplicationTypeName "AppType" -ApplicationTypeVersion "1.0.0" -ApplicationParameter @{Port='1001'; Protocol='https'; Type='Input'; Port1='2001'; Protocol='http'}
192196
```
193197

194-
Note: If the values provide for the ApplicationParameters is empty we go back to the default value provided in the ServiceManifest for the corresponding EndPointName.
198+
Note: If the values provide for the ApplicationParameters is empty, we go back to the default value provided in the ServiceManifest for the corresponding EndPointName.
195199

196200
For example:
197201

0 commit comments

Comments
 (0)