Home
%3CLINGO-SUB%20id%3D%22lingo-sub-1018522%22%20slang%3D%22en-US%22%3ERe%3A%20Service%20Fabric%207.0%20Release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1018522%22%20slang%3D%22en-US%22%3E%3CP%3EIn%20terms%20of%20upcoming%20and%20ongoing%20work%3A%20does%20the%20mention%20of%20%22%3CSPAN%3ESupport%20for%20Ubuntu%2018.04%22%20imply%20standalone%20deployment%20tooling%20for%20Linux%20clusters%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1015482%22%20slang%3D%22en-US%22%3EService%20Fabric%207.0%20Release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1015482%22%20slang%3D%22en-US%22%3E%3CP%3EAzure%20Service%20Fabric%207.0%20is%20now%20available!%20You%20will%20be%20able%20to%20update%20to%207.0%20through%20the%20Azure%20Portal%20or%20via%20an%20Azure%20Resource%20Manager%20deployment.%20Due%20to%20customer%20feedback%20on%20releases%20around%20the%20holiday%20period%20we%20will%20not%20begin%20automatically%20updating%20clusters%20set%20to%20receive%20automatic%20upgrades.%3C%2FP%3E%0A%3CP%3EIn%20January%2C%20we%20will%20resume%20the%20standard%20roll-out%20procedure%20and%20clusters%20with%20automatic%20upgrades%20enabled%20will%20begin%20to%20receive%20the%207.0%20update%20automatically.%20We%20will%20provide%20another%20announcement%20before%20the%20roll-out%20begins.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%20We%20will%20also%20update%20our%20planned%20release%20dates%20to%20indicate%20that%20we%20take%20this%20policy%20into%20consideration.%20Looks%20for%20updates%20to%20release%20roadmap%20%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fservice-fabric%23service-fabric-release-schedule%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehere%3C%2FA%3E.%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId--1444017253%22%20id%3D%22toc-hId--1444017253%22%20id%3D%22toc-hId--1444017253%22%20id%3D%22toc-hId--1444017253%22%20id%3D%22toc-hId--1444017253%22%20id%3D%22toc-hId--1444017253%22%20id%3D%22toc-hId--1444017253%22%20id%3D%22toc-hId--1444017253%22%20id%3D%22toc-hId--1444017253%22%20id%3D%22toc-hId--1444017253%22%20id%3D%22toc-hId--1444017253%22%20id%3D%22toc-hId--1444017253%22%3E%26nbsp%3B%3C%2FH2%3E%0A%3CH2%20id%3D%22toc-hId-1043495580%22%20id%3D%22toc-hId-1043495580%22%20id%3D%22toc-hId-1043495580%22%20id%3D%22toc-hId-1043495580%22%20id%3D%22toc-hId-1043495580%22%20id%3D%22toc-hId-1043495580%22%20id%3D%22toc-hId-1043495580%22%20id%3D%22toc-hId-1043495580%22%20id%3D%22toc-hId-1043495580%22%20id%3D%22toc-hId-1043495580%22%20id%3D%22toc-hId-1043495580%22%20id%3D%22toc-hId-1043495580%22%3E%3CFONT%20size%3D%226%22%3E%3CSTRONG%3EWhat%20is%20new%20in%20Service%20Fabric%207.0%3F%3C%2FSTRONG%3E%3C%2FFONT%3E%3C%2FH2%3E%0A%3CP%3E%26nbsp%3B%20We%20are%20excited%20to%20announce%20that%20the%20next%20release%20of%20Service%20Fabric%20is%20loaded%20with%20key%20features%20and%26nbsp%3B%20%26nbsp%3Bimprovements.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId--763958883%22%20id%3D%22toc-hId--763958883%22%20id%3D%22toc-hId--763958883%22%20id%3D%22toc-hId--763958883%22%20id%3D%22toc-hId--763958883%22%20id%3D%22toc-hId--763958883%22%20id%3D%22toc-hId--763958883%22%20id%3D%22toc-hId--763958883%22%20id%3D%22toc-hId--763958883%22%20id%3D%22toc-hId--763958883%22%20id%3D%22toc-hId--763958883%22%20id%3D%22toc-hId--763958883%22%3E%3CSTRONG%3EKey%20Announcements%3C%2FSTRONG%3E%3C%2FH2%3E%0A%3CUL%3E%0A%3CLI%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fazure%2Fservice-fabric%2Fservice-fabric-keyvault-references%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EKeyVaultReference%20support%20for%20application%20secrets%3C%2FA%3E%20(Preview)%3A%20Service%20Fabric%20applications%20that%20have%20enabled%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fservice-fabric%2Fconcepts-managed-identity%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EManaged%20Identities%3C%2FA%3E%20can%20now%20directly%20reference%20a%20Key%20Vault%20secret%20URL%20as%20an%20environment%20variable%2C%20application%20parameter%2C%20or%20container%20repository%20credential.%20Service%20Fabric%20will%20automatically%20resolve%20the%20secret%20using%20the%20application's%20managed%20identity.%26nbsp%3B%3C%2FLI%3E%0A%3CLI%3EImproved%20upgrade%20safety%20for%20stateless%20services%3A%20To%20guarantee%20availability%20during%20an%20application%20upgrade%2C%20we%20have%20introduced%20new%20configurations%20to%20define%20the%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdotnet%2Fapi%2Fsystem.fabric.description.statelessservicedescription%3Fview%3Dazure-dotnet%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Eminimum%20number%20of%20instances%20for%20stateless%20services%3C%2FA%3E%20to%20be%20considered%20available.%20Previously%20this%20value%20was%201%20for%20all%20services%20and%20was%20not%20changeable.%20With%20this%20new%20per-service%20safety%20check%2C%20you%20can%20ensure%20that%20your%20services%20retain%20a%20minimum%20number%20of%20up%20instances%20during%20application%20upgrades%2C%20cluster%20upgrades%2C%20and%20other%20maintenance%20that%20relies%20on%20Service%20Fabric%E2%80%99s%20health%20and%20safety%20checks.%3C%2FLI%3E%0A%3CLI%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fazure%2Fservice-fabric%2Fservice-fabric-resource-governance%23enforcing-the-resource-limits-for-user-services%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EResource%20Limits%20for%20User%20Services%3C%2FA%3E%3A%20Users%20can%20set%26nbsp%3Bup%26nbsp%3Bresource%26nbsp%3Blimits%20for%20the%20user%20services%26nbsp%3Bon%20a%20node%20to%20prevent%20scenarios%20such%20as%20resource%20exhaustion%20of%20the%20Service%20Fabric%20system%20services.%26nbsp%3B%3C%2FLI%3E%0A%3CLI%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fservice-fabric%2Fservice-fabric-cluster-resource-manager-movement-cost%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EVery%20High%20service%20move%20cost%3C%2FA%3E%20for%20a%20replica%20type.%20Replicas%20with%26nbsp%3BVery%20High%26nbsp%3Bmove%20cost%20will%20be%20moved%20only%20if%20there%20is%20a%20constraint%20violation%20in%20the%20cluster%20that%26nbsp%3Bcannot%20be%20fixed%20in%20any%20other%20way%20.Please%20see%20the%20docs%20for%20additional%20information%20on%20when%20usage%20of%20a%20%E2%80%9CVery%20High%E2%80%9D%20move%20cost%20is%20reasonable%20and%20for%20additional%20considerations.%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E%3CSTRONG%3EAdditional%20cluster%20safety%20checks%3C%2FSTRONG%3E%3C%2FSPAN%3E%3CSPAN%3E%3A%20In%20this%20release%20we%20introduced%20a%20c%3C%2FSPAN%3E%3CSPAN%3Eonfigurable%20seed%20node%20quorum%20safety%20check.%20This%20allows%20you%20%3C%2FSPAN%3Eto%20customize%20how%20many%20seed%20nodes%20must%20be%20available%20during%20cluster%20life-cycle%20and%20management%20scenarios.%20Operations%20which%20would%20take%20the%20cluster%20below%20the%20configured%20value%20are%20blocked.%20Today%20the%20default%20value%20is%20always%20a%20quorum%20of%20the%20seed%20nodes%2C%20for%20example%2C%20if%20you%20have%207%20seed%20nodes%2C%20an%20operation%20that%20would%20take%20you%20below%205%20seed%20nodes%20would%20be%20blocked%20by%20default.%20With%20this%20change%2C%20you%20could%20make%20the%20minimum%20safe%20value%206%2C%20which%20would%20allow%20only%20one%20seed%20node%20to%20be%20down%20at%20a%20time.%3C%2FLI%3E%0A%3CLI%3EAdded%20support%20for%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fazure%2Fservice-fabric%2Fservice-fabric-backuprestoreservice-quickstart-azurecluster%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Emanaging%20the%20Backup%20and%20Restore%20service%20in%20Service%20Fabric%20Explorer%3C%2FA%3E.%20This%20makes%20the%20following%20activities%20possible%20directly%20from%20within%20SFX%3A%3CUL%3E%0A%3CLI%3Ediscovering%20the%20backup%20and%20restore%20service%3C%2FLI%3E%0A%3CLI%3Ecreating%20backup%20policies%3C%2FLI%3E%0A%3CLI%3Eenabling%20automatic%20backups%3C%2FLI%3E%0A%3CLI%3Etaking%20adhoc%20backups%3C%2FLI%3E%0A%3CLI%3Etriggering%20restore%20operations%3C%2FLI%3E%0A%3CLI%3Ebrowsing%20existing%20backups%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FLI%3E%0A%3CLI%3EAnnouncing%20availability%20of%20the%20%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2Fhiadusum%2FReliableCollectionsMissingTypesTool%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EReliableCollectionsMissingTypesTool%3C%2FA%3E%3CSPAN%3E%3A%3C%2FSPAN%3E%20This%20tool%20helps%20validate%20that%20types%20used%20in%20reliable%20collections%20are%20forward%20and%20backward%20compatible%20during%20a%20rolling%20application%20upgrade.%20This%20helps%20prevent%20upgrade%20failures%20or%20data%20loss%20and%20data%20corruption%20due%20to%20missing%20or%20incompatible%20types.%3C%2FLI%3E%0A%3CLI%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fazure%2Fservice-fabric%2Fservice-fabric-reliable-services-configuration%23configuration-names-1%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EEnable%20stable%20reads%20on%20secondary%20replicas%3A%3C%2FA%3E%26nbsp%3BStable%20reads%20will%20restrict%20secondary%20replicas%20to%20returning%20values%20which%20have%20been%20quorum-acked.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3EIn%20addition%2C%20this%20release%20contains%20other%20new%20features%2C%20bug%20fixes%2C%20and%20supportability%2C%20reliability%2C%20and%20performance%20improvements.%20For%20the%20full%20list%20of%20changes%2C%20please%20refer%20to%20the%20%3CA%20title%3D%22release%20notes%22%20href%3D%22https%3A%2F%2Fgithub.com%2FAzure%2Fservice-fabric%2Fblob%2Fmaster%2Frelease_notes%2FService_Fabric_ReleaseNotes_70.md%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Erelease%20notes.%3C%2FA%3E%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-1723553950%22%20id%3D%22toc-hId-1723553950%22%20id%3D%22toc-hId-1723553950%22%20id%3D%22toc-hId-1723553950%22%20id%3D%22toc-hId-1723553950%22%20id%3D%22toc-hId-1723553950%22%20id%3D%22toc-hId-1723553950%22%20id%3D%22toc-hId-1723553950%22%20id%3D%22toc-hId-1723553950%22%20id%3D%22toc-hId-1723553950%22%20id%3D%22toc-hId-1723553950%22%20id%3D%22toc-hId-1723553950%22%3E%26nbsp%3B%3C%2FH2%3E%0A%3CH2%20id%3D%22toc-hId--83900513%22%20id%3D%22toc-hId--83900513%22%20id%3D%22toc-hId--83900513%22%20id%3D%22toc-hId--83900513%22%20id%3D%22toc-hId--83900513%22%20id%3D%22toc-hId--83900513%22%20id%3D%22toc-hId--83900513%22%20id%3D%22toc-hId--83900513%22%20id%3D%22toc-hId--83900513%22%20id%3D%22toc-hId--83900513%22%20id%3D%22toc-hId--83900513%22%20id%3D%22toc-hId--83900513%22%3E%3CSTRONG%3ECurrent%20And%20Upcoming%20Breaking%20Change%20Announcements%20%3C%2FSTRONG%3E%3C%2FH2%3E%0A%3CUL%3E%0A%3CLI%3E%3CSPAN%3EStarting%20with%20Service%20Fabric%20version%207.0%2C%20w%3C%2FSPAN%3Ee%20have%20changed%20the%20default%20value%20for%20the%20PreferUpgradedUDs%20config%20flag%20to%20FALSE%20in%20the%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fservice-fabric%2Fservice-fabric-cluster-fabric-settings%23placementandloadbalancing%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EPlacementAndLoadBalancing%20section%20of%20the%20ClusterManifest%3C%2FA%3E.%20Based%20on%20numerous%20cases%20and%20customer%20issues%2C%20this%20default%20behavior%20should%20allow%20clusters%20to%20remain%20more%20balanced%20during%20upgrades.%20If%20you%20want%20to%20preserve%20today%E2%80%99s%20behavior%20for%20your%20workload%2C%20please%20perform%20a%20cluster%20configuration%20upgrade%20to%20explicitly%20set%20the%20value%20to%20true%20either%20prior%20to%20or%20as%20a%20part%20of%20upgrading%20your%20cluster%20to%207.0.%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3EStarting%20with%20Service%20Fabric%20version%207.0%2C%20w%3C%2FSPAN%3Ee%20have%20fixed%20a%20calculation%20bug%20in%20the%20Cluster%20Resource%20Manager%20which%20impacts%20how%20node%20resource%20capacities%20are%20calculated%20in%20cases%20where%20a%20user%20manually%20provides%20the%20values%20for%20node%20resource%20capacities.%20The%20impact%20of%20this%20fix%20is%20that%20the%20Cluster%20Resource%20Manager%20will%20now%20consider%20there%20to%20be%20less%20usable%20capacity%20in%20the%20cluster.%20For%20more%20information%2C%20see%20resource%20governance.%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3EStarting%20with%20Service%20Fabric%20version%207.0%2C%3C%2FSPAN%3E%20customers%20using%26nbsp%3B%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fservice-fabric%2Fconcepts-managed-identity%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EService%20Fabric%20Managed%20Identities%3C%2FA%3E%2C%20please%20switch%20to%20new%20environment%20variables%20%E2%80%98IDENTITY_ENDPOINT%E2%80%99%20and%20%E2%80%98IDENTITY_HEADER%E2%80%99.%20The%20prior%20environment%20variables%20'MSI_ENDPOINT'%2C%20%E2%80%98MSI_ENDPOINT_%E2%80%99%20and%20'MSI_SECRET'%20are%20now%20deprecated%20in%20this%20release%20and%20will%20be%20removed%20in%207.0%20CU1.%3C%2FLI%3E%0A%3CLI%3EFor%20customers%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fservice-fabric%2Fservice-fabric-securing-containers%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Eusing%20service%20fabric%20to%20export%20certificates%20into%20their%20Linux%20containers%3C%2FA%3E%3C%2FSPAN%3E%2C%20the%20export%20mechanism%20will%20change%20in%20an%20upcoming%20CU.%20This%20change%20will%20encrypt%20the%20private%20key%20included%20in%20the%20.pem%20file%2C%20with%20the%20password%20being%20stored%20in%20an%20adjacent%20.key%20file.%3C%2FLI%3E%0A%3CLI%3EToday%20Service%20Fabric%20performs%20equality%20comparison%20for%20Boolean%20in%20placement%20constraints%20using%20a%20case-sensitive%20lexical%20comparison%20Starting%20in%20a%20subsequent%20release%2C%20we%20will%20be%20changing%20this%20comparison%20to%20be%20case-insensitive.%20This%20change%20will%20only%20apply%20to%20Boolean%20placement%20properties%2Fconstraints.%20Other%20string%20and%20numeric%20constraint%20values%20will%20continue%20to%20be%20treated%20as%20they%20are%20today%20(with%20case%20sensitive%20and%20numeric%20comparisons%2C%20respectively).%3C%2FLI%3E%0A%3CLI%3ECurrently%20Service%20Fabric%20ships%20the%20following%20nuget%20packages%20as%20a%20part%20of%20our%20ASP.Net%20Integration%20and%20support%3A%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CUL%3E%0A%3CLI%3EServiceFabric.AspNetCore.Abstractions%3C%2FLI%3E%0A%3CLI%3EServiceFabric.AspNetCore.Configuration%3C%2FLI%3E%0A%3CLI%3EServiceFabric.AspNetCore.Kestrel%3C%2FLI%3E%0A%3CLI%3EServiceFabric.AspNetCore.HttpSys%3C%2FLI%3E%0A%3CLI%3EServiceFabric.AspNetCore.WebListener%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3EThese%20packages%20are%20built%20against%20AspNetCore%201.0.0%20binaries%20which%20have%20gone%20out%20of%20support%20(%3CA%20href%3D%22https%3A%2F%2Fdotnet.microsoft.com%2Fplatform%2Fsupport%2Fpolicy%2Fdotnet-core%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdotnet.microsoft.com%2Fplatform%2Fsupport%2Fpolicy%2Fdotnet-core%3C%2FA%3E).%20Starting%20in%20Service%20Fabric%208.0%20we%20will%20start%20building%20Service%20Fabric%20AspNetCore%20integration%20against%20AspNetCore%202.1%20and%20for%20netstandard%202.0.%20As%20a%20result%2C%20there%20will%20be%20following%20changes%3A%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3EThe%20following%20binaries%20and%20their%20nuget%20packages%20will%20be%20released%20for%20netstandard%202.0%20only.%20These%20packages%20can%20be%20used%20in%20applications%20targeting%20.net%20framework%20%26lt%3B4.6.1%20and%20.net%20core%20%26gt%3B%3D2.0%3COL%3E%0A%3CLI%3EServiceFabric.AspNetCore.Abstractions%3C%2FLI%3E%0A%3CLI%3EServiceFabric.AspNetCore.Configuration%3C%2FLI%3E%0A%3CLI%3EServiceFabric.AspNetCore.Kestrel%3C%2FLI%3E%0A%3CLI%3EServiceFabric.AspNetCore.HttpSys%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3C%2FLI%3E%0A%3CLI%3EThe%20following%20package%20will%20no%20longer%20be%20shipped%3A%3COL%3E%0A%3CLI%3EServiceFabric.AspNetCore.WebListener%3A%3COL%3E%0A%3CLI%3EUse%20Microsoft.ServiceFabric.AspNetCore.HttpSys%20instead.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CH2%20id%3D%22toc-hId--1891354976%22%20id%3D%22toc-hId--1891354976%22%20id%3D%22toc-hId--1891354976%22%20id%3D%22toc-hId--1891354976%22%20id%3D%22toc-hId--1891354976%22%20id%3D%22toc-hId--1891354976%22%20id%3D%22toc-hId--1891354976%22%20id%3D%22toc-hId--1891354976%22%20id%3D%22toc-hId--1891354976%22%20id%3D%22toc-hId--1891354976%22%20id%3D%22toc-hId--1891354976%22%20id%3D%22toc-hId--1891354976%22%3E%26nbsp%3B%3C%2FH2%3E%0A%3CH2%20id%3D%22toc-hId-596157857%22%20id%3D%22toc-hId-596157857%22%20id%3D%22toc-hId-596157857%22%20id%3D%22toc-hId-596157857%22%20id%3D%22toc-hId-596157857%22%20id%3D%22toc-hId-596157857%22%20id%3D%22toc-hId-596157857%22%20id%3D%22toc-hId-596157857%22%20id%3D%22toc-hId-596157857%22%20id%3D%22toc-hId-596157857%22%20id%3D%22toc-hId-596157857%22%20id%3D%22toc-hId-596157857%22%3E%3CSTRONG%3EUpcoming%20and%20Ongoing%20Work%3C%2FSTRONG%3E%3C%2FH2%3E%0A%3CP%3EThere%20are%20some%20work%20items%20that%20are%20not%20a%20part%20of%20the%207.0%20release.%20We%20want%20to%20let%20you%20know%20that%20work%20on%20these%20items%20is%20still%20ongoing.%20At%20this%20point%20we%20plan%20for%20these%20work%20items%20to%20GA%20in%20upcoming%207.0%20CUs%2C%20or%20as%20separate%20packages%20available%20in%20the%20upcoming%20months.%20The%20specific%20delivery%20dates%20will%20be%20communicated%20as%20they%20get%20closer%20to%20GA.%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EGeneral%20Availability%20of%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fservice-fabric%2Fconcepts-managed-identity%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EService%20Fabric%20Managed%20Identities%3C%2FA%3E%20for%20SF%20apps%3C%2FLI%3E%0A%3CLI%3ESupport%20for%20using%20low%20priority%2FAzure%20Spot%20Virtual%20Machine%20Scale%20Sets%20in%20Service%20Fabric%20clusters%3C%2FLI%3E%0A%3CLI%3E%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fservice-fabric-observer%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EFabricObserver%3C%2FA%3E%20(FO)%20%E2%80%93%20A%20configurable%20and%20extensible%20watchdog%20service%20that%20runs%20as%20a%20Service%20Fabric%20application%3C%2FLI%3E%0A%3CLI%3ESupport%20for%20Ubuntu%2018.04%3C%2FLI%3E%0A%3CLI%3ECross%20Availability%20Zone%20Clusters%20%E2%80%93%20Support%20for%20using%20a%20single%20Cross-AZ%20Virtual%20Machine%20Scale%20Set.%20Today%E2%80%99s%20workloads%20require%20one%20scale%20set%20per%20AZ.%26nbsp%3B%3C%2FLI%3E%0A%3CLI%3EIncreased%20information%20about%20historical%20cluster%20and%20application%20events%20in%20Service%20Fabric%20Explorer%3C%2FLI%3E%0A%3CLI%3EProvide%20customers%20with%20diagnostics%20and%20insights%20through%20Azure%20Portal%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSTRONG%3EImprove%20Application%20life%20cycle%20experience%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3ERequest%20drain%20-%26nbsp%3Bgrace%20period%20to%20shutdown%20replicas%3C%2FLI%3E%0A%3CLI%3EEnable%20Services%20that%20Run%20till%20Completion%2FRun%20Once%3C%2FLI%3E%0A%3CLI%3ESupport%20Readiness%20probe-based%20routing%20to%20replicas%26nbsp%3B%3C%2FLI%3E%0A%3CLI%3ESupport%20for%20Health%20Probes%20for%20containerized%20services%3C%2FLI%3E%0A%3CLI%3ESupport%20for%20Initializer%20Code%20Packages%20for%20Containerized%20applications%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSTRONG%3EImage%20Store%20improvements%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3ECompliance%3A%20Remove%20dependency%20on%20NTLM%20%26nbsp%3B%3C%2FLI%3E%0A%3CLI%3EValidate%20integrity%20of%20files%20and%20folders%20downloaded%3C%2FLI%3E%0A%3CLI%3EEnable%20cleanup%20of%20local%20files%20when%20an%20app%20is%20no%20longer%20running%20on%20a%20node%3C%2FLI%3E%0A%3CLI%3EVMSS%20Ephemeral%20OS%20disk%20support%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSTRONG%3EReliable%20Collections%20Improvements%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EIn%20memory%20only%20store%20support%20for%20stateful%20services%20using%20Reliable%20Collections%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1015482%22%20slang%3D%22en-US%22%3E%3CP%3EAzure%20Service%20Fabric%207.0%20is%20now%20available!%26nbsp%3BYou%20will%20be%20able%20to%20update%20to%207.0%20through%20the%20Azure%20Portal%20or%20via%20an%20Azure%20Resource%20Manager%20deployment.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1015482%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Esf_70%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1019361%22%20slang%3D%22en-US%22%3ERe%3A%20Service%20Fabric%207.0%20Release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1019361%22%20slang%3D%22en-US%22%3E%3CP%3ECongrats%20on%20the%26nbsp%3B%20release.%20I%20work%20for%20a%20large%20investment%20bank%20and%20Service%20Fabric%20has%20been%20a%20very%20good%20success%20and%20a%2025%25%20performance%20jump%20from%20the%20previous%20version.%20I%20know%20Service%20Fabric%20is%20not%20getting%20any%20press%20lately%20compared%20with%20Kubernetes%20but%2C%20technologically%20we%20feel%20Service%20Fabric%20is%20superior.%20I%20feel%20both%20Service%20Fabric%20%5Bfor%20Stateful%20Services%20and%20Ease%20of%20use%5D%20and%20Kubernetrs%20%5Bfor%20Linux%20and%20Stateless%20workloads%5D%20have%20a%20space%20to%20play%20in%20enterprise%20distributed%20computing.%20Keep%20up%20the%20release%20cadence%20going.%20Here's%20to%20many%20more%20releases.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1025027%22%20slang%3D%22en-US%22%3ERe%3A%20Service%20Fabric%207.0%20Release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1025027%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F462331%22%20target%3D%22_blank%22%3E%40Przybylski%3C%2FA%3E%26nbsp%3B%20Support%20for%20Ubuntu%2018.04%20refers%20to%20host%20OS%20running%20the%20Service%20Fabric%20run-time.%20This%20will%20allow%20you%20to%20create%20a%20cluster%20on%20a%20host%20running%20Ubuntu%2018.04.%26nbsp%3B%20There%20are%20no%20tooling%20announcements%20as%20part%20of%20this%20support.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1032544%22%20slang%3D%22en-US%22%3ERe%3A%20Service%20Fabric%207.0%20Release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1032544%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3ECross%20Availability%20Zone%20Clusters%20sounds%20interesting%20and%20may%20be%20just%20what%20we're%20waiting%20for...%3CBR%20%2F%3E%3CBR%20%2F%3EAs%20per%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fservice-fabric%2Fservice-fabric-disaster-recovery%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EMS%20Docs%2C%3C%2FA%3E%26nbsp%3Bwe've%20chosen%20to%20run%20a%20single%20service%20fabric%20cluster%20spanning%20multiple%20regions%20and%20using%20placement%20constraints.%20Unfortunately%2C%20as%20far%20as%20I%20know%2C%20you%20still%20can't%20do%20this%20with%20Azure%20Service%20Fabric%20-%20as%20such%2C%20we've%20opted%20for%20a%20self-hosted%20Service%20Fabric%20cluster.%3C%2FSPAN%3E%3CSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3EHowever%2C%20going%20forward%3A%3CBR%20%2F%3Ea)%20Assuming%20this%20is%20coming%20to%20Azure%20Service%20Fabric%20-%20any%20time-frame%20prediction%20for%20this%3F%3CBR%20%2F%3Eb)%20Would%20we%20be%20able%20to%20have%20some%20on-premise%20Nodes%20in%20the%20mix%20with%20Azure%20SF%20Nodes%3F%3CBR%20%2F%3Ec)%20%3CSTRONG%3EWhat%20about%20Azure%20Site%20Replication%20-%20does%2Fwill%20this%20support%20Service%20Fabric%3F%3C%2FSTRONG%3E%20This%20could%20be%20an%20alternative%20for%20us%2C%20but%20I%20can't%20find%20any%20info%20about%20whether%20or%20not%20SF%20would%20support%20this.%20For%20example%2C%20you'd%20run%20a%20%2B5%20node%20Azure%20SF%20cluster%20in%20one%20Azure%20region%2C%20and%20then%20use%20Site%20Replication%20to%20another%20region%20for%20DR%20purposes%20only.%3CBR%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1034439%22%20slang%3D%22en-US%22%3ERe%3A%20Service%20Fabric%207.0%20Release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1034439%22%20slang%3D%22en-US%22%3E%3CP%3E%40%3CSPAN%20class%3D%22UserName%20lia-user-name%20lia-user-rank-Frequent-Visitor%20lia-component-message-view-widget-author-username%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F424127%22%20target%3D%22_self%22%3E%3CSPAN%20class%3D%22%22%3Edebeerisgreat%3C%2FSPAN%3E%3C%2FA%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENot%20sure%20if%20this%20is%20sufficient%2C%20but%20currently%20you%20can%20have%20a%20SF%20cluster%20with%20three%20scalesets%20all%20of%20which%20are%20in%20a%20separate%20zone%20of%20an%20availability%20zone.%20When%20the%20article%20states%20%22%3CSPAN%3ESupport%20for%20using%20a%20single%20Cross-AZ%20Virtual%20Machine%20Scale%20Set%22%20I%20believe%20what%20they%20are%20saying%20is%20that%20scale%20sets%20will%20natively%20support%20nodes%20in%20separate%20zones%2C%20so%20you%20won't%20need%20multiple%20scale%20sets%20(which%20are%20a%20pain%20to%20manage.)%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1043364%22%20slang%3D%22en-US%22%3ERe%3A%20Service%20Fabric%207.0%20Release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1043364%22%20slang%3D%22en-US%22%3E%3CP%3EFor%20those%20running%20on-premise%20SF%20clusters%20and%20want%20to%20send%20cluster%20health%20telemetry%20to%20app%20insights%20-%20I've%20created%20a%20%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2FAdebeer%2FService-Fabric-AppInsights-Health-Monitor%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ewindows%20service%3C%2FA%3E%20that%20makes%20this%20pretty%20easy.%3CBR%20%2F%3E%3CBR%20%2F%3EIt%20uses%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fwww.nuget.org%2Fpackages%2FMicrosoft.ApplicationInsights.PerfCounterCollector%2F%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3EMicrosoft.ApplicationInsights.PerfCounterCollector%3C%2FA%3E%3CSPAN%3E%26nbsp%3Bso%20you%20can%20easily%20add%20additional%20perf%20counters.%20I've%20also%20added%20couple%20of%20Kusto%20queries%20to%20help%20you%20get%20started%20with%20a%20few%20simple%20dashboards%20(e.g.%20tracking%20when%20SF%20nodes%20go%20up%2Fdown)%3CBR%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1035491%22%20slang%3D%22en-US%22%3ERe%3A%20Service%20Fabric%207.0%20Release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1035491%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F469811%22%20target%3D%22_blank%22%3E%40AdmiralBond%3C%2FA%3E%26nbsp%3Bfor%20clarifying%20the%20upcoming%20cross-AZ%20scale%20set%20support%20-%20that%20makes%20sense!%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EI%20did%20quite%20a%20lot%20of%20digging%20and%20found%20the%20info%20on%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fservice-fabric%2Fservice-fabric-cross-availability-zones%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EMSDOCs%3C%2FA%3E%20on%20how%20to%20configure%20a%20cross%20regional%20azure%20service%20fabric%20cluster%20-%20pretty%20cool%20as%20I%20incorrectly%20thought%20you%20could%20only%20have%201%20node%20type%20marked%20as%20primary.%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSTRONG%3EThat%20said%2C%20I%20would%20still%20be%20very%20interested%20in%20using%20an%20Azure%20Site%20Recovery%20based%20solution%20instead.%3C%2FSTRONG%3E%20Specifically%2C%20it'll%20be%20much%20much%20cheaper%20as%20you're%20essentially%20only%20paying%20for%20blob%20storage%20costs%20to%20sync%20the%20Azure%20Nodes%20-%20not%20running%20the%20VMs...%20plus%2C%20in%20our%20case%2C%20we%20can%20then%20get%20away%20with%20running%20all%20our%20nodes%20in%201%20Azure%20region.%20This%20together%20with%20the%20%3CEM%3EService-Fabric-AppDRTool%3C%2FEM%3E%20for%20restoring%20application%20state...%20should%20be%20a%20match%20made%20in%20heaven%26nbsp%3B%3CIMG%20class%3D%22lia-deferred-image%20lia-image-emoji%22%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Fhtml%2Fimages%2Femoticons%2Fhearteyes_40x40.gif%22%20alt%3D%22%3Ahearteyes%3A%22%20title%3D%22%3Ahearteyes%3A%22%20%2F%3E%3CSPAN%3E!%20Unfortunately%2C%20I%20can't%20find%20any%20info%20on%20the%20inter%20webs%20on%20how%20one%20can%20actually%20configure%20and%20spin%20up%20an%20SF%20cluster%20via%20Site%20Recovery.%20I'll%20have%20a%20bit%20more%20detailed%20look%20at%20creating%20an%20Azure%20cluster%20via%20ARM%20templates...%20likely%20that%20would%20provide%20this%20option%20-%20just%20surprised%20no%20one%20as%20done%2Fdocumented%20this%20process%20yet...%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CBR%20%2F%3E%3CSTRONG%3EUpdate%3A%20%3C%2FSTRONG%3EAzure%20Site%20Recovery%20doesn't%20support%20VM%20Scale%20Sets.%20The%20cross-regional%20SF%20cluster%20documentation%20from%20above%20seems%20to%20suggest%20spanning%20your%20nodes%20within%20a%20single%20Availability%20Zone%20(I'm%20guessing%20this%20is%20to%20ensure%20minimal%20latency%20between%20seed%20nodes).%20Our%20current%20On-premise%20SF%20cluster%20spans%20APAC%2FEMEA%2FNA%20regions%20-%20it's%20worked%20ok...except%20for%20periodic%20timeouts%20when%20registering%20packages%3B%20as%20far%20as%20I%20can%20tell%2C%20this%20is%20probably%20due%20to%20image%20store%20sync%20issues%20between%20SEED%20nodes%20located%20in%20different%20data%20centers.%20In%20any%20case%2C%20going%20forward%2C%20we%20decided%20it%20simpler%2Fsafer%20to%20do%20away%20with%20this%20concept%20and%20rather%20run%20independent%20clusters%20and%20use%20AppDRTool%20if%2Fwhere%20required.%20At%20least%20this%20means%20we%20can%20use%20Azure%20hosted%20SF%20clusters%20now%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E

Azure Service Fabric 7.0 is now available! You will be 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.

In January, we will resume the standard roll-out procedure and clusters with automatic upgrades enabled will begin to receive the 7.0 update automatically. We will provide another announcement before the roll-out begins.

  We will also update our planned release dates to indicate that we take this policy into consideration. Looks for updates to release roadmap here.

 

What is new in Service Fabric 7.0?

  We are excited to announce that the next release of Service Fabric is loaded with key features and   improvements.

 

Key Announcements

  • KeyVaultReference support for application secrets (Preview): 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 was not 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 is a constraint violation in the cluster that cannot be fixed in any other way .Please see the docs for additional information on when usage of a “Very High” move cost is reasonable and for additional 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 which 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 7 seed nodes, an operation that would take you below 5 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 policies
    • enabling automatic backups
    • taking adhoc backups
    • triggering restore operations
    • 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 will restrict secondary replicas to returning values which have been quorum-acked.

In addition, this release contains other new features, bug fixes, and supportability, reliability, and performance improvements. For the full list of changes, please refer to the release notes.

 

Current And Upcoming Breaking Change Announcements

  • Starting with Service Fabric version 7.0, we have changed the default value for the PreferUpgradedUDs config flag to FALSE in the PlacementAndLoadBalancing section of the ClusterManifest. Based on numerous cases and customer issues, this default behavior should allow clusters to remain more balanced during upgrades. If you want to preserve today’s behavior for your workload, please perform a cluster configuration upgrade to explicitly set the value to true either prior to or as a part of upgrading your cluster to 7.0.
  • Starting with Service Fabric version 7.0, we have fixed a calculation bug in the Cluster Resource Manager which impacts how node resource capacities are calculated in cases where a user manually provides the values for node resource capacities. The impact of this fix is that the Cluster Resource Manager will now consider there to be less usable capacity in the cluster. For more information, see resource governance.
  • Starting with Service Fabric version 7.0, customers using  Service Fabric Managed Identities, please switch to new environment variables ‘IDENTITY_ENDPOINT’ and ‘IDENTITY_HEADER’. The prior environment variables 'MSI_ENDPOINT', ‘MSI_ENDPOINT_’ and 'MSI_SECRET' are now deprecated in this release and will be removed in 7.0 CU1.
  • For customers using service fabric to export certificates into their Linux containers, the export mechanism will change in an upcoming CU. This change will encrypt the private key included in the .pem file, with the password being stored in an adjacent .key file.
  • Today Service Fabric performs equality comparison for Boolean in placement constraints using a case-sensitive lexical comparison Starting in a subsequent release, we will be changing this comparison to be case-insensitive. This change will only apply to Boolean placement properties/constraints. Other string and numeric constraint values will continue to be treated as they are today (with case sensitive and numeric comparisons, respectively).
  • Currently Service Fabric ships the following nuget packages as a part of our ASP.Net Integration and support:
  • ServiceFabric.AspNetCore.Abstractions
  • ServiceFabric.AspNetCore.Configuration
  • ServiceFabric.AspNetCore.Kestrel
  • ServiceFabric.AspNetCore.HttpSys
  • ServiceFabric.AspNetCore.WebListener

These packages are built against AspNetCore 1.0.0 binaries which have gone out of support (https://dotnet.microsoft.com/platform/support/policy/dotnet-core). Starting in Service Fabric 8.0 we will start building Service Fabric AspNetCore integration against AspNetCore 2.1 and for netstandard 2.0. As a result, there will be following changes:

  1. The following binaries and their nuget packages will be released for netstandard 2.0 only. These packages can be used in applications targeting .net framework <4.6.1 and .net core >=2.0
    1. ServiceFabric.AspNetCore.Abstractions
    2. ServiceFabric.AspNetCore.Configuration
    3. ServiceFabric.AspNetCore.Kestrel
    4. ServiceFabric.AspNetCore.HttpSys
  2. The following package will no longer be shipped:
    1. ServiceFabric.AspNetCore.WebListener:
      1. Use Microsoft.ServiceFabric.AspNetCore.HttpSys instead.

 

Upcoming and Ongoing Work

There are some work items that are not a part of the 7.0 release. We want to let you know that work on these items is still ongoing. At this point we plan for these work items to GA in upcoming 7.0 CUs, or as separate packages available in the upcoming months. The specific delivery dates will be communicated as they get closer to GA.

  • General Availability of Service Fabric Managed Identities for SF apps
  • Support for using low priority/Azure Spot Virtual Machine Scale Sets in Service Fabric clusters
  • FabricObserver (FO) – A configurable and extensible watchdog service that runs as a Service Fabric application
  • Support for Ubuntu 18.04
  • Cross Availability Zone Clusters – Support for using a single Cross-AZ Virtual Machine Scale Set. Today’s workloads require one scale set per AZ. 
  • Increased information about historical cluster and application events in Service Fabric Explorer
  • Provide customers with diagnostics and insights through Azure Portal

Improve Application life cycle experience

  • Request drain - grace period to shutdown replicas
  • Enable Services that Run till Completion/Run Once
  • Support Readiness probe-based routing to replicas 
  • Support for Health Probes for containerized services
  • Support for Initializer Code Packages for Containerized applications

Image Store improvements

  • Compliance: Remove dependency on NTLM  
  • Validate integrity of files and folders downloaded
  • Enable cleanup of local files when an app is no longer running on a node
  • VMSS Ephemeral OS disk support

Reliable Collections Improvements

  • In memory only store support for stateful services using Reliable Collections

 

7 Comments
Occasional Visitor

In terms of upcoming and ongoing work: does the mention of "Support for Ubuntu 18.04" imply standalone deployment tooling for Linux clusters?

Frequent Visitor

Congrats on the  release. I work for a large investment bank and Service Fabric has been a very good success and a 25% performance jump from the previous version. I know Service Fabric is not getting any press lately compared with Kubernetes but, technologically we feel Service Fabric is superior. I feel both Service Fabric [for Stateful Services and Ease of use] and Kubernetrs [for Linux and Stateless workloads] have a space to play in enterprise distributed computing. Keep up the release cadence going. Here's to many more releases.

Microsoft

@Przybylski  Support for Ubuntu 18.04 refers to host OS running the Service Fabric run-time. This will allow you to create a cluster on a host running Ubuntu 18.04.  There are no tooling announcements as part of this support.

Regular Visitor

Cross Availability Zone Clusters sounds interesting and may be just what we're waiting for...

As per MS Docs, we've chosen to run a single service fabric cluster spanning multiple regions and using placement constraints. Unfortunately, as far as I know, you still can't do this with Azure Service Fabric - as such, we've opted for a self-hosted Service Fabric cluster.


However, going forward:
a) Assuming this is coming to Azure Service Fabric - any time-frame prediction for this?
b) Would we be able to have some on-premise Nodes in the mix with Azure SF Nodes?
c) What about Azure Site Replication - does/will this support Service Fabric? This could be an alternative for us, but I can't find any info about whether or not SF would support this. For example, you'd run a +5 node Azure SF cluster in one Azure region, and then use Site Replication to another region for DR purposes only.

