💡[COMMAND REQUEST] Multi-Cluster Support for create, read, apply, and logs #31

Activity

1. oorrja

   added

   enhancementNew feature or requestNew feature or request

   on Jul 21, 2025
2. clubanderson commented on Aug 27, 2025

   

   clubanderson

   on Aug 27, 2025

   Member

   More actions

   /help-wanted
3. github-actions

   added

   help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.

   on Aug 27, 2025
4. clubanderson

   added

   kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.

   on Jan 13, 2026
5. Om-Beast commented on Jul 20, 2026

   

   Om-Beast

   on Jul 20, 2026

   More actions

   Hi @oorrja,

   I'd like to work on this enhancement.

   Before starting implementation, I plan to review the existing kubectl multi command architecture to understand how multi-cluster operations are currently handled and identify the common execution path that can be reused across commands.

   My approach would be to:

   • Design a reusable execution flow for multi-cluster command dispatch rather than duplicating logic for each verb.
   • Ensure results from multiple clusters are aggregated consistently while preserving cluster-specific context.
   • Keep the implementation aligned with the project's recommendation of using label-based binding policies, avoiding changes that encourage direct multi-cluster apply as the primary workflow.
   • If the scope is too large for a single PR, I'm happy to split the work into smaller incremental changes based on your guidance.

   If this issue is still available, I'd be glad to work on it. Please let me know if there's any preferred implementation approach or if you'd like the work broken into multiple PRs.