Code change:
<!-- Thanks for filing an issue! Before hitting the button, please answer these questions.--Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see ): What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.): Is this a BUG REPORT or FEATURE REQUEST? (choose one): <!-- If this is a BUG REPORT, please: Fill in as much of the template below as you can. If you leave out information, we can't help you as well. If this is a FEATURE REQUEST, please: Describe in detail the feature/behavior/change you'd like to see. In both cases, be ready for followup questions, and please respond in a timely manner. If we can't reproduce a bug or think a feature already exists, we might close your issue. If we're wrong, PLEASE feel free to reopen it and explain why. --BUG REPORT Kubernetes version (use ): Client Version: version.Info{Major:"1", Minor:"6+", GitVersion:"v1.6.0-beta.3", GitCommit:"", GitTreeState:"clean", BuildDate:"2017-03-11T04:20:22Z", GoVersion:"go1.7.5", Compiler:"gc", Platform:"darwin/amd64"} Server Version: version.Info{Major:"1", Minor:"5", GitVersion:"v1.5.4", GitCommit:"", GitTreeState:"clean", BuildDate:"2017-03-07T23:34:32Z", GoVersion:"go1.7.4", Compiler:"gc", Platform:"linux/amd64"} Environment: Cloud provider or hardware configuration: OS (e.g. from /etc/os-release): Kernel (e.g. ): Install tools: Others: What happened: With kubectl version 1.6.0-beta.3, the output of is not aligned: What you expected to happen: With kubectl version 1.5.4, the output is as follows: How to reproduce it (as minimally and precisely as possible): Run using kubectl version 1.6.0-beta.3. Anything else we need to know:
will take a look
any progress on this?
hi, tony, sorry, I haven't look at this problem yet, maybe tomorrow, just really busy recent day, you can take it if you already find the problem, thanks
Happened to see the same issue on my laptop, I can help fix this issue if you do not have time, thx
thanks, I've been really busy this week, go ahead
for this ticket, want to discuss one more thing with you: at present, for each of the update event, command with option will print out a line showing the status change of this event. But this behavior is different with what we saw from the output of linux's command, which I think is not a very good user experience. For this kind of command, we shall reset all the old output and re-print all the pod's information in the standard output, this will make this command more like a real command. do we have any plans on this right now? welcome your ideas on this.
I think both output format has it's advantage, for current output format, user can copy paste the whole information like checking logs, for linux's command style output which user can stare on only one screen(if it's not too many pods or sth else).
yep, we do have plan to do this, and I really like a more linux style command, you can refer for more detail. Anyway let's just get this fixed at first.

Related discussion:
text: // print the current object if !isWatchOnly { var objsToPrint []runtime.Object <ins> writer := printers.GetNewTabWriter(out) </ins> if isList { objsToPrint, _ = meta.ExtractList(obj) } else { objsToPrint = append(objsToPrint, obj) } for _, objToPrint := range objsToPrint { <del> if err := printer.PrintObj(objToPrint, out); err != nil { </del> <ins> if err := printer.PrintObj(objToPrint, writer); err != nil { </ins> return fmt.Errorf("unable to output the provided object: %v", err) } } <ins> writer.Flush() </ins> } // print watched changes