Repository navigation
Conversation
Render a validated node-owned checkpoint mode through Helm while preserving existing defaults. Provide a reusable reflink overlay and document filesystem compatibility, draining, artifact retention, and the distinction from dirty-memory incremental checkpoints. Validate explicit mode rendering, rejected unsupported modes and custom configuration markers with chart regressions. Signed-off-by: 月可 <hukeyang.hky@antgroup.com>
hky1999
force-pushed
the
hky1999/runsc-reflink-checkpoint-profile
branch
from
October 28, 2026 14:59
3da95e6 to
08ee1c7
Compare
hky1999
changed the title
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Expose an explicit runsc reflink checkpoint setting through Helm, so operators can enable the managed file-backed workload profile without maintaining a custom Sandboxd configuration. The default remains unset and follows the runtime default.
Review baseline
Rebased on inclusionAI/AKernel:develop, commit 5ded29d. Current head 08ee1c7. This is the deployment configuration part of the Harbor/Compose integration, separate from SDK #127 and Sandboxd #83.
Changes
node.config.sandboxd.runscCheckpointMode(fullorreflink); reject unsupported values.deploy/akernel/profiles/runsc-reflink.yamloverlay and filesystem/drain/artifact-retention guidance. Reflink is distinct from dirty-memory incremental snapshots.Validation and rollout boundary
The four checkpoint-mode regressions and 27 related ADX chart regressions passed; deployment script syntax checks passed. A broader 109-test chart run had one unrelated existing node-directory test error and one root-only skip in this client environment; the failing case was reproduced against the unmodified develop chart/script in a separate worktree. Those files are unchanged by this PR.
No Helm apply, production deployment, filesystem formatting/mounting, Coordinator update or runtime publication was performed. Before rollout, review compatible runtime support, filesystem reflink/same-mount requirements, durable sync and draining. Managed Docker uppers additionally require merged/pinned Sandboxd #83; the SDK cannot enable that server capability itself.