Open hno2 opened 5 years ago
The script is run with "set -e", which should show any error. This feels like a silent error in the underlying kfctl.sh script. That script is evolving into a go binary. Let's wait until that work is done and we'll integrate with that, hopefully in the 0.5.0 timeframe.
What kind of proxy are you running?
Thanks for your answer. Is there a fixed release cycle for kubeflow or a planned release date for 0.5.0 already? The Proxy I use is a custom CNTLM-Proxy, wich somehow always stops working in the middle of running the script. (Pulling and wget works fine, but pulling the swagger.json from GitHub fails)
While trying to deploy I noticed that the install script sometimes fails silently. Running
./install-kubeflow.sh
stopped after "Creating Kubeflow app directory:<>" without any errors. After debugging I found out that somehow my proxy stopped. Therefore the s pull for the swagger.json from GitHub in https://github.com/canonical-labs/kubeflow-tools/blob/d5e73b3cbed70891caf071e9417bf1e2651d2d49/install-kubeflow.sh#L85 didn't work. Is there any way to not silently fail here?(Running the it again brought up:
ERROR could not finde component: extracting module and component names from ambassador...
)