Skip to content

Conversation

@fuweid
Copy link
Member

@fuweid fuweid commented Feb 5, 2024

Summary:

  • Add some helper functions to reduce duplicate code in upgrade testsuite
  • Change Runtime.Status proto so that we can dump CRI configuration by API
  • Add some checkers to ensure there is no leaky resources after upgrade
  • Add failpoint in existing recover case: new release containerd should take over dead shim correctly
  • Add new case to check new release containerd can parse metric data from existing shim created by previous release.

Closes: #3757

NOTE: We should create new issue to track test suite in windows platform. For linux, I think we can close #3757 if this one is acceptable.

@fuweid fuweid added this to the 2.0 milestone Feb 5, 2024
CRI Runtime Status contains `Info` and it can help us check current
configuration.

Signed-off-by: Wei Fu <[email protected]>
The new release containerd should cleanup old pod's data dir after
RemovePodSandbox.

Signed-off-by: Wei Fu <[email protected]>
We can inject failpoint in beforeUpgradeHookFunc.

Signed-off-by: Wei Fu <[email protected]>
The new release containerd should detect dead shim during recover.

Signed-off-by: Wei Fu <[email protected]>
It's used to check new release containerd can parse metric data from existing
shim created by previous release.

Signed-off-by: Wei Fu <[email protected]>
Copy link
Member

@mikebrow mikebrow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM
do we need to modify / create any upgrade docs to reflect a need to verify we have drained the node first?

@estesp estesp added this pull request to the merge queue Feb 16, 2024
Merged via the queue into containerd:main with commit 0f5586e Feb 16, 2024
@fuweid fuweid deleted the upgrade-testcase branch February 17, 2024 00:43
@fuweid
Copy link
Member Author

fuweid commented Feb 17, 2024

@mikebrow

do we need to modify / create any upgrade docs to reflect a need to verify we have drained the node first?

I think we can revisit all impact/changelog changes and then update docs if we need.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

Add binary upgrade tests

5 participants