You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 10, 2023. It is now read-only.
The context create workflow involving supplying a kubeconfig context can leverage conventions on location of the default kubeconfig file and the active context in the kubeconfig, to minimize the amount of user input is the common cases.
e.g.
Prepopulate default standard kube config location
? Select context creation type Local kubeconfig
? Enter path to kubeconfig (~/.kube/config) /Users/dfein/.kube/config
Kube context selector
? Select context creation type Local kubeconfig
? Enter path to kubeconfig (~/.kube/config) /Users/dfein/.kube/config
? Enter kube context to use
> default
name one
second name
this would help with long kube context names
option to create tanzu context from currently active kube config/context
? Select context creation type Local kubeconfig
? Enter path to kubeconfig (~/.kube/config) /Users/dfein/.kube/config <enter>
? Select context creation type Local kubeconfig <enter>
would save having to specify kube config / context
Describe alternative(s) you've considered
Affected product area (please put an X in all that apply)
( ) APIs
( ) Addons
(X) CLI
( ) Docs
( ) IAM
( ) Installation
( ) Plugin
( ) Security
( ) Test and Release
(X) User Experience
( ) Developer Experience
Additional context
The text was updated successfully, but these errors were encountered:
Describe the feature request
The context create workflow involving supplying a kubeconfig context can leverage conventions on location of the default kubeconfig file and the active context in the kubeconfig, to minimize the amount of user input is the common cases.
e.g.
Describe alternative(s) you've considered
Affected product area (please put an X in all that apply)
Additional context
The text was updated successfully, but these errors were encountered: