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
provide clearer error messages or instructions for users when local-dev-setup.sh failed
Why is this needed:
When running a command hack/local-dev-setup.sh with missing tools(such as without Docker or Kind or Kubectl) or version mismatch issues, the error log received is always the same and indicates a timeout waiting for the kubeconfig file Waiting for kubeconfig file /root/.kube/kurator-host.config and clusters kurator-host to be ready... [ERROR] Timeout waiting for file exist /root/.kube/kurator-host.config
This can be confusing and frustrating for users who are not familiar with the requirements of the command and the dependencies it relies on. It would be helpful to provide clearer error messages or instructions for users who encounter this issue.
The text was updated successfully, but these errors were encountered:
What would you like to be added:
provide clearer error messages or instructions for users when
local-dev-setup.sh
failedWhy is this needed:
When running a command
hack/local-dev-setup.sh
with missing tools(such as without Docker or Kind or Kubectl) or version mismatch issues, the error log received is always the same and indicates a timeout waiting for the kubeconfig fileWaiting for kubeconfig file /root/.kube/kurator-host.config and clusters kurator-host to be ready... [ERROR] Timeout waiting for file exist /root/.kube/kurator-host.config
This can be confusing and frustrating for users who are not familiar with the requirements of the command and the dependencies it relies on. It would be helpful to provide clearer error messages or instructions for users who encounter this issue.
The text was updated successfully, but these errors were encountered: