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
If we check, we always execute config show after a config import. I started thinking that we should automatically print the imported data in the config import (maybe with a --quiet flag). Also for the documentation, it makes things more consistent. For instance:
Import node info:
kubectl aks config import
Run command against one of the nodes:
kubectk aks run-command --node <myNode>
Users will take the node name from the previous config import output, they we don't need to ask them to also run config show.
The text was updated successfully, but these errors were encountered:
Originally posted by @blanquicet in #52 (comment):
If we check, we always execute
config show
after aconfig import
. I started thinking that we should automatically print the imported data in theconfig import
(maybe with a--quiet
flag). Also for the documentation, it makes things more consistent. For instance:Import node info:
Run command against one of the nodes:
Users will take the node name from the previous
config import
output, they we don't need to ask them to also runconfig show
.The text was updated successfully, but these errors were encountered: