starlingx/docs
Code Issues Proposed changes
docs/doc/source/dist_cloud/kubernetes/create-a-kubernetes-upgrade-orchestration-using-horizon-16742b62ffb2.rst
Ron Stone a9f6845ab0 Re-arranged DC Horizon page 
Image and related text updates.
Some associated rST markup changes for consistency.
Updates for patchset 1 review comments.
Substantial new content to better cover Horizon usage.
Updates for patchset 3 review comments.
Updates for patchset 4 review comments.
Updates for patchset 5 review comments.
Fix typo.
Fix numbering in procedures.
Updates for patchset 8 review comments.
Clarified **Subcloud** option description.
Remove redundant sentence.
Changes to image usage to remove duplication.

Signed-off-by: Ron Stone <ronald.stone@windriver.com>
Change-Id: I53d93b93629851c07d0cd95ef1fb9c6f3fd9a0a5
2022-06-23 06:54:12 -04:00

3.0 KiB
Raw Blame History

Create a Kubernetes Upgrade Orchestration using Horizon

Use the Horizon Web interface as an alternative to the CLI for managing Kubernetes upgrade strategies.

Only one update strategy can exist at a time. The strategy controls how the subclouds are updated (for example, serially or in parallel).

Management-affecting alarms cannot be ignored using relaxed alarm rules during an orchestrated Kubernetes version upgrade operation. For a list of management-affecting alarms, see : fm-alarm-messages.

You can use the Horizon Web interface to check the alarm states:

  1. Select the SystemController region.
  2. Select Admin > Fault Management.
  3. Select Active Alarms.

  1. Select the SystemController region.

  2. Select Distributed Cloud Admin > Orchestration.

  3. On the Orchestration page, select the Orchestration Strategy tab.

    Orchestration Strategy

  4. Create a new strategy.

    On the Orchestration Strategy tab, click Create Strategy. In the Create Strategy dialog box, adjust the settings as needed.

    Strategy Type

    Kubernetes

    Apply to

    Subcloud or Subcloud Group

    Subcloud

    Enter the subcloud name

    Subcloud Group

    Enter the subcloud group name only if you select the Apply to: Subcloud Group option.

    Stop on Failure

    Default: True

    Determines whether update orchestration failure for a subcloud prevents application to subsequent subclouds.

    Subcloud Apply Type

    Default: Parallel

    Parallel or Serial. Determines whether the subclouds are updated in parallel or serially.

    Maximum Parallel Subclouds

    Default: 20

    If this is not specified using the CLI, the values for max_parallel_subclouds defined for each subcloud group will be used by default.

    Force

    Default: False

    Force kube upgrade to a subcloud which is in-sync with system controller.

    To version

    Not currently supported.

    Create a strategy

  5. Adjust how Kubernetes is upgraded on RegionOne and on subclouds.

  6. Save the new strategy.

    Click Create Strategy.

Only subclouds in the Managed state and whose patching sync status is out-of-sync are added to the list. To change the Kubernetes Upgrade strategy settings, you must delete the current strategy and create a new one. You must confirm before applying the strategy. If the strategy is older than 60 minutes, a warning message will be display on this popup. You can simply apply the strategy or verify that it is still valid.