starlingx/docs
Code Issues Proposed changes
Files
81245866d7ebe7798c1bccd9fc8f1ad3efc4681c
docs/doc/source/dist_cloud/kubernetes/the-kubernetes-distributed-cloud-update-orchestration-process.rst
Ron Stone ab2c5331c8 Apply dir convention to DC 
Moved all DC content under a kubernetes directory. This is needed
to allow title versioning distinctions in partner builds.

Signed-off-by: Ron Stone <ronald.stone@windriver.com>
Change-Id: Ia7ab4fccc7cb9ed6c242cf584f237165f00e5ef2
(cherry picked from commit 10805c3e8f)

Move files into 'kuberneres' subdir

Needed for compatability with downstream builds per master 10805c3

Signed-off-by: Ron Stone <ronald.stone@windriver.com>
Change-Id: I4a15a09217584795274887837318113deabf1f9d
Signed-off-by: Ron Stone <ronald.stone@windriver.com>
2021-09-03 17:19:18 +00:00

1.3 KiB
Raw Blame History

Kubernetes Version Upgrade Distributed Cloud Orchestration Overviews

For an orchestrated Kubernetes version upgrade across a , you need to first create a Kubernetes Version Upgrade Distributed Cloud Orchestration Strategy, or plan, for the automated Kubernetes version upgrade procedure orchestrated across all subclouds of the Distributed Cloud system.

You must use the dcmanager CLI tool to create, and then apply the upgrade strategy. A created strategy can be monitored with the show command. For more information, see Kubernetes Version Upgrade Distributed Cloud Orchestration Procedure <configuring-kubernetes-update-orchestration-on-distributed-cloud>.

Kubernetes upgrade orchestration automatically iterates through all managed online subclouds.

The specific steps involved in a Kubernetes Version Upgrade Distributed Cloud Orchestration for a single or group of hosts in each subcloud includes:

  1. Create the subcloud kube upgrade strategy based on the new version installed as part of the platform.
  2. Apply the subcloud kube upgrade strategy.