[Feature Request]: human readable MO cluster/component summary

[aylei]

Is there an existing issue for the same feature request?

• I have checked the existing issues.

Is your feature request related to a problem?

Currently, when viewing the summary of MO cluster/component via kubectl get or kubectl get -owide, the information is not clear and helpful.

k -n e2e-1687663318377408000 get mo
NAME   LOG   DN    TP    AP    VERSION            PHASE   AGE
test   3     1                 nightly-d15e37b5   Ready   13m
k -n e2e-1687663318377408000 get mo -owide
NAME   LOG   DN    TP    AP    VERSION            PHASE   UI    AGE
test   3     1                 nightly-d15e37b5   Ready         22m
k -n e2e-1687663318377408000 get cnset
NAME      IMAGE                                     REPLICAS   AGE
test-tp   matrixorigin/matrixone:nightly-d15e37b5   2          22m
k -n e2e-1687663318377408000 get cnset -owide
NAME      IMAGE                                     REPLICAS   AGE
test-tp   matrixorigin/matrixone:nightly-d15e37b5   2          22m

Describe the feature you'd like

When viewing the summary of MO cluster/component via kubectl get

1. the replicas should distinguish desired replicas and current available replicas;
2. the summary should always indicate whether the cluster/component is ready or not;
3. get -owide should print more informative messages, especially cpu/memory/storage resources of each Pod;

Example goes below:

k -n e2e-1687663318377408000 get mo
NAME   LOG     DN      CN    VERSION            PHASE   AGE
test   3/3     1/1     5/5   nightly-d15e37b5   Ready   13m

k -n e2e-1687663318377408000 get mo
NAME   LOG     DN      CN    VERSION            PHASE      AGE
test   3/3     1/1     5/5   nightly-d15e37b5   NotReady   13m

k -n e2e-1687663318377408000 get mo -owide
NAME   LOG     DN      CN    VERSION            PHASE      REASON                  AGE
test   3/3     1/1     4/5   nightly-d15e37b5   NotReady   CNGroup A is not Ready  13m

Describe implementation you've considered

No response

Documentation, Adoption, Use Case, Migration Strategy

No response

Additional information

No response