12 KiB
Microsoft Azure Service Fabric 8.2 Release Notes
This release includes the bug fixes and features described in this document. This release includes runtime, SDKs, and Windows Server Standalone deployments to run on-premises.
The following packages and versions are part of this release:
| Service | Platform | Version |
|---|---|---|
| Service Fabric Runtime | Ubuntu 18 Windows |
8.2.1124.1 8.2.1235.9590 |
| Service Fabric for Windows Server | Service Fabric Standalone Installer Package | 8.2.1235.9590 |
| .NET SDK | Windows .NET SDK Microsoft.ServiceFabric Reliable Services and Reliable Actors ASP.NET Core Service Fabric integration |
5.2.1235 8.2.1235 5.2.1235 5.2.1235 |
| Java SDK | Java for Linux SDK | 1.0.6 |
| Service Fabric PowerShell and CLI | AzureRM PowerShell Module SFCTL |
0.3.15 11.1.0 |
Contents
Microsoft Azure Service Fabric 8.2 Release Notes
- Key Announcements
- Current And Upcoming Breaking Changes
- Service Fabric Runtime
- Service Fabric Common Bug Fixes
- Repositories and Download Links
Key Announcements
- Expose an API in Cluster Manager to note if upgrade is impactful
Current Breaking Changes
- Guest Executable and Container Applications: Guest executable and container applications created or upgraded in Service Fabric clusters with runtime versions 7.1+ are incompatible with prior Service Fabric runtime versions (e.g. Service Fabric 7.0).
Following scenarios are impacted:
- An application with guest executables or containers is created or upgraded in an Service Fabric 7.1+ cluster.
The cluster is then downgraded to a previous Service Fabric runtime version (e.g. Service Fabric 7.0).
The application fails to activate. - A cluster upgrade from pre-SF 7.1 version to Service Fabric 7.1+ version is in progress.
In parallel with the Service Fabric runtime upgrade, an application with guest executables or containers is created or upgraded.
The Service Fabric runtime upgrade starts rolling back (due to any reason) to the pre-SF 7.1 version.
The application fails to activate.
To avoid issues when upgrading from a pre-SF 7.1 runtime version to an Service Fabric 7.1+ runtime version, do not create or upgrade applications with guest executables or containers while the Service Fabric runtime upgrade is in progress. - The simplest mitigation, when possible, is to delete and recreate the application in Service Fabric 7.0.
- The other option is to upgrade the application in Service Fabric 7.0 (for example, with a version only change).
If the application is stuck in rollback, the rollback has to be first completed before the application can be upgraded again.
- An application with guest executables or containers is created or upgraded in an Service Fabric 7.1+ cluster.
- .NET Core 2.x Support: .NET Core runtime LTS 2.1 runtime is out of support as of Aug 21, 2021, and .NET Core runtime 2.2 is out of support from Dec 2019. Service Fabric releases after those dates will drop support for Service Fabric apps running with .NET Core 2.1 & .NET Core 2.2 runtimes respectively. Current apps running on .NET Core 2.x runtime will continue to work, but requests for investigations or request for changes will no longer receive support. Service Fabric .NET SDK will take a dependency on .NET runtime 3.x features to support Service Fabric .NET Core apps.
- Ubuntu 16.04 Support: Ubuntu 16.04 LTS reached it's 5-year end-of-life window on April 30, 2021. Due to this, Service Fabric runtime has dropped support for 16.04 LTS and we recommend moving your clusters and applications to Ubuntu 18.04 LTS. Current applications running on it will continue to work, but requests for investigations or requests for change will no longer receive support.
- ASP.NET Core 1.0 Support: Service Fabric ASP.NET Core packages are built against ASP.NET Core 1.0 binaries which are out of support. Starting Service Fabric 8.2, we will be building Service Fabric ASP.NET Core packages against .NET Core 3.1, .NET Core 5.0, .NET Core 6.0, .NET Framework 4.6.1. As a result, they can be used only to build services targeting .NET Core 3.1, .NET Core 5.0, .NET Core 6.0, >=.NET Framework 4.6.1 respectively.
For .NET Core 3.1, .NET Core 5.0, .NET Core 6.0, Service Fabric ASP.NET Core will be taking dependency on Microsoft.AspNetCore.App shared framework, whereas for NetFx target frameworks >=.NET Framework 4.6.1, Service Fabric ASP.NET Core will be taking dependency on ASP.NET Core 2.1 packages.
The package Microsoft.ServiceFabric.AspNetCore.WebListener will no longer be shipped, Microsoft.ServiceFabric.AspNetCore.HttpSys package should be used instead.
Service Fabric Runtime
| Versions | IssueType | Description | Resolution |
|---|---|---|---|
| Windows - 8.2.1235.9590 Ubuntu 18 - 8.2.1124.1 |
Feature | Expose an API in Cluster Manager to note if upgrade is impactful | Brief Description: Added a new ValidateFabricUpgrade API, which validates the parameters of a Fabric Cluster upgrade request and returns the expected service host impact. Impact is assessed based on whether the upgrade is expected to cause Service Fabric's service host to restart when applied to a node, which leads to all services on the node to restart as well. |
| Windows - 8.2.1235.9590 Ubuntu 18 - 8.2.1124.1 |
Feature | New Sfx by Default | Brief Description: The option to return to the old SFX application has been moved to the advanced option's dropdown. The old SFX application is not recommended to be used due to security concerns and will be removed in a later version entirely. |
Service Fabric Add-ons Applications
Introducing FabricHealer (Preview) - Auto-Mitigation in Service Fabric Clusters
FabricHealer is a Service Fabric application that attempts to automatically fix a set of reliably solvable problems that can take place in Service Fabric application services, including containers, host virtual machines, and logical disks (scoped to space usage problems only). These repairs mostly employ a set of Service Fabric API calls, but can also be fully customizable (like Disk repair). All repairs are safely orchestrated through Service Fabric’s RepairManager service. Repair configuration is written as Prolog-like logic with supporting external predicates written in C#. This is made possible by a new logic programming library for .NET, Guan. The fun starts when FabricHealer detects supported error or warning states reported by FabricObserver. FabricHealer requires FabricObserver to be running in the same cluster.
We are especially interested in Feedback with respect to the new Configuration-as-Logic feature. Out of the box, FabricHealer is configured to solve several problems automatically. You do not have to be a logic programmer to use FabricHealer right away. Check out the scenario-based getting started samples to get going quickly. There are several logic rules supplied by default that span service to VM level auto-mitigation. You just need to change arguments in the rules to match your needs.
We are also very interested in your feedback with respect to Guan, should you want to dig into its design and implementation and/or use it in other .NET projects. The way FabricHealer employs Guan is just one use case. As a general purpose logic programming library (.NET Standard), Guan can be used to solve any number of logic programming problems for .NET developers.
Please experiment with FabricHealer Preview in your Test clusters and let us know how it goes. Please create issues on the FabricHealer repo. Thank you!
Repositories and Download Links
The table below is an overview of the direct links to the packages associated with this release. Follow this guidance for setting up your developer environment: