Run Docker tests with systemd-node, allows K3s service restarts #11638
+522
−577
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed Changes
rancher/systemd-node
image as the base for K3s Docker tests. The K3s binary is mounted and the service installed via the normal install script. This allows docker tests to operate k3s as a regular service, with stops and restarts.snapshotrestore
E2E test from vagrant into a docker test. This allows us to run a test we previously could not in GHARunCmdOnNode
a method are steps in that directionconfig.yaml
Types of Changes
Testing/CI
Verification
CI passes, with new tests
Snapshot Restore Performance Comparison
Testing
Its all new tests
Linked Issues
#11625
User-Facing Change
Future PR work: