TaskRun support stop/wait status

[withlin]

1. Support stop/wait status,which will stop/wait the taskrun pod

idea:

1. user set task spec status to stop/wait staus
2. have a CRD find out which machine the current taskrun pod is on.
3. and then get running container id.
4. excute kill -STOP ${pid} ,which the pod will be  hold (use daemonset).
5. when set task status is reruning will excute  kill -CONT ${pid}

Do you have any better ideas?

[withlin]

/cc @vdemeester @sbwsg

[vdemeester]

/kind feature

[ghost]

It would be good to know a bit more about the intended use case for this feature. Why do you want it?

Is it to support something like #2159 ?

In general I think we would not want the Pod hanging around consuming resources while the TaskRun is waiting. Ideally when a TaskRun begins waiting its resources are released so that other tasks can be scheduled while it's sleeping. When the TaskRun is told to continue it would spin up a new Pod at the point where it left off.

The use cases for this behaviour (that I know of) are often systems that run for 24 hours or more. Examples include:

• Manual Approvals that are performed by teams operating in different timezones
• Approvals that trigger actions which are not allowed on the last day of the week and so must wait until the start of the following week
• Canary analysis systems that observe metrics over a long period of time before making decisions
• Global rollouts that span multiple days

In all of these cases it would be much better if the TaskRun released its resources while in a paused state.

[laik]

we test pod during taskRun, send a stop signal to the container system pid, at this time, the process stops and does not take up the load. I let this be an effective way to control the transfer of resources. If there is a rerun function, it is even better.

[laik]

/cc @sbwsg

[ghost]

the process stops and does not take up the load

Curious about this - What state does the Pod enter into? Does Kubernetes release the resource quota it has set aside for the Pod?

[laik]

the process stops and does not take up the load

Curious about this - What state does the Pod enter into? Does Kubernetes release the resource quota it has set aside for the Pod?

the pod still running, but it doesn't work anymore, as we use fg/bg, my idea is to identify a paused state record in taskRun

[withlin]

/assign

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[vdemeester]

/remove-lifecycle stale

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[tekton-robot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

[tekton-robot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

[tekton-robot]

@tekton-robot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.