This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Azure Service Fabric 7.2 is now available!
We're excited to announce that 7.2 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 will be available through Web Platform Installer, NuGet packages and Maven repositories in 7-10 days within all regions.
What is new in Service Fabric 7.2?
This release is loaded with key features and improvements. Some of the key features are highlighted below:
- 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 details 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. Please 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. Please 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 do not 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 the 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 limit specifications for CPU and memory resources.
- Service Fabric 7.2 and higher runtime drops support for .Net core Service Fabric apps running with .Net core 2.2 runtime. .Net core runtime 2.2 is out of support from Dec 2019. Service Fabric runtime will not install .Net core runtime 2.2 as part of its dependency. Customers should upgrade their .Net 2.2 runtime SF apps to the next .Net core LTS version 3.1.
- .Net core runtime LTS 2.1 runtime will go out of support from Aug 21, 2021. Service Fabric releases after that date will drop support for Service Fabric apps running with .Net core 2.1 runtime. Service Fabric .Net SDK will take a dependency on .Net runtime 3.* features to support Service Fabric .Net core apps. This has no impact on Service Fabric .Net Framework SDK.
- We will be deprecating the latest tag for OneBox container images. The new scheme for containers will substitute the current naming scheme ‘latest’ to be replaced with an OS-targeted latest set to explicitly identify the base OS for latest SF releases:
- The default action of deleting uploaded application package is changed. If the application package is registered successfully, the uploaded application package is deleted by default. Before this default action changes, the uploaded application package was deleted either by calling to Remove-ServiceFabricApplicationPackage or by using ApplicationPackageCleanupPolicy parameter explicitly with Register-ServiceFabricApplicationType
- Service Fabric 7.2 will become the baseline release for future development of image validation. When the feature is activated in future version e.g., Service Fabric 7.3, the cluster is not desired to rolled back down to 7.1 or lower. The version 7.2 is the baseline to which the cluster can downgrade.