Skip to content

docs(pipelines): Add troubleshooting tip for standalone Pipelines installation #4084

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.

Sign up for GitHub

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

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

docs(pipelines): Add troubleshooting tip for standalone Pipelines installation #4084

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0db9f48
docs(pipelines): add troubleshooting tip for installation using platf…
kaikaila Apr 11, 2025
19a48a0
Correct the format of "3 minutes to complete"
kaikaila Apr 11, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 11 additions & 3 deletions content/en/docs/components/pipelines/operator-guides/installation/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,11 +24,19 @@ You should be familiar with [Kubernetes](https://kubernetes.io/docs/home/),
kubectl apply -k "github.com/kubeflow/pipelines/manifests/kustomize/env/dev?ref=$PIPELINE_VERSION"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we replace the environment installation from dev to env/platform-agnostic to make the installation compatible on any Kubernetes cluster

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we replace the environment installation from dev to env/platform-agnostic to make the installation compatible on any Kubernetes cluster

That makes sense — I originally added it as a troubleshooting tip to keep the change minimal, but I agree platform-agnostic might be a better default in the long run.

I'm happy to update the PR if that's the preferred direction from the maintainers. Open to hearing what others think!

```

The Kubeflow Pipelines deployment requires approximately 3 minutes to complete.
> 💡 **Troubleshooting**: If you encounter persistent pod crashes (e.g., `proxy-agent`, `workflow-controller`) after applying the default config, you may try using the `platform-agnostic` configuration instead:
>
> ```bash
> kubectl apply -k "github.com/kubeflow/pipelines/manifests/kustomize/env/platform-agnostic?ref=$PIPELINE_VERSION"
> ```
>
> This workaround was verified on Minikube using `v2.0.0`, and aligns with community suggestions in [kubeflow/pipelines#9546](https://github.com/kubeflow/pipelines/issues/9546). It may also help users facing similar pod crash issues in other environments or newer versions.

2. Run the following to port-forward the Kubeflow Pipelines UI:
The Kubeflow Pipelines deployment requires approximately 3 minutes to complete.

1. Run the following to port-forward the Kubeflow Pipelines UI:
```
kubectl port-forward -n kubeflow svc/ml-pipeline-ui 8080:80
```

3. Open http://localhost:8080 on your browser to see the Kubeflow Pipelines UI.
2. Open http://localhost:8080 on your browser to see the Kubeflow Pipelines UI.