k8s upgrade via Horizon - Add "to-version" field to k8s upgrade strategy
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Low
|
Cristian Mondo |
Bug Description
Brief Description
-----------------
k8s upgrade via GUI - Add "to-version" field to k8s upgrade strategy
This option is available via cli but it is not available via GUI.
It would be good to have it in the following scenario:
customer has a subcloud group with subclouds with different k8s versions
custumer wants to sync k8s version for all subclouds using the highest active version among the subcloud.
Using the field "to-version" it would be possible to use a specific kube version and the orchestration would skip the subclouds which already have the target kube version as an active version.
if the field "to-version" is not specified the orchestration will upgrade all the subclouds to its available kube version, which can be different between each other.
Severity
--------
<Minor: System/Feature is usable with minor issue>
Steps to Reproduce
------------------
deploy a dc system with multiple subclouds
create a kube upgrade strategy on GUI
select "subcloud-group" to "Apply to" field
Reproducibility
---------------
State if the issue is 100% reproducible
System Configuration
-------
Dc systems
Workaround
----------
Using CLI to upgrade instead of GUI
Changed in starlingx: | |
assignee: | nobody → Cristian Mondo (cmondo) |
Changed in starlingx: | |
importance: | Undecided → Low |
tags: | added: stx.gui |
tags: | added: stx.8.0 |
Fix proposed to branch: master /review. opendev. org/c/starlingx /gui/+/ 859639
Review: https:/