Repository navigation
⏳[PERFORMANCE]: multi rollout status timeout #23
Description
Performance Metric
Time out of current context output:
Command Executed
kubectl multi rollout status deployment/my-deploy
Execution Time
Timeout
Resource Usage
No response
Number of Clusters
CURRENT NAME CLUSTER AUTHINFO NAMESPACE
-
cluster1 kind-cluster1 kind-cluster1 cluster2 kind-cluster2 kind-cluster2 its1 its1-cluster its1-admin kind-kubeflex kind-kubeflex kind-kubeflex kind-nonkubestellar kind-nonkubestellar kind-nonkubestellar kind-nonkubestellar1 kind-nonkubestellar1 kind-nonkubestellar1 wds1 wds1-cluster wds1-admin default
Baseline Comparison
N/A
Steps to Reproduce
Switch into kubestellar cluster. Run kubectl multi rollout status deployment/my-deploy
System Information
No response
Additional Context
No response
Activity
Om-Beast commentedon Jul 20, 2026
Hi @gauri-sharmaa,
I'd like to investigate this issue.
My plan is to first reproduce the timeout in a local multi-cluster KubeStellar environment and trace the execution path of
kubectl multi rollout statusto determine whether the timeout is caused by rollout status polling, context cancellation, concurrency synchronization, or handling of one or more cluster responses.Once I can reliably reproduce the behavior, I'll identify the root cause, implement a focused fix, and add a regression test (if applicable) to prevent similar timeout regressions in the future.
If no one is actively working on this issue, I'd be happy to take it on and submit a PR.