feat(demo): deliver four-Pod MVP installation and benchmark package - #82
Merged
Merged
Conversation
added 9 commits
September 20, 2026 15:42
Keep database processes non-root, bind device ownership to a single deployment, and allow reuse only after coordinated clean shutdown. Freeze product sources at v0.131.0 without kernel changes.
Insert shared test rows only after cluster activation. Preserve client returns and full ordered row evidence, and fail reports on SQL errors, server errors or incorrect committed sums.
Provide customer prerequisites, startup, data, benchmark and clean restart commands. Exercise both native architectures and require protected CI before publishing tested OCI images.
The first native CI run reached Pod creation but not SQL readiness. Retain only runtime logs and summaries so the compatibility failure can be diagnosed without exporting bootstrap credentials or database contents.
Compare the identical non-root capability-free TCP probe with runtime-set and entrypoint-set no-new-privileges. Preserve AppArmor denial evidence without changing host policy or database code.
Reproduce Ubuntu crun profile stacking with runtime-applied NNP. Set NNP at the trusted image entrypoint and managed exec boundaries, assert actual kernel flags, and verify running PostgreSQL processes before and after restart. Run kube play from owned storage to avoid its image-name probe colliding with the customer script.
Podman 4 legacy pod inspect emits an object for one Pod while Podman 5 emits an array. Use inspect --type=pod, whose array output is stable, without changing exact ownership or stopped-state checks. Native Ubuntu reached clean shutdown before exposing this compatibility failure.
The retained normal-restart trace proves an early probe emitted the expected PostgreSQL starting-up FATAL, which strict startup validation refused. Wait for all four current-launch ready messages before SQL; keep the error gate unchanged and retain the failed attempt.
Owner
Author
|
Post-merge release status: image publication is BLOCKED. Both PR native lifecycle jobs and all protected PR/main checks passed, but final publication run 35500993944 had an AMD64 normal-shutdown failure (LMON identity rejection/FATAL followed by post-checkpoint closure PANIC). ARM64 passed. The publication job was skipped; ghcr.io/sqlrush/pgrac-demo:v0.131.0-demo.1 has NOT been released. Failure logs are retained in that run. No check will be waived and no retry-only success will close the defect. A documentation follow-up warns customers. Database kernel remains the frozen v0.131.0 source. |
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
1 participant
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.
Delivery
Frozen v0.131.0 database, four non-root Podman Pods on one Linux host. Includes a Chinese installation manual, environment checks, initialization/benchmark scripts, persistent local shared data, coordinated normal stop and original-data restart. No kernel changes.
Verified candidate 950aa9c
Release boundary
Single-host demonstration, not multi-host shared-LUN or HA certification. No automatic crash recovery, destructive reset, rolling upgrade or forced shutdown. Owner permits this delivery only to skip human CODEOWNER approval after all CI and container tests pass; no CI waived. Public image publication and anonymous pull verification follow main integration.