-
Notifications
You must be signed in to change notification settings - Fork 3.8k
sandbox: add cri integration test case for upgrade #9434
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
|
Hi @abel-von. Thanks for your PR. I'm waiting for a containerd member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/ok-to-test |
|
/retest |
cf49701 to
c3660f9
Compare
fuweid
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.
LGTM
Just let comments on naming. Thanks!
c3660f9 to
658373b
Compare
Signed-off-by: Abel Feng <fshb1988@gmail.com>
For backward compatibility, we should get runtimeInfo from sandbox in db, or get it from the sandbox container in db. Note that this is a temporary solution and we will remove the Container field in Sandbox in cri cache, and replace it with a SandboxInsantance of type containerd.Sandbox interface. Signed-off-by: Abel Feng <fshb1988@gmail.com>
658373b to
c036375
Compare
Hmm, never see this before. |
To make sure the compatibility when upgrade from 1.6-1.7, or 1.7-2.0, we add more test cases to manipulate the containers in the pod of old version.
and we add a commit to fix the compatibility issue. that when get runtime info of sandbox, we may have to downgrade to get it from sandbox container.