Skip to content

Restore capacity for the Longhorn maintenance rollout #6424

Open

Description

@devantler

🤖 Generated by the Agentic Engineer

The fresh, protected read-only census for #6073 reports insufficient declared memory for the additional storage manager needed during the maintenance rollout. The image selection must remain held until that prerequisite is restored.

Move the stateless Flux operator away from the constrained placement through the existing temporary migration headroom configuration. Preserve its resource requests, rolling availability and ordinary scheduling constraints; do not move stateful applications or add permanent capacity.

Acceptance:

  • Production rendering includes the scoped operator placement while preserving existing affinity and rollout safeguards.
  • The replacement operator becomes Ready and available without interrupting reconciliation; its live allocated requests and host headroom qualify.
  • A fresh, stable, protected read-only census reports declared overlap FIT on every storage node before fix(storage): select the approved Longhorn maintenance runtime #6401 advances.
  • Keep runtime adoption, benchmark, recovery and full volume migration acceptance separate.

Part of #6073

Activity

  1. self-assigned this
    on Nov 16, 2026
  2. coderabbitai commented on Nov 16, 2026

    @coderabbitai
    Contributor
    🔗 Related PRs

    #6396 - fix(storage): keep headroom for the runtime rollout [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 a commit that references this issue on Nov 16, 2026
  5. moved this from 🏃🏻‍♂️ In Progress to 👀 In Review in 🌊 Project Boardon Nov 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Fields

Priority

None yet

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions