Skip to content
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

Jump to bottom

[YUNIKORN-400] Helm hub page linked in getting started page #24

Merged
merged 1 commit into from Sep 22, 2020
Merged

[YUNIKORN-400] Helm hub page linked in getting started page #24

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/get_started/get_started.md
View file
Open in desktop
Expand Up @@ -42,6 +42,8 @@ By default, the helm chart will install the scheduler, web-server and the admiss
When `admission-controller` is installed, it simply routes all traffic to YuniKorn. That means the resource scheduling
is delegated to YuniKorn. You can disable it by setting `embedAdmissionController` flag to false during the helm install.

Further configuration options for installing YuniKorn via Helm are available in the [YuniKorn Helm hub page](https://hub.helm.sh/charts/yunikorn/yunikorn).

If you don't want to use helm charts, you can find our step-by-step
tutorial [here](developer_guide/deployment.md).

Expand Down