-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Visualize Kruise Rollout progress with kruise-tools command #94
Comments
Hey @furykerry I have gone through the problem statement and find it quite interesting. I am keen to take on this project as part of the LFX mentorship program. Before starting, I would like to create a detailed proposal that outlines my thoughts and plans to address this issue comprehensively. |
Hello @furykerry I am kairvee and am interested to work over this issue under the LFX mentorship program , Please let me know so that I can further create a proposal for it . |
Hi @vinayakjaas would you like to explain the detail information about LFX mentorship program? |
Hey everyone! I'm Nihit, a pre-final year student from the Indian Institute of Information Technology, Gwalior, majoring in Information Technology. I'm a tech enthusiast with a strong passion for open-source. I've applied for this project and have been working on this issue for some time now. I would greatly appreciate any guidance or clarity on how best to approach this issue. I'm really looking forward to solving this problem and contributing to the project as much as possible. |
Currently kubectl get rollout only display exposed rollout status as columns, however it is vital to display the status of all involved objects as well, e.g. pods, traffic routings objects. So kruise-tools can provide a deep inspection command, in the form of
kubectl kruise describe rollout ns/name
, and provide the following information:In addition, the new describe command should support a watch option, to dynamically update the output during the rollout.
One can use the Argo kubectl plugin as a reference
The text was updated successfully, but these errors were encountered: