10805c3e8f
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
31 lines
1.3 KiB
ReStructuredText
31 lines
1.3 KiB
ReStructuredText
|
|
.. fez1617811988954
|
|
.. _the-kubernetes-distributed-cloud-update-orchestration-process:
|
|
|
|
====================================================================
|
|
Kubernetes Version Upgrade Distributed Cloud Orchestration Overviews
|
|
====================================================================
|
|
|
|
For an orchestrated Kubernetes version upgrade across a |prod-dc|, 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 :command:`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 :ref:`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:
|
|
|
|
.. _fez1617811988954-ol-a1b-v5s-tlb:
|
|
|
|
#. Create the subcloud kube upgrade strategy based on the new version installed as part of the platform.
|
|
|
|
#. Apply the subcloud kube upgrade strategy.
|