Change:
So I started using namespaces for the first time, and I ran: nothing was showing up...I was really confused, debugging stuff for 30+ minutes.. finally I was like, even tho this is really dumb, maybe they are behind a namespace, so I did: and finally my pods showed up. so yes there is: but this should really be the default, shouldn't it? You will save people a lot of time if you make this fix. tbh, this is a really crappy cli design in this case.
While this might sound like a good idea if you're running a single deployment with a few pods, once you start running multiple dozens of deployments and objects it starts to become less and less useful to have this become the default. I also suspect exposing all objects without specifying namespace is probably a non-goal. Namespaces were created for a reason which is to logically segment resources together. In my opinion, what you are suggesting just nullifies the entire purpose of namespaces.
I think this is more of a usability bug. kubectl get pods gives the list of all pods in default namespace.By default no pods are present in default namespace. So it does give a message saying No Resources found. Improving this message a little bit will be helpful like No Resources found in default namespace
/sig cli
I could implement this if that's alright with you !
sure, how about
We should wait for kubernetes members to comment if this change should be taken up
The title of this issue could use an update, if the priority has been shifted to improving the output of an empty namespace. Maybe it's early to claim the consensus seems to be that --all-namespaces should not be the default, but I personally agree that it shouldn't be. Take note of the shorthand , to make typing it a bit easier, or the option to to something other than to get around typing your namespace altogether.
:) IMHO, is innocent. But we could make the messages more clear. For example, will show also. And is a bit long, but a is too simple to describe our intent, "all namespaces of cluster or all some resource of some namespace", so puzzled. My conclusion: is competent, namespace is ok, making more clear message is enough.
"~" is already implemented as in , in . Not sure if I came across as suggesting a new shorthand or if I misread your comment, but for clarity's sake there it is.
the problem is that the nixos-rebuild command is not available on non-NixOS linux machines. However, the underlying issue is that if we run we get this error:

Discussion:
w.Flush() if trackingWriter.Written == 0 && !o.IgnoreNotFound && len(allErrs) == 0 { // if we wrote no output, and had no errors, and are not ignoring NotFound, be sure we output something <del> fmt.Fprintln(o.ErrOut, "No resources found.") </del> <ins> noResourcesFoundFormat := fmt.Sprintf("No resources found in %s namespace.", o.Namespace) fmt.Fprintln(o.ErrOut, noResourcesFoundFormat) </ins> } return utilerrors.NewAggregate(allErrs) }

if e, a := expected, buf.String(); e != a { t.Errorf("expectedn%vngotn%v", e, a) } <del> expectedErr := `No resources found. </del> <ins> expectedErr := `No resources found in test namespace. </ins> ` if e, a := expectedErr, errbuf.String(); e != a { t.Errorf("expectedErrn%vngotn%v", e, a)