{"action":"opened","issue":{"url":"https://api.github.com/repos/GoogleCloudPlatform/kubernetes/issues/10516","labels_url":"https://api.github.com/repos/GoogleCloudPlatform/kubernetes/issues/10516/labels{/name}","comments_url":"https://api.github.com/repos/GoogleCloudPlatform/kubernetes/issues/10516/comments","events_url":"https://api.github.com/repos/GoogleCloudPlatform/kubernetes/issues/10516/events","html_url":"https://github.com/GoogleCloudPlatform/kubernetes/issues/10516","id":91939205,"number":10516,"title":"`kubectl config view --minify` needs a top-level alias","user":{"login":"mbforbes","id":1170062,"avatar_url":"https://avatars.githubusercontent.com/u/1170062?v=3","gravatar_id":"","url":"https://api.github.com/users/mbforbes","html_url":"https://github.com/mbforbes","followers_url":"https://api.github.com/users/mbforbes/followers","following_url":"https://api.github.com/users/mbforbes/following{/other_user}","gists_url":"https://api.github.com/users/mbforbes/gists{/gist_id}","starred_url":"https://api.github.com/users/mbforbes/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mbforbes/subscriptions","organizations_url":"https://api.github.com/users/mbforbes/orgs","repos_url":"https://api.github.com/users/mbforbes/repos","events_url":"https://api.github.com/users/mbforbes/events{/privacy}","received_events_url":"https://api.github.com/users/mbforbes/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/GoogleCloudPlatform/kubernetes/labels/team/UX","name":"team/UX","color":"d2b48c"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-06-30T00:04:15Z","updated_at":"2015-06-30T00:04:15Z","closed_at":null,"body":"Here's the question I want to answer: when I use kubectl, what cluster am I talking to?\r\n\r\nAs a developer with several clusters, this is a really important question to me.\r\n\r\nI was looking through `kubectl config --help` and I saw the options are:\r\n\r\n```\r\n  view            displays Merged kubeconfig settings or a specified kubeconfig file.\r\n  set-cluster     Sets a cluster entry in kubeconfig\r\n  set-credentials Sets a user entry in kubeconfig\r\n  set-context     Sets a context entry in kubeconfig\r\n  set             Sets an individual value in a kubeconfig file\r\n  unset           Unsets an individual value in a kubeconfig file\r\n  use-context     Sets the current-context in a kubeconfig file\r\n```\r\n\r\nOnly asking @jlowdermilk did I learn that `kubectl config view --minify` was what I wanted. This seems kind of crazy! `--minify`? To see my current context?\r\n\r\n@bgrant0607 how would you feel about one of the following options?\r\n\r\n0. Top-level \"GET\" analogs for the \"PUT\" methods (get-cluster, get-credentials, get-context, ...)\r\n0. Have `kubectl config view` output *only* the current context by default, and have a flag like `--full` for the full config (rather than having to pass `--minify` for the current context).\r\n\r\n(Leaving this for oncall and @bgrant0607 to determine priority.)"}}