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.

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

modify documentation on Daemonset to use built-in Priority Class #496

Merged
merged 4 commits into from
Jan 7, 2025
Merged
Changes from 1 commit
Commits
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
Prev Previous commit
Update website/guides/tutorial/deploy-jupyterhub-qovery.md.erb
Co-authored-by: Julien Dan <[email protected]>
  • Loading branch information
baalooos and jul-dan authored Dec 11, 2024
commit ccde76624b4b441894968df03e32ee083ce438d8
2 changes: 1 addition & 1 deletion website/guides/tutorial/deploy-jupyterhub-qovery.md.erb
Original file line number Diff line number Diff line change
Expand Up @@ -80,7 +80,7 @@ proxy:

</TabItem>

<TabItem value="karpenter">
<TabItem value="EKS with karpenter">

To avoid [a known issue](https://hub.qovery.com/guides/advanced/deploy-daemonset-with-karpenter/) with Karpenter, we need to add a priorityClass to our pods. It is possible to do this using built-in configuration keys:

Expand Down