Service Fabric releases
This article provides more information on the latest releases and updates to the Service Fabric runtime and SDKs.
The following resources are also available:
Service Fabric 10.1
We're excited to announce that the 10.1 release of the Service Fabric runtime started rolling out to the various Azure regions along with tooling and SDK updates. The updates for .NET SDK, Java SDK, and Service Fabric runtimes can be downloaded from the links provided in Release Notes. The SDK, NuGet packages, and Maven repositories are available in all regions within 7-10 days.
Key announcements
- Service Fabric runtime defines two client roles - Admin and Client. The Admin role is highly privileged, and undistinguishable from the runtime itself, which can be problematic in shared clusters, where all tenants have Admin privileges and can perform unintended destructive operations on the services of another tenant. In this release, we introduce a third client role - ElevatedAdmin, which, combined with properly configured Security/ClientAccess section of cluster manifest, can prevent the described scenario.
- Service Fabric now emits a health event visible in SFX/SFE when Sessions are exhausted.
- This allows the weight of InBuild Auxiliary replicas to be set when applied to InBuild throttling. A higher weight means that an InBuild Auxiliary replica takes up more of the InBuild limit, and likewise a lower weight would consume less of the limit, allowing more replicas to be placed InBuild before the limit is reached.
- Starting with Cumulative Update 3.0 (CU3) of the Service Fabric 10.1 runtime, the .NET 8 runtime is supported.
- For those interested in using .NET 8, keep the following in mind:
- You need to rebuild and redeploy your applications with .NET 8. This step isn't necessary if you want to continue using older versions of .NET.
- If you deploy self-contained applications, know that applications are no longer self-contained by default in .NET 8. You must explicitly add and set the
SelfContainedproperty totrueto your projects in .NET 8. - For customers utilizing Service Fabric Remoting v1, customers must enable the
BinaryFormatter, which isn't enabled with .NET 8. For the procedure to enable BinaryFormatter, see the BinaryFormatter Obsoletion Strategy GitHub page.
- For those interested in using .NET 8, keep the following in mind:
Service Fabric 10.1 releases
| Release date | Release | More info |
|---|---|---|
| November 1, 2023 | Azure Service Fabric 10.1 Release | Release notes |
| April 1, 2024 | Azure Service Fabric 10.1 Second Refresh Release | Release notes |
| June 15, 2024 | Azure Service Fabric 10.1 Third Refresh Release | Release notes |
| August 15, 2024 | Azure Service Fabric 10.1 Fourth Refresh Release | Release notes |
| September 30, 2024 | Azure Service Fabric 10.1 Fifth Refresh Release | Release notes |
| October 31, 2024 | Azure Service Fabric 10.1 Sixth Refresh Release | Release notes |
Service Fabric 10.0
We're excited to announce that the 10.0 release of the Service Fabric runtime has started rolling out to the various Azure regions along with tooling and SDK updates. The updates for .NET SDK, Java SDK, and Service Fabric runtimes can be downloaded from the links provided in Release Notes. The SDK, NuGet packages, and Maven repositories are available in all regions within 7-10 days.
Key announcements
- Enhance Container image pruning.
- Balancing of a cluster per node type.
- Expose health check phase and timer for application and cluster upgrade.
- Support ESE.dll version compatibility in the replica building process.
- Enable Lease probes.
- Extend the FabricClient constructor to include "SecurityCredentials" without "HostEndpoints".
- Security audit of cluster management endpoint settings.
Service Fabric 10.0 releases
| Release date | Release | More info |
|---|---|---|
| September 09, 2023 | Azure Service Fabric 10.0 Release | Release notes |
| November 1, 2023 | Azure Service Fabric 10.0 First Refresh Release | Release notes |
| April 1, 2024 | Azure Service Fabric 10.0 Third Refresh Release | Release notes |
| June 15, 2024 | Azure Service Fabric 10.0 Fourth Refresh Release | Release notes |
| August 15, 2024 | Azure Service Fabric 10.0 Fifth Refresh Release | Release notes |
| September 30, 2024 | Azure Service Fabric 10.0 Sixth Refresh Release | Release notes |
| October 31, 2024 | Azure Service Fabric 10.0 Seventh Refresh Release | Release notes |
Service Fabric 9.1
We're excited to announce roll outs of the 9.1 release of the Service Fabric runtime Azure regions along with tooling and SDK updates. The updates for .NET SDK, Java SDK, and Service Fabric runtimes can be downloaded from the links provided in Release Notes. The SDK, NuGet packages, and Maven repositories are available in all regions within 7-10 days.
Key announcements
- Azure Service Fabric blocks deployments that don't meet Silver or Gold durability requirements starting on 11/10/2022 (The date is extended from 10/30/2022 to 11/10/2022). Five VMs or more will be enforced with this change for newer clusters created after 11/10/2022 to help avoid data loss from VM-level infrastructure requests for production workloads. VM count requirement isn't changing for Bronze durability. Enforcement for existing clusters will be rolled out in the coming months.
- Azure Service Fabric node types with Virtual Machine Scale Set durability of Silver or Gold should always have the property "virtualMachineProfile.osProfile.windowsConfiguration.enableAutomaticUpdates" set to false in the scale set model definition. Setting enableAutomaticUpdates to false prevent unintended OS restarts due to the Windows updates like patching, which can impact the production workloads. Instead, you should enable Automatic OS upgrades through Virtual Machine Scale Set OS Image updates by setting "enableAutomaticOSUpgrade" to true. With automatic OS image upgrades enabled on your scale set, an extra patching process through Windows Update isn't required.
- Starting 9.1.1436.9590, Service Fabric Runtime provides a configuration on Linux and Windows called "Setup/BlockAccessToWireServer" to allow the runtime deployer to set up Access Control Lists (ACLs) on the Virtual Machine (VM) to prevent access from containers to the wire server. These ACLs are kept in sync during new cluster creation/upgrade and VM/SF node restart scenarios.
Service Fabric 9.1 releases
| Release date | Release | More info |
|---|---|---|
| October 24, 2022 | Azure Service Fabric 9.1 | Release notes |
| December 8, 2022 | Azure Service Fabric 9.1 First Refresh Release | Release notes |
| March 1, 2023 | Azure Service Fabric 9.1 Second Refresh Release | Release notes |
| April 6, 2023 | Azure Service Fabric 9.1 Third Refresh Release | Release notes |
| May 15, 2023 | Azure Service Fabric 9.1 Fourth Refresh Release | Release notes |
| June 19, 2023 | Azure Service Fabric 9.1 Fifth Refresh Release | Release notes |
| August 30, 2023 | Azure Service Fabric 9.1 Sixth Refresh Release | Release notes |
| November 1, 2023 | Azure Service Fabric 9.1 Seventh Refresh Release | Release notes |
| April 1, 2024 | Azure Service Fabric 9.1 Ninth Refresh Release | Release notes |
| June 15, 2024 | Azure Service Fabric 9.1 Tenth Refresh Release | Release notes |
| August 15, 2024 | Azure Service Fabric 9.1 Eleventh Refresh Release | Release notes |
| September 30, 2024 | Azure Service Fabric 9.1 Twelfth Refresh Release | Release notes |
| October 31, 2024 | Azure Service Fabric 9.1 Thirteenth Refresh Release | Release notes |
Service Fabric 9.0
We're excited to announce that 9.0 release of the Service Fabric runtime has started rolling out to the various Azure regions along with tooling and SDK updates. The updates for .NET SDK, Java SDK, and Service Fabric runtime are available through Web Platform Installer, NuGet packages, and Maven repositories.
Key announcements
- General Availability Support for .NET 6.0
- General Availability Support for Ubuntu 20.04
- General Availability Support for Multi-AZ within a single Virtual Machine Scale Set
- Added support for IHost, IHostBuilder, and Minimal Hosting Model
- Enabling opt-in option for Data Contract Serialization (DCS) based remoting exception
- Support creation of End-to-End Developer Experience for Linux development on Windows using WSL2
- Support for parallel recursive queries to Service Fabric DNS Service
- Support for Managed KeyVaultReference
- Expose Container ID for currently deployed code packages
- Added Fabric_InstanceId environment variable for stateless guest applications
- Exposed API for reporting MoveCost
- Enforce a configurable Max value on the InstanceCloseDelayDuration
- Added ability to enumerate actor reminders
- Made updates to platform events
- Introduced a property in Service Fabric runtime that can be set via SFRP as the Azure Resource Manager resource ID
- Exposed application type provision timestamp
- Support added for Service Fabric Resource Provider (SFRP) metadata to application type + version entities, starting with Azure Resource Manager resource ID
- Windows Server 2022 is now supported as of the 9.0 CU2 release.
- Mirantis Container runtime support on Windows for Service Fabric containers
- The Azure Web Platform Installer (WebPI) used for installing Service Fabric SDK and Tools was retired on July 1, 2022.
- Azure Service Fabric blocks deployments that don't meet Silver or Gold durability requirements starting on 9/30/2022. 5 VMs or more will be enforced with this change to help avoid data loss from VM-level infrastructure requests for production workloads. Enforcement for existing clusters will be rolled out in the coming months.
- Azure Service Fabric node types with Virtual Machine Scale Set durability of Silver or Gold should always have Windows update explicitly disabled to avoid unintended OS restarts due to the Windows updates, which can impact the production workloads. This can be done by setting the "enableAutomaticUpdates": false, in the Virtual Machine Scale Set OSProfile. Consider enabling Automatic Virtual Machine Scale Set Image upgrades instead. The deployments will start failing from 09/30/2022 for new clusters, if the WindowsUpdates aren't disabled on the Virtual Machine Scale Set. Enforcement for existing clusters will be rolled out in the coming months.
Service Fabric 9.0 releases
| Release date | Release | More info |
|---|---|---|
| April 29, 2022 | Azure Service Fabric 9.0 | Release notes |
| June 06, 2022 | Azure Service Fabric 9.0 First Refresh Release | Release notes |
| July 14, 2022 | Azure Service Fabric 9.0 Second Refresh Release | Release notes |
| September 13, 2022 | Azure Service Fabric 9.0 Third Refresh Release | Release notes |
| October 11, 2022 | Azure Service Fabric 9.0 Fourth Refresh Release | Release notes |
| December 8, 2022 | Azure Service Fabric 9.0 Fifth Refresh Release | Release notes |
| March 1, 2023 | Azure Service Fabric 9.0 Seventh Refresh Release | Release notes |
| April 6, 2023 | Azure Service Fabric 9.0 Eighth Refresh Release | Release notes |
| May 15, 2023 | Azure Service Fabric 9.0 Ninth Refresh Release | Release notes |
| November 1, 2023 | Azure Service Fabric 9.0 Twelfth Refresh Release | Release notes |
Service Fabric 8.2
We're excited to announce that 8.2 release of the Service Fabric runtime started rollout to the various Azure regions along with tooling and SDK updates. The updates for .NET SDK, Java SDK, and Service Fabric runtime are available through Web Platform Installer, NuGet packages, and Maven repositories.
Key announcements
- Expose an API in Cluster Manager to note if upgrade is impactful
- Azure Service Fabric blocks deployments that don't meet Silver or Gold durability requirements starting on 11/10/2022 (The date is extended from 10/30/2022 to 11/10/2022). Five VMs or more will be enforced with this change for newer clusters created after 11/10/2022 to help avoid data loss from VM-level infrastructure requests for production workloads. VM count requirement isn't changing for Bronze durability. Enforcement for existing clusters will be rolled out in the coming months.
- Azure Service Fabric node types with Virtual Machine Scale Set durability of Silver or Gold should always have the property "virtualMachineProfile.osProfile.windowsConfiguration.enableAutomaticUpdates" set to false in the scale set model definition. Setting enableAutomaticUpdates to false prevents unintended OS restarts due to the Windows updates like patching, which can impact the production workloads. Instead, you should enable Automatic OS upgrades through Virtual Machine Scale Set OS Image updates by setting "enableAutomaticOSUpgrade" to true. With automatic OS image upgrades enabled on your scale set, an extra patching process through Windows Update isn't required.
Service Fabric 8.2 releases
| Release date | Release | More info |
|---|---|---|
| October 29, 2021 | Azure Service Fabric 8.2 | Release notes |
| December 16, 2021 | Azure Service Fabric 8.2 First Refresh Release | Release notes |
| February 12, 2022 | Azure Service Fabric 8.2 Second Refresh Release | Release notes |
| June 06, 2022 | Azure Service Fabric 8.2 Third Refresh Release | Release notes |
| July 14, 2022 | Azure Service Fabric 8.2 Fourth Refresh Release | Release notes |
| October 11, 2022 | Azure Service Fabric 8.2 Sixth Refresh Release | Release notes |
| October 24, 2022 | Azure Service Fabric 8.2 Seventh Refresh Release | Release notes |
| March 1, 2023 | Azure Service Fabric 8.2 Ninth Refresh Release | Release notes |
Service Fabric 8.1
We're excited to announce that 8.1 release of the Service Fabric runtime started rollout to the various Azure regions along with tooling and SDK updates. The updates for .NET SDK, Java SDK, and Service Fabric runtime are available through Web Platform Installer, NuGet packages, and Maven repositories.
Key announcements
- Added support for Auxiliary Replica
- Preview Added support for .NET 6.0 Service Fabric applications
- Added API support for updating application descriptions
- Added periodic ping between Reconfiguration Agent (RA) and Reconfiguration Agent Proxy (RAP) to detect IPC failure and process stuck
- Added support for liveness and readiness probes for non containerized applications
- Made cluster upgrade for node capacity updates impactless
Service Fabric 8.1 releases
| Release date | Release | More info |
|---|---|---|
| July 28, 2021 | Azure Service Fabric 8.1 | Release notes |
| August 13, 2021 | Azure Service Fabric 8.1 First Refresh Release | Release notes |
| September 09, 2021 | Azure Service Fabric 8.1 Second Refresh Release | Release notes |
| October 06 2021 | Azure Service Fabric 8.1 Third Refresh Release | Release notes |
Service Fabric 8.0
We're excited to announce the roll out of the 8.0 release of the Service Fabric runtime to the various Azure regions along with tooling and SDK updates. The updates for .NET SDK, Java SDK, and Service Fabric runtime are available through Web Platform Installer, NuGet packages, and Maven repositories.
Key announcements
- General Availability of support for .NET 5 for Windows
- General Availability of Stateless NodeTypes
- Ability to move stateless service instances
- Ability to add parameterized DefaultLoad in the application manifest
- For singleton replica upgrades - ability to have some of the cluster level settings to be defined at an application level
- Ability for smart placement based on node tags
- Ability to define percentage threshold of unhealthy nodes that influence cluster health
- Ability to query top loaded services
- Ability to add a new interval for new error codes
- Capability to mark service instance as completed
- Support for wave-based deployment model for automatic upgrades
- Added readiness probe for containerized applications
- Enable UseSeparateSecondaryMoveCost to true by default
- Fixed StateManager to release the reference as soon as safe to release
- Block Central Secret Service removal while storing user secrets
Service Fabric 8.0 releases
| Release date | Release | More info |
|---|---|---|
| April 08, 2021 | Azure Service Fabric 8.0 | Release notes |
| May 17, 2021 | Azure Service Fabric 8.0 First Refresh Release | Release notes |
| June 17, 2021 | Azure Service Fabric 8.0 Second Refresh Release | Release notes |
| July 28, 2021 | Azure Service Fabric 8.0 Third Refresh Release | Release notes |
Previous versions
Service Fabric 7.2
Key announcements
- Preview: Service Fabric managed clusters are now in public preview. Service Fabric managed clusters aim to simplify cluster deployment and management by encapsulating the underlying resources that make up a Service Fabric cluster into a single ARM resource. For more information see, Service Fabric managed cluster overview.
- Preview: Supporting stateless services with a number of instances greater than the number of nodes is now in public preview. A placement policy enables the creation of multiple stateless instances of a partition on a node.
- FabricObserver (FO) 3.0 is now available.
- You can now run FabricObserver in Linux and Windows clusters.
- You can now build custom observer plugins. See plugins readme and the sample plugin project for details and code.
- You can now change any observer setting via application parameters upgrade. This means you no longer need to redeploy FO to modify specific observer settings. See the sample.
- Support for Ubuntu 18.04 OneBox container images.
- Preview: KeyVault Reference for Service Fabric applications supports ONLY versioned secrets. Secrets without versions are not supported.
- SF SDK requires the latest VS 2019 update 16.7.6 or 16.8 Preview 4 to be able create new .NET Framework stateless/stateful/actors projects. If you don't have the latest VS update, after creating the service project, use package manager to install Microsoft.ServiceFabric.Services (version 4.2.x) for stateful/stateless projects and Microsoft.ServiceFabric.Actors (version 4.2.x) for actor projects from nuget.org.
- RunToCompletion: Service Fabric supports concept of run to completion for guest executables. With this update once the replica runs to completion, the cluster resources allocated to this replica will be released.
- Resource governance support has been enhanced: allowing requests and limits specifications for cpu and memory resources.
Service Fabric 7.2 releases
| Release date | Release | More info |
|---|---|---|
| October 21, 2020 | Azure Service Fabric 7.2 | Release notes |
| November 9, 2020 | Azure Service Fabric 7.2 Second Refresh Release | Release notes |
| November 10, 2020 | Azure Service Fabric 7.2 Third Refresh Release | Release notes |
| December 2, 2020 | Azure Service Fabric 7.2 Fourth Refresh Release | Release notes |
| January 25, 2021 | Azure Service Fabric 7.2 Fifth Refresh Release | Release notes |
| February 17, 2021 | Azure Service Fabric 7.2 Sixth Refresh Release | Release notes |
| March 10, 2021 | Azure Service Fabric 7.2 Seventh Refresh Release | Release notes |
Service Fabric 7.1
Due to the current COVID-19 crisis, and taking into consideration the challenges faced by our customers, we're making 7.1 available, but won't automatically upgrade clusters set to receive automatic upgrades. We're pausing automatic upgrades until further notice to ensure that customers can apply upgrades when most appropriate for them, to avoid unexpected disruptions.
You're able to update to 7.1 via through the Azure portal or via an Azure Resource Manager deployment.
Service Fabric clusters with automatic upgrades enabled will begin to receive the 7.1 update automatically once we resume the standard rollout procedure. We provide another announcement before the standard rollout begins on the Service Fabric Tech Community Site. We also have published updates to end of support date for major releases starting from 6.5 up to 7.1 here.
Key announcements
- General Availability of Service Fabric Managed Identities for Service Fabric applications
- Support for Ubuntu 18.04
- Preview: Virtual machine scale set Ephemeral OS disk support**: Ephemeral OS disks are storage created on the local virtual machine, and not saved to remote Azure Storage. They're recommended for all Service Fabric node types (Primary and Secondary), because compared to traditional persistent OS disks, ephemeral OS disks:
- Reduce read/write latency to OS disk
- Enable faster reset/re-image node management operations
- Reduce overall costs (the disks are free and incur no extra storage cost)
- Support for declaration of Service Endpoint certificates of Service Fabric applications by subject common name.
- Support for Health Probes for containerized services: Support for Liveness Probe mechanism for containerized applications. Liveness Probe help announce the liveness of the containerized application and when they don't respond in a timely fashion, it results in a restart.
- Support for Initializer Code Packages for containers and guest executable applications. This allows executing Code Packages (for example, containers), in a specified order, to perform Service Package initialization.
- FabricObserver and ClusterObserver are stateless applications that capture Service Fabric Telemetry related to different aspects of an SF cluster. Both these applications are ready for deployment to Windows production clusters to capture rich telemetry with implemented support for ApplicationInsights, EventSource and LogAnalytics.
- FabricObserver (FO) 2.0- runs on all nodes, generates health events, emits telemetry when user configured resource usage thresholds are reached. This release contains several enhancements across monitoring, data management, health event details, structured telemetry.
- ClusterObserver (CO) 1.1 - runs on one node, captures cluster level health telemetry. In this release, ClusterObserver also monitors node status and emits telemetry when node is down/disabling/disabled for longer than user-specified time period.
Improve application life cycle experience
- Preview:Request drain: During planned service maintenance, such as service upgrades or node deactivation, you would like to allow the services to gracefully drain connections. This feature adds an instance close delay duration in the service configuration. During planned operations, SF removes the Service's address from discovery and then waits this duration before shutting down the service.
- Automatic Subcluster Detection and Balancing: Subclustering happens when services with different placement constraints have a common load metric. If the load on the different sets of nodes differs significantly, the Service Fabric Cluster Resource Manager believes that the cluster is imbalanced, even when it has the best possible balance because of the placement constraints. As a result, it attempts to rebalance the cluster, potentially causing unnecessary service movements (since the "imbalance" can't be substantially improved). The Cluster Resource Manager will now attempt to automatically detect these sorts of configurations and understand when the imbalance can be fixed through movement, and when instead it should leave things alone since no substantial improvement can be made.
- Different Move cost for secondary replicas: We have introduced new move cost value VeryHigh that provides more flexibility in some scenarios to define if a separate move cost should be used for secondary replicas.
- Enabled Liveness Probe mechanism for containerized applications. Liveness Probe help announce the liveness of the containerized application and when they don't respond in a timely fashion, it results in a restart.
- Run to completion/once for services**
Image Store improvements
- Service Fabric 7.1 uses custom transport to secure file transfer between nodes by default. The dependency on SMB file share is removed from the version 7.1. The secured SMB file shares still exist on nodes that contain Image Store Service replica for customer's choice to opt out from default and for upgrade and downgrade to old version.
Reliable Collections improvements
- In memory only store support for stateful services using Reliable Collections: Volatile Reliable Collections allows data to be persisted to disk for durability against large-scale outages, can be used for workloads like replicated cache, for example, where occasional data loss can be tolerated. Based on the limitations and restrictions of Volatile Reliable Collections, we recommend this for workloads that don't need persistence, for services that handle the rare occasions of Quorum Loss.
- Preview: Service Fabric Backup Explorer: To ease management of Reliable Collections backups for Service Fabric Stateful applications, Service Fabric Backup Explorer enables users to
- Audit and review the contents of the Reliable Collections,
- Update current state to a consistent view
- Create Backup of the current snapshot of the Reliable Collections
- Fix data corruption
Service Fabric 7.1 releases
| Release date | Release | More info |
|---|---|---|
| April 20, 2020 | Azure Service Fabric 7.1 | Release notes |
| June 16, 2020 | Azure Service Fabric 7.1 First Refresh | Release notes |
| July 20, 2020 | Azure Service Fabric 7.1 Second Refresh | Release notes |
| August 12, 2020 | Azure Service Fabric 7.1 Third Refresh | Release notes |
| September 10, 2020 | Azure Service Fabric 7.1 Fourth Refresh | Release notes |
| October 7, 2020 | Azure Service Fabric 7.1 Sixth Refresh | Release notes |
| November 23, 2020 | Azure Service Fabric 7.1 Eighth Refresh | Release notes |
Service Fabric 7.0
Azure Service Fabric 7.0 is now available! You are able to update to 7.0 through the Azure portal or via an Azure Resource Manager deployment. Due to customer feedback on releases around the holiday period we will not begin automatically updating clusters set to receive automatic upgrades until January. In January, we resume the standard roll-out procedure and clusters with automatic upgrades enabled will begin to receive the 7.0 update automatically. We provide another announcement before the roll-out begins. We also update our planned release dates to indicate that we take this policy into consideration. Look here for updates on our future release schedules.
Key announcements
KeyVaultReference support for application secrets: Service Fabric applications that have enabled Managed Identities can now directly reference a Key Vault secret URL as an environment variable, application parameter, or container repository credential. Service Fabric will automatically resolve the secret using the application's managed identity.
Improved upgrade safety for stateless services: To guarantee availability during an application upgrade, we have introduced new configurations to define the minimum number of instances for stateless services to be considered available. Previously this value was 1 for all services and wasn't changeable. With this new per-service safety check, you can ensure that your services retain a minimum number of up instances during application upgrades, cluster upgrades, and other maintenance that relies on Service Fabric's health and safety checks.
Resource Limits for User Services: Users can set up resource limits for the user services on a node to prevent scenarios such as resource exhaustion of the Service Fabric system services.
Very High service move cost for a replica type. Replicas with Very High move cost will be moved only if there's a constraint violation in the cluster that can't be fixed in any other way. Refer to the linked document for additional information on when usage of a "Very High" move cost is reasonable and for more considerations.
Additional cluster safety checks: In this release, we introduced a configurable seed node quorum safety check. This allows you to customize how many seed nodes must be available during cluster life-cycle and management scenarios. Operations that would take the cluster below the configured value are blocked. Today the default value is always a quorum of the seed nodes, for example, if you have seven seed nodes, an operation that would take you below five seed nodes would be blocked by default. With this change, you could make the minimum safe value 6, which would allow only one seed node to be down at a time.
Added support for managing the Backup and Restore service in Service Fabric Explorer. This makes the following activities possible directly from within SFX: discovering the backup and restore service, creating backup policy, enabling automatic backups, taking adhoc backups, triggering restore operations and browsing existing backups.
Announcing availability of the ReliableCollectionsMissingTypesTool: This tool helps validate that types used in reliable collections are forward and backward compatible during a rolling application upgrade. This helps prevent upgrade failures or data loss and data corruption due to missing or incompatible types.
Enable stable reads on secondary replicas: Stable reads restrict secondary replicas to returning values, which are quorum-acked.
In addition, this release contains other new features, bug fixes, and supportability, reliability, and performance improvements. For the full list of changes, refer to the release notes.
Service Fabric 7.0 releases
| Release date | Release | More info |
|---|---|---|
| November 18, 2019 | Azure Service Fabric 7.0 | Release notes |
| January 30, 2020 | Azure Service Fabric 7.0 Refresh Release | Release notes |
| February 6, 2020 | Azure Service Fabric 7.0 Refresh Release | Release notes |
| March 2, 2020 | Azure Service Fabric 7.0 Refresh Release | Release notes |
| May 6, 2020 | Azure Service Fabric 7.0 Sixth Refresh Release | Release notes |
| October 9, 2020 | Azure Service Fabric 7.0 Ninth Refresh Release | Release notes |
Service Fabric 6.5
This release includes supportability, reliability, and performance improvements, new features, bug fixes, and enhancements to ease cluster and application lifecycle management.
Important
Service Fabric 6.5 is the final release with Service Fabric tools support in Visual Studio 2015. Customers are advised to move to Visual Studio 2019 going forward.
What's new in Service Fabric 6.5:
Service Fabric Explorer includes an Image Store Viewer for inspecting applications you upload to image store.
Patch Orchestration Application (POA) version 1.4.0 includes many self-diagnostic improvements. Customers of POA are recommended to move to this version.
EventStore Service is enabled by default for Service Fabric 6.5 clusters unless you opt out.
Added replica lifecycle events for stateful services.
Better visibility of seed node status, including cluster-level warnings if a seed node is unhealthy (Down, Removed or Unknown).
Service Fabric Application Disaster Recovery Tool allows Service Fabric stateful services to recover quickly when the primary cluster encounters a disaster. Data from primary cluster is continuously synchronized on the secondary standby application using periodic backup and restore.
Visual Studio support for publishing .NET Core apps to Linux-based clusters.
Azure Service Fabric CLI (SFCTL) installs automatically for Service Fabric 6.5 (and later versions) when you upgrade or create a new Linux cluster on Azure.
SFCTL is installed by default on MacOS/Linux OneBox clusters.
For more information, see the Service Fabric 6.5 Release Notes.
Service Fabric 6.5 releases
| Release date | Release | More info |
|---|---|---|
| June 11, 2019 | Azure Service Fabric 6.5 | Release notes |
| July 2, 2019 | Azure Service Fabric 6.5 Refresh Release | Release notes |
| July 29, 2019 | Azure Service Fabric 6.5 Refresh Release | Release notes |
| Aug 23, 2019 | Azure Service Fabric 6.5 Refresh Release | Release notes |
| Oct 14, 2019 | Azure Service Fabric 6.5 Refresh Release | Release notes |