This message was deleted.

I'm not seeing this behavior in 2.8.0, but it could be a couple of things. Does the namespace filter in the top navigation have the same namespace selected where your secrets or configmaps are located? It could also be that your user doesn't have the permissions to view secrets or configmaps, or perhaps even the permission to manage workloads. I'm curious if you edit your existing deployment as yaml does the secret name show up correctly?