kubectl get all does not list all resources in a namespace

[tback]

Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see http://kubernetes.io/docs/troubleshooting/.):

What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.):
get all, get all resources

---

Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT

Kubernetes version (use kubectl version):
Client Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.2", GitCommit:"bdaeafa71f6c7c04636251031f93464384d54963", GitTreeState:"clean", BuildDate:"2017-10-24T19:48:57Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"8+", GitVersion:"v1.8.2-gke.0", GitCommit:"52ea03646e64b35a5b092ab32bb529400c296aa6", GitTreeState:"clean", BuildDate:"2017-10-24T23:31:18Z", GoVersion:"go1.8.3b4", Compiler:"gc", Platform:"linux/amd64"}

Environment:

• Cloud provider or hardware configuration:
  gke
• OS (e.g. from /etc/os-release):
  macos 10.12.6

What happened:
kubectl get all does not list all resources in a namespace.

What you expected to happen:
As a user performing kubectl get all I expect to see all objects in the current context, including limits.

How to reproduce it (as minimally and precisely as possible):

kubectl create namespace tmp
kubectl create -f https://k8s.io/docs/tasks/administer-cluster/memory-defaults.yaml --namespace=tmp
kubectl get all --namespace tmp
namespace "tmp" created
limitrange "mem-limit-range" created
No resources found.

[stewart-yu]

kubectl get all --namespace tmp is wrong, you may use kubectl get all --n tmp

[tback]

@stewart-yu: Double dash and short form (kubectl get all --n tmp) doesn't work!

Both variants below do work:
kubectl get all --namespace tmp
kubectl get all -n tmp

You can look that up in kubectl options:

...
-n, --namespace='': If present, the namespace scope for this CLI request
...

[stewart-yu]

/kind bug

[stewart-yu]

I will fix it ASAP

[stewart-yu]

cc @smarterclayton Described as above. We can not get limitRange for it is unknown objects?

[stewart-yu]

cc @fabianofranz

[fabianofranz]

As a user performing kubectl get all I expect to see all objects in the current context, including limits.

There are some rules about which resources must fall under "all", take a look here. Are the resources you want covered there?

[tback]

@fabianofranz: Yes, limits are covered there (Rule 2: No namespace admin level resources (limits, quota, policy, authorization rules)).

This leaves me frustrated though:

1. kubectl help get describes kubectl get all as List all resources with different types. so I think I am right to expect all resources to be listed.
2. It might be ok if adminstrative resources are hidden from a normal user. As a cluster admin I need an easy way to see everything in a namespace to decide if i can delete it or not.

[smarterclayton]

There's an open issue for that - I'd like to see it solved, but it requires some other work to happen because there are resources that exist, but aren't deletable.

…

On Thu, Nov 30, 2017 at 10:06 AM, Till Backhaus ***@***.***> wrote: Yes, limits are covered there (Rule 2: No namespace admin level resources (limits, quota, policy, authorization rules)). This leaves me frustrated though: 1. kubectl help get describes kubectl get all as List all resources with different types. so I think I am right to expect *all* resources to be listed. 2. It might be ok if adminstrative resources are hidden from a normal user. As a cluster admin I *need* an easy way to see *everything* in a namespace to decide if i can delete it or not. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#151 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABG_pyQoDwAuOBgKu-aylMQzae2yPZZZks5s7sR1gaJpZM4QtFDB> .

[tback]

@smarterclayton can you provide a link to the issue?

I'm not concerned about kubernetes not deleting a namespace when I issue kubectl delete namespace <namespace>. I've never seen that happen.

I'm concerned about the user interface issue. I expect to be able to list everything (preferrably via kubectl get all, but an alternative command might be ok aswell), so I can make an informed decision.

To me this is the same as being the admin of a linux box without ls -a. On that box I might forget to backup everything that is hidden (including my .profile, and .ssh private keys). In both cases (kubectl and linux box) I'm setting myself up for desaster because it becomes very likely that I loose data at some point in the future.

[HartS]

I'd like to see a documentation improvement, as well as a new 'type' to use to actually show all resources in a namespace, as the current meaning of all is both unintuitive and not documented anywhere. Just fixing kubectl wouldn't help users figure out what's going on for older versions, so I think a new name (everything ?) would be helpful for retaining consistency with older client versions.

Currently I know that all doesn't refer to the following types of resources:

• resources which are not namespace (this makes sense... though with --all-namespaces it might be useful to include these): clusterrolebindings, clusterroles, etc.
• configmaps
• rolebindings
• roles

all does refer to the following types of (namespaced) resources:

• pods (though completed pods are still omitted without --show-all
• services
• replicasets
• deployments

This is only a partial list, as I have no way of knowing what are kinds of resources are listed by all

I think there needs to be better documentation around resources in general, and a better explanation of the magic all resource pseudo-type.

[joaosousafranco]

Same issue here. Its returning only deployments, replicasets and pods

[mengqiy]

Ref: https://github.com/kubernetes/community/blob/master/contributors/devel/kubectl-conventions.md#rules-for-extending-special-resource-alias---all

We may want to explain all in the help text.