-
Notifications
You must be signed in to change notification settings - Fork 1.9k
openshift-sdn to ovn-kubernetes migration testing feedback #24445
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Explicitely state success of no lingering openshift-sdn pods Use watch command rather than the oc --watch arg, which offers no indication of completion
|
@dlbewley thanks, I'll take a look! |
|
if i had a nickel for every time i've mistyped kubernetes..., i'd be less embarrased |
| + | ||
| ---- | ||
| $ oc get pod -n openshift-sdn --watch | ||
| $ watch oc get pod -n openshift-sdn |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dlbewley, what makes this preferable than --watch?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The condition the user wants to see is that all the pods are gone. Using --watch simply emits a stream of changes . It is much more obvious when the pods are gone with watch <cmd>, particularly if there are many pods (nodes).
If watch can be assumed to be broadly available I think the output is much more clear.
|
Hi @huiran0826, Do these updates make sense? Thanks! |
|
lgtm |
codyhoag
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Two small suggestions. Otherwise, LGTM!
| ---- | ||
|
|
||
| . To confirm that the migration disabled the OVN-Kubernetes default CNI network provider, enter the following command. It might take several moments for all the OVN-Kubernetes Pods to stop. | ||
| . To confirm that the migration disabled the OVN-Kubernetes default CNI network provider and removed all the OVN-Kubernetes pods, enter the following command. It might take several moments for all the OVN-Kubernetes Pods to stop. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/pods/Pods
|
@dlbewley, if you can fix the two issues above we're good to go with this. Thanks! |
|
@dlbewley, squashed and merged, thanks! |
…#24445) Update procedure for OVN-Kubernetes migration Explicitly state success of no lingering openshift-sdn pods Use watch command rather than the oc --watch arg, which offers no indication of completion Co-authored-by: Vagner Farias <vfarias@redhat.com>
…#24445) Update procedure for OVN-Kubernetes migration Explicitly state success of no lingering openshift-sdn pods Use watch command rather than the oc --watch arg, which offers no indication of completion Co-authored-by: Vagner Farias <vfarias@redhat.com>
…24832) Update procedure for OVN-Kubernetes migration Explicitly state success of no lingering openshift-sdn pods Use watch command rather than the oc --watch arg, which offers no indication of completion Co-authored-by: Dale Bewley <dale@bewley.net> Co-authored-by: Vagner Farias <vfarias@redhat.com>
[enterprise-4.6] openshift-sdn to ovn-kubernetes migration testing feedback (#24445)
Suggested updates for openshift-sdn to ovn-kubernetes migration docs.