Occasional Visitor

@debeerisgreat

 

Not sure if this is sufficient, but currently you can have a SF cluster with three scalesets all of which are in a separate zone of an availability zone. When the article states "Support for using a single Cross-AZ Virtual Machine Scale Set" I believe what they are saying is that scale sets will natively support nodes in separate zones, so you won't need multiple scale sets (which are a pain to manage.)

 

Regular Visitor

Thank you @AdmiralBond for clarifying the upcoming cross-AZ scale set support - that makes sense!


I did quite a lot of digging and found the info on MSDOCs on how to configure a cross regional azure service fabric cluster - pretty cool as I incorrectly thought you could only have 1 node type marked as primary.

That said, I would still be very interested in using an Azure Site Recovery based solution instead. Specifically, it'll be much much cheaper as you're essentially only paying for blob storage costs to sync the Azure Nodes - not running the VMs... plus, in our case, we can then get away with running all our nodes in 1 Azure region. This together with the Service-Fabric-AppDRTool for restoring application state... should be a match made in heaven :hearteyes:! Unfortunately, I can't find any info on the inter webs on how one can actually configure and spin up an SF cluster via Site Recovery. I'll have a bit more detailed look at creating an Azure cluster via ARM templates... likely that would provide this option - just surprised no one as done/documented this process yet... 


Update: Azure Site Recovery doesn't support VM Scale Sets. The cross-regional SF cluster documentation from above seems to suggest spanning your nodes within a single Availability Zone (I'm guessing this is to ensure minimal latency between seed nodes). Our current On-premise SF cluster spans APAC/EMEA/NA regions - it's worked ok...except for periodic timeouts when registering packages; as far as I can tell, this is probably due to image store sync issues between SEED nodes located in different data centers. In any case, going forward, we decided it simpler/safer to do away with this concept and rather run independent clusters and use AppDRTool if/where required. At least this means we can use Azure hosted SF clusters now :)

Regular Visitor

For those running on-premise SF clusters and want to send cluster health telemetry to app insights - I've created a windows service that makes this pretty easy.

It uses Microsoft.ApplicationInsights.PerfCounterCollector so you can easily add additional perf counters. I've also added couple of Kusto queries to help you get started with a few simple dashboards (e.g. tracking when SF nodes go up/down)