Closed RobinKa closed 2 years ago
Using the pns executor instead makes everything work as described here
kustomize build apps/pipeline/upstream/env/platform-agnostic-multi-user-pns | kubectl apply -f -
So I assume I made a mistake in my Docker setup? Although not much about docker is mentioned in the manifests readme.
Hello @RobinKa , you can switch over to emissary executor since that is going to be the default executor going forward. https://github.com/kubeflow/pipelines/issues/5714
Even with proper emissary executor , sometimes component will stuck
Hey, hope this is the right place to post this issue at. I'm new to Kubeflow and Kubernetes so please let me know what else would be useful to know.
Environment
Steps to reproduce
[Tutorial] DSL - Control structures
Terminating the run does nothing. I also tried running other pipelines and the result is the same.
Expected result
The pipeline step should complete and run the rest of the pipeline.
Materials and Reference
Setup on Ubuntu 20.04 server from scratch
kubectl get pods output
kubectl logs conditional-execution-pipeline-with-exit-handler-scjtr-3243716801 -c wait -n kubeflow-user-example-com
Step Events tab
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.