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

Improve human-readable output of Deployments and StatefulSets #68623

Open
juanvallejo opened this Issue Sep 13, 2018 · 3 comments

Comments

Projects
None yet
4 participants
@juanvallejo
Member

juanvallejo commented Sep 13, 2018

The column output for Deployments, StatefulSets, and DaemonSets are not as helpful as the human-readable output for Pods (for example).

We need to reduce the number of columns that we use to inform about the current amount of replicas (for example) that are desired and have been fulfilled for these resources, and add a new column or two that give the user more information about the current state of a Deployment or StatefulSet, and the reason behind that state.

For example:

Before

NAME            DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
deployment1     1         1         1            0           4s

After

NAME            READY   STATUS             UP-TO-DATE   AVAILABLE  RESTARTS   AGE
deployment1     1/1     CrashLoopBackOff   1            0          2          4s 

What is expected:

Improve the human-readable output in kubectl get for the following resources:

  • DaemonSets
  • StatefulSets
  • Deployments

cc @soltysh @smarterclayton

@juanvallejo

This comment has been minimized.

Show comment
Hide comment
@juanvallejo

juanvallejo Sep 13, 2018

Member

/sig cli

Member

juanvallejo commented Sep 13, 2018

/sig cli

@k8s-ci-robot k8s-ci-robot added sig/cli and removed needs-sig labels Sep 13, 2018

@sahitpj

This comment has been minimized.

Show comment
Hide comment
@sahitpj

sahitpj Sep 13, 2018

May I work on this, if it hasn't been assigned yet?

sahitpj commented Sep 13, 2018

May I work on this, if it hasn't been assigned yet?

@soltysh soltysh assigned soltysh and juanvallejo and unassigned soltysh Sep 13, 2018

@juanvallejo

This comment has been minimized.

Show comment
Hide comment
@juanvallejo

juanvallejo Sep 13, 2018

Member

@sahitpj Sure, feel free to put together a pull for this. Please reach out on slack if you have any questions

Member

juanvallejo commented Sep 13, 2018

@sahitpj Sure, feel free to put together a pull for this. Please reach out on slack if you have any questions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment