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 Nov 15, 2022. It is now read-only.
When attempting to run kedge apply without kubectl in PATH, it would appear that kedge "falls back" to looking for the oc (OpenShift) client. Instead of providing a useful error message such as "kubectl was not found, please install kubectl and add it to your path", the user is told simply that the oc command couldn't be found, as though that's a kedge dependency.
This, in my opinion, is poor error handling and it's done so using a non-standard fall-back. The appropriate message should instruct the user to resolve the missing kubectl dependency and nothing more. Introducing a dependency on oc, and the subsequent message around oc missing, leads the user to believe that oc is fundamentally required for kedge to work.
'oc' should never have been introduced as the fallback, and should be taken out.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When attempting to run
kedge apply
without kubectl in PATH, it would appear that kedge "falls back" to looking for the oc (OpenShift) client. Instead of providing a useful error message such as "kubectl was not found, please install kubectl and add it to your path", the user is told simply that the oc command couldn't be found, as though that's a kedge dependency.This, in my opinion, is poor error handling and it's done so using a non-standard fall-back. The appropriate message should instruct the user to resolve the missing kubectl dependency and nothing more. Introducing a dependency on oc, and the subsequent message around oc missing, leads the user to believe that oc is fundamentally required for kedge to work.
'oc' should never have been introduced as the fallback, and should be taken out.
The text was updated successfully, but these errors were encountered: