From e86ebe3fe0fe9d4128a17e6ad40c1a8371321035 Mon Sep 17 00:00:00 2001
From: Sheogorath <sheogorath@shivering-isles.com>
Date: Mon, 21 Feb 2022 02:42:12 +0100
Subject: [PATCH] fix(descheduler): Fix failed cronjobs
This patch should resovled the issue of failed descheduler cronjobs when
the descheduler binary is exiting unexpected. In the issue linked below,
some descheduler contributors recommend to use the `Deployment` kind for
descheduler, since that's what descheuler is optimised for nowadays. The
Helm chart just hasn't caught up yet.
References:
https://github.com/kubernetes-sigs/descheduler/issues/728
---
infrastructure/kube-system/descheduler.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/infrastructure/kube-system/descheduler.yaml b/infrastructure/kube-system/descheduler.yaml
index 125c69708..a4ede583b 100644
--- a/infrastructure/kube-system/descheduler.yaml
+++ b/infrastructure/kube-system/descheduler.yaml
@@ -25,6 +25,7 @@ spec:
version: 0.23.1
interval: 5m
values:
+ kind: Deployment
resources:
requests:
cpu: 100m
--
GitLab