From 0f2fab36c847d447ff0c70bedf269ab184f3c99a Mon Sep 17 00:00:00 2001
From: Kiah Imani <kiah@c-trax.com>
Date: Sun, 2 Aug 2026 21:07:27 -0400
Subject: [PATCH] DOC-279: Document pod config support for additional K8s
 services

List all services now covered by LOCALSTACK_K8S_POD_CONFIG (CodeBuild,
DocumentDB, ElastiCache, Kafka, Kinesis Data Analytics, MWAA, RDS
MySQL/MSSQL, Glue, EC2), and note that RDS PostgreSQL/MariaDB don't
apply since they run in-process rather than spawning child pods.
---
 .../customization/kubernetes/configuration.md |  1 +
 .../kubernetes/pod-configuration.md           | 36 ++++++++++++++++---
 2 files changed, 32 insertions(+), 5 deletions(-)

diff --git a/src/content/docs/aws/customization/kubernetes/configuration.md b/src/content/docs/aws/customization/kubernetes/configuration.md
index 05156095..676f802d 100644
--- a/src/content/docs/aws/customization/kubernetes/configuration.md
+++ b/src/content/docs/aws/customization/kubernetes/configuration.md
@@ -31,6 +31,7 @@ K8S_ANNOTATIONS=prometheus.io/scrape=true,prometheus.io/port=8080
 ### Pod configuration
 
 `K8S_POD_CONFIG` configures Kubernetes metadata, scheduling, and resource settings for child pods created by supported services such as Lambda and ECS.
+`LOCALSTACK_K8S_POD_CONFIG` configures Kubernetes metadata, scheduling, and resource settings for child pods created by supported services, including Lambda, ECS, CodeBuild, DocumentDB, ElastiCache, Kafka, Kinesis Data Analytics, MWAA, RDS (MySQL and SQL Server engines), Glue, and EC2.
 Use it to define reusable pod profiles with fields such as `nodeSelector`, `tolerations`, `affinity`, `resources`, `labels`, and `annotations`.
 The value must be valid JSON.
 
diff --git a/src/content/docs/aws/customization/kubernetes/pod-configuration.md b/src/content/docs/aws/customization/kubernetes/pod-configuration.md
index 01f1ed85..da8ee888 100644
--- a/src/content/docs/aws/customization/kubernetes/pod-configuration.md
+++ b/src/content/docs/aws/customization/kubernetes/pod-configuration.md
@@ -16,10 +16,28 @@ Use the `K8S_POD_CONFIG` environment variable to configure Kubernetes metadata,
 The variable accepts a JSON object with reusable `profiles` and optional per-service mappings.
 The value must be valid JSON. LocalStack validates this configuration at startup and refuses to start if the value is not valid JSON or contains unknown fields, so misconfigurations surface before any child pods are created.
 
-::::note
-This feature currently applies to Lambda and ECS pods created by the Kubernetes executor.
-Support for additional service integrations is being added incrementally.
-::::
+## Supported services
+
+`LOCALSTACK_K8S_POD_CONFIG` applies to child pods created by the following services:
+
+- Lambda (`lambda`)
+- ECS (`ecs`)
+- CodeBuild (`codebuild`)
+- DocumentDB (`docdb`)
+- ElastiCache (`elasticache`)
+- Kafka (`kafka`)
+- Kinesis Data Analytics (`kinesisanalyticsv2`)
+- MWAA (`mwaa`)
+- RDS (`rds`), for the MySQL and SQL Server (MSSQL) engines only
+- Glue (`glue`)
+- EC2 (`ec2`)
+
+The value in parentheses is the key to use for that service under the `services` block.
+
+:::note
+RDS pod configuration only applies to the MySQL and SQL Server engines.
+The PostgreSQL and MariaDB engines run in-process inside the main LocalStack pod rather than spawning a separate child pod, so `LOCALSTACK_K8S_POD_CONFIG` doesn't apply to them.
+:::
 
 ## Supported fields
 
@@ -157,6 +175,11 @@ A service can reference a single profile with `profile`, or it can map `arm64` a
       "nodeSelector": {
         "pool": "ecs-nodes"
       }
+    },
+    "database": {
+      "nodeSelector": {
+        "pool": "db-nodes"
+      }
     }
   },
   "services": {
@@ -165,6 +188,9 @@ A service can reference a single profile with `profile`, or it can map `arm64` a
     },
     "ecs": {
       "profile": "ecs-tasks"
+    },
+    "rds": {
+      "profile": "database"
     }
   }
 }
@@ -172,7 +198,7 @@ A service can reference a single profile with `profile`, or it can map `arm64` a
 
 In this example, ARM Lambda pods use `lambda-arm`.
 AMD64 Lambda pods use `defaultAmd64`.
-ECS pods always use `ecs-tasks`, regardless of architecture, because `services.ecs.profile` bypasses architecture-based routing.
+ECS pods always use `ecs-tasks`, and RDS pods always use `database`, regardless of architecture, because `services.<service>.profile` bypasses architecture-based routing.
 Workloads without architecture information use `default`.
 
 ## Profile resolution