Tommy Li

The result file path should be available in the Tekton core controller as a variable `$(results.resultname.path)`. We just need a lightweight container that pushes these results to some object storages...

@ScrapCodes Here is the possible sidecar issue https://github.com/tektoncd/pipeline/issues/1347 Tekton's current Sidecar implementation contains a bug. Tekton uses a container image named nop to terminate Sidecars. That image is configured by...

Thanks @ScrapCodes for your feedback on the sidecar, do you think having a post-processing step can avoid these issues?

I will open another issue once I find a way to fix it in Tekton. This issue is for fixing the parameter validation.

So looks like the Tekton compiler and Argo have difference issue. For Tekton I opened a new issue #599 for fixing the loop custom task location. The Argo error generated...

/close

Currently you have to create the Tekton loop resources before calling the `create_run_from_pipeline_func` function. To generate the loop resources, you can run the first part of the nested loop instruction...

On 0.6.0, the nested loop feature wasn't implemented, so you are probably running an incomplete pipeline. This issue should be fixed in the upcoming kfp-tekton 0.9.0 as we are working...

As for now, you have to follow this instruction to generate the Tekton resources separately because we just added the inline enhancement to the Tekton community few weeks ago in...

FYI this issue should be fixed if you run with our 0.9.0 kfp-tekton release with Tekton 0.25+ https://github.com/kubeflow/kfp-tekton/blob/master/guides/kfp_tekton_install.md#standalone-kubeflow-pipelines-with-tekton-backend-deployment