Red Hat Bugzilla – Bug 1471160
use current context when logging in
Last modified: 2017-09-06 07:04:44 EDT
Description of problem: `oc` tool supports operation against multiple clusters. User can edit ~/.kube/config file to rename contexts to make them easier to remember. The issue is that when current context is for example `myeasyname` and the next day user performs `oc login` a new context is created with the default name `project/clustername/username`. So the user cannot anymore use `myeasyname` context unless user edits kubeconfig again. Version-Release number of selected component (if applicable): oc v3.6.124 How reproducible: always Steps to Reproduce: 1. oc login 2. rename context 3. wait credentials to expire 4. oc login Actual results: a new context is created and current context is the newly created context Expected results: the existing context is reused Additional info: I filed an issue about shell completion for --context option [1]. I think it is also very important for user experience working with multiple environments. [1] https://github.com/openshift/origin/issues/15184
I think a solution to this would be to have the `oc login` command acknowledge the global `--context` flag (if one is provided). That way, if it is a user's intent to actually have the default context with a default name be created on login, the command's current behavior remains unchanged. Origin PR: https://github.com/openshift/origin/pull/16161
Provided that `oc` uses current context server for the login command, then it makes sense to update current context. I think it only makes sense to create a new context when user changes `server` or `user` when logging in.