New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kill feature for containers spun up by the Google Batch Task Runner (GcpBatchTaskRunner) #3700
Labels
Milestone
Comments
fhussonnois
added a commit
to kestra-io/plugin-gcp
that referenced
this issue
May 14, 2024
fhussonnois
added a commit
to kestra-io/plugin-gcp
that referenced
this issue
May 14, 2024
fhussonnois
added a commit
that referenced
this issue
May 14, 2024
fhussonnois
added a commit
that referenced
this issue
May 14, 2024
anna-geller
changed the title
Kill feature for containers spun up by Task Runner
Kill feature for containers spun up by the Google Batch Task Runner (GcpBatchTaskRunner)
May 14, 2024
The priority is to tackle this for the Added separate issues for other providers to make sure we kill the infrastructure resources to avoid unnecessary costs for the user:
|
fhussonnois
added a commit
that referenced
this issue
May 14, 2024
fhussonnois
added a commit
that referenced
this issue
May 14, 2024
fhussonnois
added a commit
to kestra-io/plugin-gcp
that referenced
this issue
May 14, 2024
fhussonnois
added a commit
to kestra-io/plugin-gcp
that referenced
this issue
May 14, 2024
fhussonnois
added a commit
to kestra-io/plugin-gcp
that referenced
this issue
May 15, 2024
fhussonnois
added a commit
to kestra-io/plugin-azure
that referenced
this issue
May 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature description
Currently, Containers spun up by a task runner will run till completion even if the Kestra server would fail or when execution would be killed.
The text was updated successfully, but these errors were encountered: