With the recent refactoring due to removing KUBECONFIG, kubectl script in $HOME/bin is no longer gettting created and hence direct reference to kubectl without a path prefix or getting it from "kubectl.dest" can result in "command not found" type errors.
With the recent refactoring due to removing KUBECONFIG, kubectl script in $HOME/bin is no longer gettting created and hence direct reference to kubectl without a path prefix or getting it from "kubectl.dest" can result in "command not found" type errors.