From c88a01299b886c62448829007d53b014172043e5 Mon Sep 17 00:00:00 2001
From: leezerg <138777478+leezerg@users.noreply.github.com>
Date: Thu, 2 Oct 2025 13:30:33 +0300
Subject: [PATCH] fix resources livekit

---
 livekit/livekit-egress/values.yaml | 6 +++---
 livekit/livekit-server/values.yaml | 8 ++++----
 2 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/livekit/livekit-egress/values.yaml b/livekit/livekit-egress/values.yaml
index 82641e3..db322c5 100644
--- a/livekit/livekit-egress/values.yaml
+++ b/livekit/livekit-egress/values.yaml
@@ -28,11 +28,11 @@ nodeSelector:
 
 resources:
   requests:
+    cpu: 4000m
+    memory: 4Gi
+  limits:
     cpu: 6000m
     memory: 6Gi
-  limits:
-    cpu: 8000m
-    memory: 8Gi
 
 serviceAccount:
   create: false
diff --git a/livekit/livekit-server/values.yaml b/livekit/livekit-server/values.yaml
index 9b72f4e..0127120 100644
--- a/livekit/livekit-server/values.yaml
+++ b/livekit/livekit-server/values.yaml
@@ -98,11 +98,11 @@ nodeSelector:
 
 resources:
   requests:
-    cpu: 10000m
-    memory: 10Gi
+    cpu: 7000m
+    memory: 7Gi
   limits:
-    cpu: 10000m
-    memory: 10Gi
+    cpu: 8000m
+    memory: 8Gi
   # Due to port restrictions, you can run only one instance of LiveKit per physical
   # node. Because of that, we recommend giving it plenty of resources to work with
   # limits: