Repository navigation
Conversation
…orage-apply-released-pool-layout-5787
…eleased-pool-layout-5787
…eleased-pool-layout-5787
…eleased-pool-layout-5787
…eleased-pool-layout-5787 # Conflicts: # .github/actions/deploy-prod/action.yml # .github/workflows/cd.yaml # .github/workflows/ci.yaml # .github/workflows/dr-rebuild.yaml # .github/workflows/prove-scoped-package-access.yaml # .github/workflows/validate-image-verifier-liveness.yaml # .github/workflows/validate-main.yaml # k8s/bases/infrastructure/controllers/ksail-operator/oci-repository.yaml # scripts/reconcile-talos-kernel-args/audited_inputs.go
Contributor
✅
|
Contributor
✅
|
Part of #5787. The released operator adds only core nodes/list to account for host node networks during nested Kind provisioning. Regenerate the exact-grant fixture through its existing generator; preserve policy exclusions, write permissions and all broadening/aggregation negative controls.
Contributor
Author
Release applicability review for KSail 7.213.4, source
The published CLI passed both local and production workload validation. The actual CI render regression passed with the pinned Talos client, and the fold package race tests and source-pin check passed after merging the current base. The raw pool patch fixtures were checked for encryption, locked-state keys and the preserved existing extent. The chart RBAC regression passes for 20 rendered roles, eight exact excluded-role grants and five built-in aggregate contributors; broadening, unexcluded privileged roles and new aggregation are refused. The local actionlint version does not recognize the repository's existing Code Quality permission; this is a local-tool limitation, with hosted workflow validation still required. This draft does not grant reset clearance or activate V2. #6075 and fresh native preparation/account checks remain merge/deployment prerequisites; current-head hosted checks and substantive review must settle before promotion. |
Code coverage overviewLanguages: Go Go / code-coverage/go
Line coverage data for the main branch is not yet available. View coverage of the 10 most covered files.
ℹ️ Calculations represent line coverage. Results may change as calculations are updated. Updated |
…eleased-pool-layout-5787 # Conflicts: # .github/actions/deploy-prod/action.yml # .github/workflows/cd.yaml # .github/workflows/ci.yaml # .github/workflows/dr-rebuild.yaml # .github/workflows/prove-scoped-package-access.yaml # .github/workflows/validate-image-verifier-liveness.yaml # .github/workflows/validate-main.yaml # k8s/bases/infrastructure/controllers/ksail-operator/oci-repository.yaml
devantler
added a commit
that referenced
this pull request
Nov 11, 2026
Contributor
Author
@coderabbitai review |
Contributor
Action not completed
|
Contributor
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 33 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. |
Contributor
Author
@codex review |
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Codex Review: Didn't find any major issues. What shall we delve into next? Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
…eleased-pool-layout-5787 # Conflicts: # .github/actions/deploy-prod/action.yml # .github/workflows/cd.yaml # .github/workflows/ci.yaml # .github/workflows/dr-rebuild.yaml # .github/workflows/prove-scoped-package-access.yaml # .github/workflows/validate-image-verifier-liveness.yaml # .github/workflows/validate-main.yaml # k8s/bases/infrastructure/controllers/ksail-operator/oci-repository.yaml
…orage-apply-released-pool-layout-5787
devantler
added a commit
that referenced
this pull request
Nov 11, 2026
Contributor
Author
The current signed revision is The published binary still matches its verified archive and Go 1.27.4 build. Both local and production schema validations pass all 878 files, retaining the three previously recorded offline namespace-selector warning families. The audited kernel-argument fold check passes; affected fold, migration and provider packages pass race tests. The setup helper controls pass, and the new complete download-guard race suite passes in 3.251 seconds with GNU checksum tooling. Bare actionlint 1.7.12 still refuses the existing Prior CI and review at 2426b81 are historical. Current-head CI and substantive review are required again. The native provider-account and preparation prerequisites still hold this draft; no pool reset, capacity release or V2 activation is established. |
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.
Why
The temporary migration workers need usable raw disks before platform volumes can move to Longhorn V2. Their current disk layouts prevent that preparation.
What
Adopts the released storage-pool tooling and encrypted layouts for the existing temporary workers, preserving their locked-state keys and the existing raw disk. Rebuilds remain separately guarded and use the approved temporary capacity.
Part of #5787