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
In the pull request created for the above issue, certain improvements were discussed in the different error codes being returned during crc start. The ones discussed till now are:
Different error codes being returned will allow the user to ignore certain error codes (such as cluster unstable)
The cannot update kubeconfig message can be more descriptive for the user
Additional message about how to access the cluster can be added (like export KUBECONFIG=$HOME/.crc/machine/crc/kubeconfig or use oc --kubeconfig=$HOME/.crc/machine/crc/kubeconfig) to assist the user in debugging
The text was updated successfully, but these errors were encountered:
Follow up for: #4284
In the pull request created for the above issue, certain improvements were discussed in the different error codes being returned during
crc start
. The ones discussed till now are:cannot update kubeconfig
message can be more descriptive for the userThe text was updated successfully, but these errors were encountered: