-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Description
Motivation
There are two motivations.
-
Some users have different clusters with different version. Although it is possible to switch server context by
oc login, client version cannot. Since k8s/openshift supports only N±1 version, oc client sometimes incompatible. -
During upgrade, playbook upgrade.yml executes:
step-1. Run some pre operations with oc command like
# oc adm migrate storagein pre upgrade storage .
step-2. Update client package (e.g oc v3.7->3.9).
step-3. Run some post operations with updated oc command like# oc adm migrate storage.
So, If playbook failed at step-3, re-running playbook from step-1 will fail due to incompatible client version.
Additional Information
One possible solution is that switching symbolic link by a script. However, the motivation #2 needs a official solution from client options or RPM package release.