You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"When an endpoint resource is defined in the service manifest, Service Fabric assigns ports from the reserved application port range when a port isn't specified explicitly" So when a port is defined it can be outside the application port range? then why the port range in the first place? port range is on 20000 while manifest it is like 8444. So much difference
Document details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
ID: 94aa1985-f344-537c-ba38-d5a9a1626a4d
Version Independent ID: 5d685dd3-dc6b-879c-202c-c20d1fe21066
@theBlueclouds Thank you for taking the time to ask this question and seek clarification. Did you include a specific port number or did you leave it blank, wishing to be provisioned a port number within the range specified in the manifest file but, in fact, have been provisioned a port number outside that range in the manifest file? Please clarify, as we are actively looking into your query,
@theBlueclouds We will now close this issue. Please come back whenever you are ready. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.
"When an endpoint resource is defined in the service manifest, Service Fabric assigns ports from the reserved application port range when a port isn't specified explicitly" So when a port is defined it can be outside the application port range? then why the port range in the first place? port range is on 20000 while manifest it is like 8444. So much difference
Document details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: