diff --git a/website/guides/advanced/deploy-daemonset-with-karpenter.md b/website/guides/advanced/deploy-daemonset-with-karpenter.md index d5eef5f71b..2b6af563d0 100644 --- a/website/guides/advanced/deploy-daemonset-with-karpenter.md +++ b/website/guides/advanced/deploy-daemonset-with-karpenter.md @@ -1,5 +1,5 @@ --- -last_modified_on: "2024-08-09" +last_modified_on: "2024-11-27" $schema: "/.meta/.schemas/guides.json" title: Deploy a DaemonSet in a Karpenter context description: How to ensure your DaemonSet is well deployed when you are using Karpenter. @@ -51,7 +51,7 @@ This ensures that critical workloads receive the necessary resources to run effe ### Deploy a new Priority Class using Helm -I created a [simple repository](https://github.com/baalooos/karpenter-daemonset-priority-class) you can clone to follow along. +I created a [simple repository](https://github.com/Qovery/qovery-charts-examples/tree/main/karpenter-daemonset-priority-class-main) you can clone to follow along. Create the karpenter-priority-class service in the Qovery environment where you want to deploy your DaemonSet by following [this documentation][docs.using-qovery.configuration.helm] and these values: @@ -59,20 +59,16 @@ Create the karpenter-priority-class service in the Qovery environment where you * Service name: `karpenter-priority-class` * Source: * Helm source: `Git Provider` - * Git repository: `Github` (Change if you are not using GitHub) - * Repository: `Baalooos/karpenter-daemonset-priority-class` (Replace by the name of your repository) + * Git account: `Public repository` (Change if you are not using GitHub) + * Repository: `https://github.com/Qovery/qovery-charts-examples.git` (Replace by the name of your repository) * Branch: `main` - * Root application path: `/` + * Root application path: `/karpenter-daemonset-priority-class-main` * Allow cluster-wide resources :heavy_check_mark: Click on Continue * Values override as file: - * File source: `Git repository` - * Git repository: `Github` (Change if you are not using GitHub) - * Repository: `Baalooos/karpenter-daemonset-priority-class` (Replace by the name of your repository) - * Branch: `main` - * Override path: `/values.yaml` + * File source: `None` Then, you can: diff --git a/website/guides/advanced/deploy-daemonset-with-karpenter.md.erb b/website/guides/advanced/deploy-daemonset-with-karpenter.md.erb index e069561f45..e89426ad5a 100644 --- a/website/guides/advanced/deploy-daemonset-with-karpenter.md.erb +++ b/website/guides/advanced/deploy-daemonset-with-karpenter.md.erb @@ -42,7 +42,7 @@ This ensures that critical workloads receive the necessary resources to run effe ### Deploy a new Priority Class using Helm -I created a [simple repository](https://github.com/baalooos/karpenter-daemonset-priority-class) you can clone to follow along. +I created a [simple repository](https://github.com/Qovery/qovery-charts-examples/tree/main/karpenter-daemonset-priority-class-main) you can clone to follow along. Create the karpenter-priority-class service in the Qovery environment where you want to deploy your DaemonSet by following [this documentation][docs.using-qovery.configuration.helm] and these values: @@ -50,20 +50,16 @@ Create the karpenter-priority-class service in the Qovery environment where you * Service name: `karpenter-priority-class` * Source: * Helm source: `Git Provider` - * Git repository: `Github` (Change if you are not using GitHub) - * Repository: `Baalooos/karpenter-daemonset-priority-class` (Replace by the name of your repository) + * Git account: `Public repository` (Change if you are not using GitHub) + * Repository: `https://github.com/Qovery/qovery-charts-examples.git` (Replace by the name of your repository) * Branch: `main` - * Root application path: `/` + * Root application path: `/karpenter-daemonset-priority-class-main` * Allow cluster-wide resources :heavy_check_mark: Click on Continue * Values override as file: - * File source: `Git repository` - * Git repository: `Github` (Change if you are not using GitHub) - * Repository: `Baalooos/karpenter-daemonset-priority-class` (Replace by the name of your repository) - * Branch: `main` - * Override path: `/values.yaml` + * File source: `None` Then, you can: 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 e0d3a372cf..3fe5bc04c6 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-09-09" +last_modified_on: "2024-11-27" $schema: "/.meta/.schemas/guides.json" title: Kubernetes observability and monitoring with Datadog description: How to integrate Datadog with Kubernetes on Qovery. @@ -126,6 +126,13 @@ agents: - fargate ``` + + +There is a [known issue](https://github.com/kubernetes-sigs/karpenter/issues/731) with Karpenter and DaemonSets when scaling nodes. A way to resolve this problem is to use a Priority Class and attach it to the DaemonSet we are creating. +Check this ([guide][guides.advanced.deploy-daemonset-with-karpenter]) for more information. + + + @@ -201,3 +208,4 @@ You now have Datadog agent running on your Qovery cluster. You can check their ` [docs.using-qovery.configuration.environment-variable]: /docs/using-qovery/configuration/environment-variable/ [docs.using-qovery.configuration.helm]: /docs/using-qovery/configuration/helm/ [docs.using-qovery.configuration.organization.helm-repository]: /docs/using-qovery/configuration/organization/helm-repository/ +[guides.advanced.deploy-daemonset-with-karpenter]: /guides/advanced/deploy-daemonset-with-karpenter/ 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 5338f80822..d344e96f52 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 @@ -113,6 +113,13 @@ agents: - fargate ``` + + +There is a [known issue](https://github.com/kubernetes-sigs/karpenter/issues/731) with Karpenter and DaemonSets when scaling nodes. A way to resolve this problem is to use a Priority Class and attach it to the DaemonSet we are creating. +Check this ([guide][guides.advanced.deploy-daemonset-with-karpenter]) for more information. + + +