From 99c19584f7dfdeb2577e67f7e408c48023199e69 Mon Sep 17 00:00:00 2001
From: Viktor Barzin <vbarzin@gmail.com>
Date: Thu, 11 Jun 2026 19:56:09 +0000
Subject: [PATCH] android-emulator: fit pod inside the tier-1 ResourceQuota
 (Burstable memory)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

First deploy hit 'exceeded quota: tier-quota, requested requests.memory=8Gi,
limited 4Gi' — the generated tier-1 quota caps memory REQUESTS at 4Gi but
allows 32Gi of limits, so go Burstable (requests 3Gi, limits 8Gi) like
tiers 3/4 do, instead of opting the namespace out via custom-quota.
---
 stacks/android-emulator/main.tf | 11 +++++++----
 1 file changed, 7 insertions(+), 4 deletions(-)

diff --git a/stacks/android-emulator/main.tf b/stacks/android-emulator/main.tf
index 154cd7f6..8617a480 100644
--- a/stacks/android-emulator/main.tf
+++ b/stacks/android-emulator/main.tf
@@ -110,12 +110,15 @@ resource "kubernetes_deployment" "android-emulator" {
           }
 
           resources {
-            # No CPU limit (cluster-wide rule — CFS throttling); requests=limits
-            # on memory. Emulator peak: qemu (-memory 4096) + guest overhead +
-            # Xvfb/VNC + JVM sdkmanager on first boot.
+            # No CPU limit (cluster-wide rule — CFS throttling). Burstable on
+            # memory: the tier-1 quota caps requests.memory at 4Gi per
+            # namespace, so requests stay under it while the limit gives the
+            # emulator (qemu -memory 4096 + guest overhead + Xvfb/VNC + JVM
+            # sdkmanager on first boot) room to peak — same Burstable pattern
+            # tiers 3/4 use deliberately.
             requests = {
               cpu    = "2"
-              memory = "8Gi"
+              memory = "3Gi"
             }
             limits = {
               memory = "8Gi"