You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What would you like to be added:
Currently, when using kubectl get with lws , there are only two fields displayed: name and age. We should provide more meaningful fields to make it more convenient to use.
root@VM-0-8-ubuntu:/home/ubuntu# kubectl get lws
NAME AGE
leaderworkerset-sample 5h21m
We should provide more meaningful fields, which will be more convenient to use
as follows:
root@VM-0-8-ubuntu:/home/ubuntu# kubectl get lws
NAME READY UP-TO-DATE AGE
leaderworkerset-sample 3/3 3 5h21m
There were some minor problems during implementation. FRY: kubernetes-sigs/kubebuilder#4134
I am not sure whether the current JSONPath of kubebuilder can achieve a display effect similar to (X/Y). In addition, should we add other useful fields (maybe we can also discuss this PR)? If not, I will close this issue
Why is this needed:
provide more meaningful fields Completion requirements:
This enhancement requires the following artifacts:
Design doc
API change
Docs update
The artifacts should be linked in subsequent comments.
The text was updated successfully, but these errors were encountered:
That's great, but there's a small problem. kubernetes-sigs/kubebuilder#4134 This problem can be solved by adding an extra field to the status, but I don't think this is a good way to handle it. Maybe we can wait until this problem is solved before implementing it
What would you like to be added:
Currently, when using kubectl get with lws , there are only two fields displayed: name and age. We should provide more meaningful fields to make it more convenient to use.
We should provide more meaningful fields, which will be more convenient to use
as follows:
There were some minor problems during implementation. FRY: kubernetes-sigs/kubebuilder#4134
I am not sure whether the current JSONPath of kubebuilder can achieve a display effect similar to (X/Y). In addition, should we add other useful fields (maybe we can also discuss this PR)? If not, I will close this issue
Why is this needed:
Completion requirements:
This enhancement requires the following artifacts:
The artifacts should be linked in subsequent comments.
The text was updated successfully, but these errors were encountered: