Skip to content

[PR-10] Cluster-Scoped Cruise Control Operation Retrieval #378

Closed as not planned
Closed as not planned

Description

@amuraru

Delivery bundle: C: Convergence, APIs, and gated scalability. See #395 and #368 for the four-PR stack.

Parent: #393
Roadmap: #368
Plan item: PR-10
Priority: P2
Dependencies: PR-07

Kubernetes support: Rolling upstream-maintained minors; use the oldest/newest boundaries pinned in config/kubernetes-versions.env. See #368 for the current policy. Unrun jobs are not passed validation.

Problem Statement

Evidence: controllers/cruisecontroloperation_controller.go:86-100 directly lists all namespace operations before identifying the requested object, then filters again by KafkaCluster.

Proposed Solution

Files: That controller and tests, pkg/k8sutil/cache.go if a cache index is needed, and related operation-label helpers.

Interface contract: Fetch the requested operation first, resolve its KafkaCluster, then retrieve the required operation set for that cluster. A server-side label selector is different from a cache-only field index; do not send unsupported arbitrary field selectors to the API server.

  • Add a test with unrelated clusters and completed history; assert unrelated objects cannot influence execution selection.
  • Assert fresh reads are retained at execution-critical boundaries and operation scheduling order is unchanged.
  • Implement label-scoped direct retrieval or indexed cached retrieval with explicit fresh-read boundaries.
  • Validate with go test ./controllers ./controllers/tests; benchmark increasing unrelated history and compare list bytes, scan counts, and reconcile latency.

Done when: Work scales with relevant operations rather than all operations in the namespace.

Delivery: Four consolidated PRs, approved November 16, 2026: A -> B -> C; D branches from A. Foundation is #395. The 22 PR-XX identifiers are work-item IDs, not separate PRs. Preserve every work-item acceptance criterion and native dependency. No gated experiment is automatically enabled, and no issue is complete merely because one PR references it. D must satisfy its native #375 gate, including lifecycle-domain signals assigned to B; branching from A does not waive that merge prerequisite. Write focused regression tests first; record exact commands/results and run make check plus this issue's real-cluster/measurement gates.

Alternatives Considered

Twenty-two individual PRs add unnecessary integration overhead, while one omnibus PR obscures correctness and rollout boundaries. Deliver this scope in its approved dependency-aligned bundle. Do not expand into deferred consistency, storage, or concurrency changes without their own decision gates.

Additional Context

Baseline: 95138e0d; detailed roadmap scope: #368, section PR-10. The roadmap #368 and its native sub-issues are the planning source of truth. No planning document is committed in the final PR diffs. Re-read affected source and overlapping work before implementation. Historical baseline test passes are not validation of this change.

Activity

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

    @amuraru
    Author

    Operation-retrieval efficiency is consolidated into evidence-gated #393 under #368. Measure unrelated-history cost before implementing; preserve scheduling/freshness. Superseded, not implemented.

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

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions