US 12,438,773 B2
Autonomous configuration-based release orchestration with autonomous runtime container management configuration
Vijay Karani, Fremont, CA (US); Arunabha Ghosh, San Jose, CA (US); Firas Saltaji, Mississauga (CA); Varun Arvind Jobanputra, New York, NY (US); and Brian Whitten, Burlingame, CA (US)
Assigned to Salesforce, Inc., San Francisco, CA (US)
Filed by Salesforce, Inc., San Francisco, CA (US)
Filed on Jan. 31, 2024, as Appl. No. 18/429,381.
Prior Publication US 2025/0247292 A1, Jul. 31, 2025
Int. Cl. H04L 41/082 (2022.01); G06F 8/65 (2018.01); G06F 8/656 (2018.01); H04L 41/0859 (2022.01); H04L 43/062 (2022.01)
CPC H04L 41/082 (2013.01) [G06F 8/65 (2013.01); G06F 8/656 (2018.02); H04L 41/0863 (2013.01); H04L 43/062 (2013.01)] 20 Claims
OG exemplary drawing
 
1. A method for both autonomous container management configuration changes to container clusters during runtime and autonomous configuration-based release orchestration that supports staggered feature releases across a plurality of container clusters, wherein an application in application (app) containers in the plurality of container clusters include features that each have a state that may be changed, the method comprising:
by a release manager outside of the container clusters, managing a staggered feature release that includes a plurality of staggers, an order for the staggers, and which subset of one or more of the plurality of container clusters is in each stagger;
by a logging service, managing logs generated by the plurality of container clusters and/or the app containers within the plurality of container clusters;
by an update service, outside of the container clusters and coupled to the logging service, determining container management configuration changes based on analysis of data, the data provided at least in part by the logging service;
by a shared engine, outside of the container clusters and coupled to the release manager and the update service, attempting to implement instructions provided by the release manager and the update service at different times, wherein instructions provided by the release manager pertain to one of the plurality of staggers selected by the release manager as a current stagger;
by the release manager, receiving an indication of success or failure of the attempted deployment of the feature release to the current stagger; and
by the release manager, responsive to at least the indication of success or failure of the attempted deployment of the feature release, determining to perform one of a plurality of actions, wherein the plurality of actions includes i) attempting to deploy the feature release to a next one of the plurality of staggers according to the order, and ii) rolling back.