Release v0.1.0

As far as I can tell, dagster-ray' s functionality has been quite stable for a while. The only thing keeping dagster-ray from graduating to 0.1.x was it's API -- it wasn't very polished and obviously required lots of improvements.

dagster-ray 0.1.0 comes with an better API for KubeRayCluster that's aligned with standard Kubernetes resources.

It also includes a bunch of new features, the main highlight being, of course, KubeRayInteractiveJob. This resource is a beast: it combines the slick UX of KubeRayCluster with convenient RayJob features such as timeouts, automatic cleanup, and the ability to target existing clusters (via clusterSelector).

KubeRayInteractiveJob is now the recommended way of running Ray applications in client mode on Kubernetes.

LifeCycleACtions(create=<bool>, wait=<bool>, connect=<bool>) options and .create(), .wait() and .connect() API brings more UX improvements: it makes it possible to lazily create RayCluster/RayJob and only wait for them to become ready once actually needed.

Breaking API changes are still expected in the future (I haven't got to Pipes yet!), but they are now guaranteed to happen only on minor version updates.

---

Changed

• [:bomb: breaking] RayResource: top-level skip_init and skip_setup configuration parameters have been removed. The lifecycle field is the new way of configuring steps performed during resource initialization. KubeRayCluster's skip_cleanup has been moved to lifecycle as well.
• [:bomb: breaking] injected dagster.io/run_id Kubernetes label has been renamed to dagster/run-id. Keys starting with dagster.io/ have been converted to dagster/ to match how dagster-k8s does it.
• [:bomb: breaking] dagster_ray.kuberay Configurations have been unified with KubeRay APIs.
• dagster-ray now populates Kubernetes labels with more values (including some useful Dagster Cloud values such as git-sha)

Added

• KubeRayInteractiveJob -- a new resource that utililizes the new InteractiveMode for RayJob. It can be used to connect to Ray in Client mode -- like KubeRayCluster -- but gives access to RayJob features, such as automatic cleanup (ttlSecondsAfterFinished), retries (backoffLimit) and timeouts (activeDeadlineSeconds).
• RayResource setup lifecycle has been overhauled: resources now has an actions parameter with 3 configuration options: create, wait and connect. The user can disable them and run .create(), .wait() and .connect() manually if needed.

Full Changelog: v0.0.23...v0.1.0

Release v0.1.0-alpha.0

This is a pre-release for dagster-ray 0.1.0. It's available for testing.

I want to merge #193 before releasing 0.1.0. There are no other API changes planned (currently).

🔧 Changed

• 💣 breaking: RayResource: top-level skip_init and skip_setup configuration parameters have been removed. The lifecycle field is the new way of configuring steps performed during resource initialization. KubeRayCluster's skip_cleanup has been moved to lifecycle as well.
• 💣 breaking: injected dagster.io/run_id Kubernetes label has been renamed to dagster/run-id. Keys starting with dagster.io/ have been converted to dagster/ to match how dagster-k8s does it.
• 💣 breaking: dagster_ray.kuberay configurations have been unified with KubeRay APIs.
• dagster-ray now populates Kubernetes labels with more values (including some useful Dagster Cloud values such as git-sha)

✨ Added

• KubeRayInteractiveJob -- a new resource that utilizes the new InteractiveMode for RayJob. It can be used to connect to Ray in Client mode -- like KubeRayCluster -- but gives access to RayJob features, such as automatic cleanup (ttlSecondsAfterFinished), retries (backoffLimit) and timeouts (activeDeadlineSeconds).
• RayResource setup lifecycle has been overhauled: resources now has an actions parameter with 3 configuration options: create, wait and connect. The user can disable them and run .create(), .wait() and .connect() manually if needed.

Full Changelog: v0.0.23...v0.1.0-alpha.0

Release v0.0.23

What's Changed

• ⬆️ support Dagster 1.11.6 by @geoHeil in #181
• 🐛 fix early exiting raycluster readiness waiting loop by @danielgafni in #182

Full Changelog: v0.0.22...v0.0.23

Release v0.0.22

What's Changed

• fix: fix typos by @geoHeil in #164
• 🐛 retry urllib3.exceptions.ProtocolError when streaming k8s events by @danielgafni in #172

New Contributors

• @geoHeil made their first contribution in #164

Full Changelog: v0.0.21...v0.0.22

Release v0.0.21

What's Changed

• Improve KubeRayCluster cleanup by @photoroman in #149 - thanks!

New Contributors

• @photoroman made their first contribution in #149

Full Changelog: v0.0.20...v0.0.21

Release v0.0.20

What's Changed

• fix profiling option by @danielgafni in #143
• 🔊 log cluster conditions while waiting for readiness by @danielgafni in #144
• ✅ update testing matrix to include KubeRay 1.4.0 and Dagster 1.11.1 without ray 2.47.0 by @danielgafni in #146

Full Changelog: v0.0.19...v0.0.20

Release v0.0.19

What's Changed

• 🐛 fix hangs during log reading (Dagster steps do not complete) by @danielgafni in #136 --- thanks @serriaguirregaray !

Full Changelog: v0.0.18...v0.0.19

Release v0.0.18

What's Changed

• ♻️ rename client -> kuberay_client resource by @danielgafni in #108
• 🧪 test with dagster 1.10.12 by @danielgafni in #120
• ✨ [pipes] attach metadata and improve message/log reading by @danielgafni in #119

Full Changelog: v0.0.17...v0.0.18

Release v0.0.17

What's Changed

• 📖 correct no cleanup message by @danielgafni in #103
• 🐛 trim bad characters from the beginning of k8s labels by @danielgafni in #104

Full Changelog: v0.0.16...v0.0.17

Release v0.0.16

What's Changed

• ✨ add debugging options by @danielgafni in #102
• 🔧 remove backticks in kubectl log by @danielgafni in #99

Full Changelog: v0.0.15...v0.0.16