-
Notifications
You must be signed in to change notification settings - Fork 34
Open
Labels
Feature EnhancementEnhancing an existing feature driven by business requirements. Typically backwards compatible.Enhancing an existing feature driven by business requirements. Typically backwards compatible.Pending TriageNew issue that needs to be triaged by the teamNew issue that needs to be triaged by the team
Description
Feature to Enhance
Rather than relying on system kubectl, Solo should fall back to a managed toolchain inside ~/.solo/ when needed.
Requested Enhancement
If kubectl is missing or fails the non-interactive runnable check, Solo downloads and uses ~/.solo/bin/kubectl.
Business Need
This affects any windows WSL2 user or Linux user who attempts to install solo using brew (the recommended method now) and doesn't have kubeCTL when they attempt the solo one shot deploy.
If our goal is a flawless first experience with Solo this is an important error path to eliminate.
Additional Context
Repro steps
Remove kubectl OR make it interactive.
Run solo one-shot single deploy.
Verify Solo installs and uses its own kubectl and continues.
Metadata
Metadata
Assignees
Labels
Feature EnhancementEnhancing an existing feature driven by business requirements. Typically backwards compatible.Enhancing an existing feature driven by business requirements. Typically backwards compatible.Pending TriageNew issue that needs to be triaged by the teamNew issue that needs to be triaged by the team