Skip to content

Adopt the KSail routing and inventory fixes in production tooling #6442

Open

Description

@devantler

🤖 Generated by the Agentic Engineer

Problem

Production deployment, recovery and validation need a coherent KSail version containing the reviewed routing and inventory fixes. Updating only one caller would leave an older update path in use.

Scope

Adopt a published release containing devantler-tech/ksail#8417, devantler-tech/ksail#8418 and the safe-removal follow-up devantler-tech/ksail#8439 across the relevant CLI and coupled SDK/audit inputs, after the validation compatibility gaps are resolved. Preserve the declared Talos and Kubernetes versions and every existing deployment, authorization and review gate. Include the contracts validation caller added by #6443 when rebinding the final change.

Part of #6433. This delivery slice is separate from the recovery owner's provider operation.

Acceptance criteria

  • Verify the release source contains the routing, inventory and safe-removal fixes and its published native CLI archive, checksum manifest and embedded source/version proof; separately verify the coupled chart and controller image signatures.
  • Keep deployment, recovery, validation and any coupled SDK/audit pins coherent; retain historical negative fixtures where appropriate.
  • Existing targeted regressions and local/production rendering pass, including the declared Talos version for both roles.
  • Repair proven effective chart-template violations exposed by expanded validation, beginning with Crossplane's controller security settings; preserve runtime identities, explicit permissions and the existing admission policies, and verify native failing/passing render controls. Keep composition, mutation and admission-identity model gaps separate from configuration defects.
  • Make fresh-cache validation reproducible for the deployed Agent API: generate its missing local schema from the exact pinned kagent CRD chart, check reproducibility and rejected invalid input with native validation, and keep the complete manifest walk and schema enforcement intact.
  • Complete current-head CI and substantive review, then use the protected merge queue after recovery clearance.
  • Observe the actual deployed tool version, stable endpoint and current-main reconciliation before closing the slice.

No credentials, private addresses or production mutations belong in this source change.

Activity

  1. added theissue type on Nov 16, 2026
  2. coderabbitai commented on Nov 16, 2026

    @coderabbitai
    Contributor
    🔗 Related PRs

    #6168 - fix(talos): record the audited KSail 7.212.5 and 7.212.6 fold inputs [merged]


    📝 Issue Planner

    Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.

    • Create Plan

    🧪 Issue enrichment is currently in open beta.

    You can configure auto-planning by selecting labels in the issue_enrichment configuration.

    To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

    issue_enrichment:
      auto_enrich:
        enabled: false

    💬 Have feedback or questions? Drop into our discord!

  3. moved this to 🏃🏻‍♂️ In Progress in 🌊 Project Boardon Nov 16, 2026
  4. added 4 commits that reference this issue on Nov 16, 2026
  5. added a commit that references this issue on Nov 16, 2026
  6. added 4 commits that reference this issue on Nov 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Fields

    Priority

    None yet

    Effort

    None yet

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions