From 39506ec48cb199522d68514f7bba431c3a5ed2ff Mon Sep 17 00:00:00 2001
From: acarranoqovery <105300721+acarranoqovery@users.noreply.github.com>
Date: Sat, 30 Nov 2024 19:44:41 +0100
Subject: [PATCH] Chore update jp karpenter (#493)
* chore: update jupyterHub doc for Karpenter
* fix
---
.../tutorial/deploy-jupyterhub-qovery.md | 42 ++++++++++++++++++-
.../tutorial/deploy-jupyterhub-qovery.md.erb | 37 ++++++++++++++++
...servability-and-monitoring-with-datadog.md | 6 +--
...ability-and-monitoring-with-datadog.md.erb | 4 +-
4 files changed, 83 insertions(+), 6 deletions(-)
diff --git a/website/guides/tutorial/deploy-jupyterhub-qovery.md b/website/guides/tutorial/deploy-jupyterhub-qovery.md
index e46baefff0..a8c8ec48c6 100644
--- a/website/guides/tutorial/deploy-jupyterhub-qovery.md
+++ b/website/guides/tutorial/deploy-jupyterhub-qovery.md
@@ -1,5 +1,5 @@
---
-last_modified_on: "2024-07-19"
+last_modified_on: "2024-11-30"
$schema: "/.meta/.schemas/guides.json"
title: Deploy JupyterHub using Helm
description: How to deploy JupyterHub on Qovery using the official Helm chart.
@@ -8,6 +8,9 @@ tags: ["type: tutorial", "technology: qovery"]
hide_pagination: true
---
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
import Steps from '@site/src/components/Steps';
import Assumptions from '@site/src/components/Assumptions';
@@ -69,6 +72,17 @@ Create the JupyterHub service in the Qovery environment of your choice (preferab
* File source: `Raw YAML`
* Raw YAML:
+
+
+
+
```yaml
fullnameOverride: "jupyterhub"
proxy:
@@ -76,6 +90,32 @@ proxy:
type: ClusterIP
```
+
+
+
+
+To ensure every node created by Karpenter is monitored by Datadog, we need to configure a priority class.
+
+```yaml
+fullnameOverride: "jupyterhub"
+proxy:
+ service:
+ type: ClusterIP
+scheduling:
+ podPriority:
+ enabled: true
+ globalDefault: true
+ defaultPriority: 50
+ imagePullerPriority: 1000
+ userPlaceholderPriority: 0
+```
+
+
+
+
+
+
+
There are many other values you can set to modify the JupyterHub behavior. For advanced usage, check: [JupyterHub Customization](https://z2jh.jupyter.org/en/stable/jupyterhub/customization.html)
Now get to the last step and `Create` the service on Qovery.
diff --git a/website/guides/tutorial/deploy-jupyterhub-qovery.md.erb b/website/guides/tutorial/deploy-jupyterhub-qovery.md.erb
index 517ead8914..6035c3046c 100644
--- a/website/guides/tutorial/deploy-jupyterhub-qovery.md.erb
+++ b/website/guides/tutorial/deploy-jupyterhub-qovery.md.erb
@@ -60,13 +60,50 @@ Create the JupyterHub service in the Qovery environment of your choice (preferab
* File source: `Raw YAML`
* Raw YAML:
+
+
+
+
+```yaml
+fullnameOverride: "jupyterhub"
+proxy:
+ service:
+ type: ClusterIP
+```
+
+
+
+
+
+To ensure every node created by Karpenter is monitored by Datadog, we need to configure a priority class.
+
```yaml
fullnameOverride: "jupyterhub"
proxy:
service:
type: ClusterIP
+scheduling:
+ podPriority:
+ enabled: true
+ globalDefault: true
+ defaultPriority: 50
+ imagePullerPriority: 1000
+ userPlaceholderPriority: 0
```
+
+
+
+
+
+
There are many other values you can set to modify the JupyterHub behavior. For advanced usage, check: [JupyterHub Customization](https://z2jh.jupyter.org/en/stable/jupyterhub/customization.html)
Now get to the last step and `Create` the service on Qovery.
diff --git a/website/guides/tutorial/kubernetes-observability-and-monitoring-with-datadog.md b/website/guides/tutorial/kubernetes-observability-and-monitoring-with-datadog.md
index 1fca0505d0..d414dbe4de 100644
--- a/website/guides/tutorial/kubernetes-observability-and-monitoring-with-datadog.md
+++ b/website/guides/tutorial/kubernetes-observability-and-monitoring-with-datadog.md
@@ -1,5 +1,5 @@
---
-last_modified_on: "2024-11-28"
+last_modified_on: "2024-11-30"
$schema: "/.meta/.schemas/guides.json"
title: Kubernetes observability and monitoring with Datadog
description: How to integrate Datadog with Kubernetes on Qovery.
@@ -17,7 +17,7 @@ import Assumptions from '@site/src/components/Assumptions';
import Jump from '@site/src/components/Jump';
While Qovery will soon provide basic metrics on apps resources usage, you might need a more advanced view on what happens on your infrastructure. There are many solutions on the market, one of them being Datadog.
-Datadog is one of the leading platforms for monitoring and observability, and it's pretty easy to integrate it with Qovery.
+Datadog is one of the leading platforms for monitoring and observability, and it is pretty easy to integrate it with Qovery.
@@ -100,7 +100,7 @@ datadog:
-
+
To ensure every node created by Karpenter is monitored by Datadog, we need to configure a priority class.
diff --git a/website/guides/tutorial/kubernetes-observability-and-monitoring-with-datadog.md.erb b/website/guides/tutorial/kubernetes-observability-and-monitoring-with-datadog.md.erb
index 78eb186966..5abf48179c 100644
--- a/website/guides/tutorial/kubernetes-observability-and-monitoring-with-datadog.md.erb
+++ b/website/guides/tutorial/kubernetes-observability-and-monitoring-with-datadog.md.erb
@@ -12,7 +12,7 @@ import Assumptions from '@site/src/components/Assumptions';
import Jump from '@site/src/components/Jump';
While Qovery will soon provide basic metrics on apps resources usage, you might need a more advanced view on what happens on your infrastructure. There are many solutions on the market, one of them being Datadog.
-Datadog is one of the leading platforms for monitoring and observability, and it's pretty easy to integrate it with Qovery.
+Datadog is one of the leading platforms for monitoring and observability, and it is pretty easy to integrate it with Qovery.
@@ -87,7 +87,7 @@ datadog:
-
+
To ensure every node created by Karpenter is monitored by Datadog, we need to configure a priority class.