8b591b5a80
This change provides two system commands: 'system kube-host-cordon'
and 'system kube-host-uncordon'. The "system kube-host-cordon
<host-name>" command will evict the regular pods from the host.
This command will not evict the mirror and daemon set-managed pods.
The "system kube-host-uncordon <host-name>" command will
allow the regular pods on the host again.
These system commands will be used during K8s version upgrade on
AIO-SX and in the following sequence:
- system kube-upgrade-start <target-version>
- system kube-upgrade-download-images
- system kube-upgrade-networking
- system kube-host-cordon controller-0
- system kube-host-upgrade controller-0 control-plane
- system kube-host-upgrade controller-0 kubelet
- system kube-host-uncordon controller-0
- system kube-upgrade-complete
- system kube-upgrade-delete
Test Plan: Debian
PASS: Fresh install ISO as AIO-SX. Successfully upgraded
from 1.23.1 to 1.24 using the manual K8s upgrade.
After executing cordon system command some of the pods went to
the 'Pending' status. After executing uncordon system command
pending pods are return to 'Running' status.
Used the command 'kubectl get pods -n <namespace>' to verify
the status before and after executing the cordon and uncordon.
Story: 2010565
Task: 47825
Change-Id: Ia07e1ec3e4f955f3b6dd1ea6084b9682b3f09acd
Signed-off-by: Ramesh Kumar Sivanandam <rameshkumar.sivanandam@windriver.com>
|
||
|---|---|---|
| .. | ||
| centos | ||
| cgts-client | ||
| debian | ||
| opensuse | ||
| .gitignore | ||
| PKG-INFO | ||