Updated K8 Upgrade Sections of the Distributed Cloud Guide / Updates Guide
Removed additional Change-ID Updated Patchset 6 comments Fixed build errors Updated Patchset 3 comments Updated Patchset 2 comments Added an additional command "system health-query-kube-upgrade" Updated CLI output to include [--to-version TO_VERSION] Updated Patchset 1 comments Signed-off-by: Juanita-Balaraj <juanita.balaraj@windriver.com> Change-Id: I1fddb8eef40de8bcdc976b43a3219a653abbf604
This commit is contained in:
Juanita-Balaraj
@@ -3,7 +3,7 @@
|
||||
.. _configuring-kubernetes-update-orchestration-on-distributed-cloud:
|
||||
|
||||
====================================================================
|
||||
Kubernetes Version Upgrade Distributed Cloud Orchestration Procedure
|
||||
Configure Kubernetes Version Upgrade Distributed Cloud Orchestration
|
||||
====================================================================
|
||||
|
||||
You can configure a *Kubernetes Version Upgrade Distributed Cloud
|
||||
@@ -130,6 +130,7 @@ controller for access by subclouds. For example:
|
||||
[--max-parallel-subclouds MAX_PARALLEL_SUBCLOUDS]
|
||||
[--stop-on-failure] [--force]
|
||||
[--group GROUP]
|
||||
[--to-version TO_VERSION]
|
||||
[cloud_name]
|
||||
|
||||
|
||||
@@ -158,6 +159,16 @@ controller for access by subclouds. For example:
|
||||
strategy that is only applied to all subclouds in the specified group. If
|
||||
not specified, all subcloud groups are upgraded.
|
||||
|
||||
**--force**
|
||||
Ignore the audit status of subclouds when selecting them for
|
||||
orchestration. This allows subclouds that are in-sync to be orchestrated.
|
||||
|
||||
**to-version**
|
||||
Specify a target version for Kubernetes orchestration. The subcloud
|
||||
will orchestrate to its 'available' version if the 'to-version' is
|
||||
greater or equal to the available version. The 'to-version' can be a
|
||||
partial version. For example, if the available version is 1.20.5,
|
||||
selecting 1.20 would upgrade to that version.
|
||||
|
||||
#. Optional: Display the strategy in summary, if required. The Kubernetes
|
||||
upgrade strategy :command:`show` command displays the strategy in a summary.
|
||||
@@ -172,7 +183,7 @@ controller for access by subclouds. For example:
|
||||
| subcloud apply type | None |
|
||||
| max parallel subclouds | None |
|
||||
| stop on failure | False |
|
||||
| state | complete |
|
||||
| state | initial |
|
||||
| created_at | 2020-11-09 23:00:07.210958 |
|
||||
| updated_at | 2020-11-09 23:01:15.697763 |
|
||||
+------------------------+----------------------------+
|
||||
|
||||
@@ -108,9 +108,9 @@ FPGA device image update management
|
||||
|
||||
device-image-update-orchestration
|
||||
|
||||
----------------------------------------------------------
|
||||
Kubernetes Version Upgrade Distributed Cloud Orchestration
|
||||
----------------------------------------------------------
|
||||
--------------------------------------------------------------------
|
||||
Configure Kubernetes Version Upgrade Distributed Cloud Orchestration
|
||||
--------------------------------------------------------------------
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 1
|
||||
|
||||
@@ -2,9 +2,13 @@
|
||||
.. fez1617811988954
|
||||
.. _the-kubernetes-distributed-cloud-update-orchestration-process:
|
||||
|
||||
====================================================================
|
||||
Kubernetes Version Upgrade Distributed Cloud Orchestration Overviews
|
||||
====================================================================
|
||||
===================================================================
|
||||
Kubernetes Version Upgrade Distributed Cloud Orchestration Overview
|
||||
===================================================================
|
||||
|
||||
Before you create a *Kubernetes Version Upgrade Distributed Cloud Orchestration
|
||||
Strategy*, ensure that the Kubernetes version on the System Controller has been upgraded
|
||||
using the procedure documented in :ref:`Manual Kubernetes Version Upgrade <manual-kubernetes-components-upgrade>`.
|
||||
|
||||
For an orchestrated Kubernetes version upgrade across a |prod-dc|, you need to
|
||||
first create a *Kubernetes Version Upgrade Distributed Cloud Orchestration
|
||||
@@ -13,18 +17,18 @@ 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>`.
|
||||
**show** command. For more information, see :ref:`Create Kubernetes Version
|
||||
Upgrade Cloud Orchestration Strategy <configuring-kubernetes-update-orchestration-on-distributed-cloud>`.
|
||||
|
||||
Kubernetes upgrade orchestration automatically iterates through all managed
|
||||
online subclouds.
|
||||
online subclouds if you do not specify a group of subclouds to be upgraded.
|
||||
|
||||
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.
|
||||
#. Creating the subcloud kube upgrade strategy based on the new version installed
|
||||
as part of the platform.
|
||||
|
||||
#. Apply the subcloud kube upgrade strategy.
|
||||
#. Applying the subcloud kube upgrade strategy.
|
||||
|
||||
@@ -66,24 +66,27 @@ Follow the steps below to manually upgrade the System Controller:
|
||||
#. Confirm that the system is healthy.
|
||||
|
||||
Check the current system health status, resolve any alarms and other issues
|
||||
reported by the :command:`health-query-upgrade` command, then recheck the
|
||||
system health status to confirm that all **System Health** fields are set
|
||||
to **OK**.
|
||||
reported by the :command:`system health-query-upgrade` command then recheck
|
||||
the system health status to confirm that all **System Health** fields are
|
||||
set to **OK**.
|
||||
|
||||
.. code-block:: none
|
||||
|
||||
~(keystone_admin)]$ system health-query-upgrade
|
||||
System Health:
|
||||
All hosts are provisioned: [OK]
|
||||
All hosts are unlocked/enabled: [OK]
|
||||
All hosts have current configurations: [OK]
|
||||
All hosts are patch current: [OK]
|
||||
Ceph Storage Healthy: [OK]
|
||||
No alarms: [OK]
|
||||
All kubernetes nodes are ready: [OK]
|
||||
All kubernetes control plane pods are ready: [OK]
|
||||
Required patches are applied: [OK]
|
||||
License valid for upgrade: [OK]
|
||||
System Health:
|
||||
All hosts are provisioned: [OK]
|
||||
All hosts are unlocked/enabled: [OK]
|
||||
All hosts have current configurations: [OK]
|
||||
All hosts are patch current: [OK]
|
||||
Ceph Storage Healthy: [OK]
|
||||
No alarms: [OK]
|
||||
All kubernetes nodes are ready: [OK]
|
||||
All kubernetes control plane pods are ready: [OK]
|
||||
Required patches are applied: [OK]
|
||||
License valid for upgrade: [OK]
|
||||
No instances running on controller-1: [OK]
|
||||
All kubernetes applications are in a valid state: [OK]
|
||||
Active controller is controller-0: [OK]
|
||||
|
||||
By default, the upgrade process cannot run and is not recommended to run
|
||||
with active alarms present. It is strongly recommended that you clear your
|
||||
|
||||
Reference in New Issue
Block a user