Channels
announcements
ask-the-community
auth
conference-talks
contribute
databricks-integration
datahub-flyte
deployment
ecosystem-unionml
engineeringlabs
events
feature-discussions
flyte-bazel
flyte-build
flyte-console
flyte-deployment
flyte-documentation
flyte-github
flyte-on-gcp
flyte-ui-ux
flytekit
flytekit-java
flytelab
great-content
hacktoberfest-2022
helsing-flyte
in-flyte-conversations
integrations
introductions
jobs
konan-integration
linkedin-flyte
random
ray-integration
ray-on-flyte
release
scipy-2022-sprint
show-and-tell
sig-large-models
torch-elastic
workflow-building-ui-proj
writing-w-sfloris
Powered by
Title
p
Padma Priya M
12/22/2022, 1:52 PM
In version 0.3.0, while running the basic ray task mentioned in the documentation
https://docs.flyte.org/projects/cookbook/en/latest/auto/integrations/kubernetes/ray_example/ray_example.html
, the pods were getting up and running but the execution got queued in the console until we terminate manually.
k
Kevin Su
12/23/2022, 1:24 AM
yes, in some cases, propeller didn’t delete the cluster. will fix it
#ray-integration
Join Slack