
This commit introduces DC Kubernetes upgrade orchestration. - Added a new kubernetes endpoint for DC audit The audit compares that the active-target-version in the subcloud for kubernetes matches the system controller. - Wiring the kubernetes strategy to the kube orch thread - Add protections to orchestrator shutdown for when 'start' encounters a problem. - Added 'kubernetes' as a valid strategy type for: create / abort / delete / show - Update the endpoint flag file name to trigger updating the new endpoint - Added a kubernetes orch thread similar to sw upgrade orch thread with these states: - updating kube patches - creating vim patch strategy - applying vim patch strategy - deleting vim patch strategy - creating vim kube upgrade strategy - applying vim kube upgrade strategy Patch vim orchestration steps will be skipped if there are no patches that need to be applied in the subcloud. Change-Id: Ic508ed1a504dba177c100a9caf783e87bc10193a Story: 2008137 Task: 41177 Depends-On: https://review.opendev.org/c/starlingx/nfv/+/767421 Signed-off-by: albailey <al.bailey@windriver.com>
DistributedCloud
Wind River's Distributed Cloud system supports an edge computing solution by providing central management and orchestration for a geographically distributed network of Titanium Cloud systems.