[dns] Technitium — raise memory limit to 2Gi (was 1Gi, originally 512Mi)

Primary was at 401Mi / 512Mi (78%) before the first bump; the plan's 1Gi
leaves enough headroom for normal operation but thin margin if blocklists or
cache grow. User escalated: OOM cascades are the exact failure mode that
causes user-visible DNS outages, so give a full 2x safety margin across all
three instances. Replicas currently use 124-155Mi steady-state so they have
enormous headroom at 2Gi — accepted for symmetry and future growth (OISD
blocklists, in-memory cache).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Viktor Barzin 2026-04-19 15:08:04 +00:00
parent a86a97deb7
commit 5ea079181f
2 changed files with 6 additions and 6 deletions

View file

@ -116,10 +116,10 @@ resource "kubernetes_deployment" "technitium_secondary" {
resources {
requests = {
cpu = "100m"
memory = "1Gi"
memory = "2Gi"
}
limits = {
memory = "1Gi"
memory = "2Gi"
}
}
port {
@ -271,10 +271,10 @@ resource "kubernetes_deployment" "technitium_tertiary" {
resources {
requests = {
cpu = "100m"
memory = "1Gi"
memory = "2Gi"
}
limits = {
memory = "1Gi"
memory = "2Gi"
}
}
port {

View file

@ -171,10 +171,10 @@ resource "kubernetes_deployment" "technitium" {
resources {
requests = {
cpu = "100m"
memory = "1Gi"
memory = "2Gi"
}
limits = {
memory = "1Gi"
memory = "2Gi"
}
}
port {