-
Notifications
You must be signed in to change notification settings - Fork 125
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #637 from MicrosoftDocs/main
11/21/2024 AM Publish
- Loading branch information
Showing
21 changed files
with
96 additions
and
49 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,52 @@ | ||
--- | ||
title: Set up IP tags on a Service Fabric managed cluster | ||
description: Learn how to set IP tags on a Service Fabric managed cluster. | ||
ms.topic: how-to | ||
ms.author: tomcassidy | ||
author: tomvcassidy | ||
ms.service: azure-service-fabric | ||
services: service-fabric | ||
ms.date: 10/30/2024 | ||
--- | ||
|
||
# Set up IP tags on a Service Fabric managed cluster (SFMC) | ||
|
||
An IP tag represents a group of IP address prefixes from a given Azure service. Microsoft manages the address prefixes encompassed by the IP tag and automatically updates the service tag as addresses change, minimizing the complexity of frequent updates to network security rules. You can use IP tags to define network access controls on [network security groups](/azure/virtual-network/network-security-groups-overview#security-rules), [Azure Firewall](/azure/firewall/service-tags), and user-defined routes. By adding IP tags, an SFMC cluster has an added layer of security. | ||
|
||
> [!NOTE] | ||
> The `IPTag` property only applies to the public IPv4 and IPv6 addresses of the default cluster load balancer. | ||
## Limitations | ||
|
||
You shouldn't implement IP tags on existing clusters. | ||
|
||
## Prerequisites | ||
|
||
Ensure that you [provisioned IPTags beforehand](/powershell/module/az.network/new-azpublicipaddress#example-3-create-a-new-public-ip-address-with-iptag). | ||
|
||
## Modify your ARM template | ||
|
||
When creating a new Service Fabric managed cluster, you need to add to the ARM template with the following property: | ||
|
||
|
||
```json | ||
{ | ||
"type": "Microsoft.ServiceFabric/managedClusters", | ||
"apiVersion": "2021-07-01-preview", | ||
"properties": { | ||
"ipTags": [ | ||
{ | ||
"ipTagType": "string", | ||
"tag": "string" | ||
} | ||
] | ||
} | ||
} | ||
``` | ||
|
||
Then, deploy your SFMC cluster as normal. | ||
|
||
## Next steps | ||
|
||
* To see more about Service Fabric managed cluster network settings, see [Configure network settings for Service Fabric managed clusters](how-to-managed-cluster-networking.md). | ||
* To learn about using public IP prefixes in managed clusters, see [Use a Public IP address prefix in a Service Fabric managed cluster](how-to-managed-cluster-public-ip-prefix.md). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Binary file removed
BIN
-87.7 KB
...ric/media/service-fabric-cluster-creation-setup-aad/portal-client-api-grant.png
Binary file not shown.
Binary file removed
BIN
-91.1 KB
...media/service-fabric-cluster-remote-connect-to-azure-cluster-node/lb-window.png
Binary file not shown.
Binary file removed
BIN
-66.8 KB
articles/service-fabric/media/service-fabric-quickstart-containers/publish-app.png
Binary file not shown.
Binary file removed
BIN
-185 KB
...es/service-fabric/media/service-fabric-tutorial-monitoring-aspnet/ai-search.png
Binary file not shown.
Binary file removed
BIN
-126 KB
...ervice-fabric/media/service-fabric-tutorial-monitoring-aspnet/trace-details.png
Binary file not shown.
Binary file removed
BIN
-58.3 KB
...ric/media/service-fabric-tutorial-monitoring-wincontainers/solution-landing.png
Binary file not shown.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.