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
I tried running Kale against plain Kubeflow and hit authentication issues. When I asked Arrikto pre-sales about this, I was told that Kale now depends on EKF to make Kubeflow compatible with Kale. Assuming all that is correct, it seems like the Readme should be updated to clearly state this dependency. Otherwise, people running without EKF will waste their time getting to a dead end.
Also, I don't really see a roadmap anywhere for Kale. And I note the code contributions to Kale have slowed dramatically. Has something about the commitment to this project changed that prospective users should be made aware of?
The text was updated successfully, but these errors were encountered:
It's been more than 30 days, so I guess that constitutes a tacit acknowledgement that unfortunately, yes, the commitment level to this project has changed...
It's been more than 30 days, so I guess that constitutes a tacit acknowledgement that unfortunately, yes, the commitment level to this project has changed...
This project is officially dead. No roadmap no updates. Progress happening only in Arrikto enterprise.
Folks looking for alternatives might want to check out Elyra. Visual editor where notebooks become pipeline nodes (rather than specific cells). It works pretty well from limited experience...
I tried running Kale against plain Kubeflow and hit authentication issues. When I asked Arrikto pre-sales about this, I was told that Kale now depends on EKF to make Kubeflow compatible with Kale. Assuming all that is correct, it seems like the Readme should be updated to clearly state this dependency. Otherwise, people running without EKF will waste their time getting to a dead end.
Also, I don't really see a roadmap anywhere for Kale. And I note the code contributions to Kale have slowed dramatically. Has something about the commitment to this project changed that prospective users should be made aware of?
The text was updated successfully, but these errors were encountered: