infrastructure

Use a multi-stage build with mcr.microsoft.com/dotnet/aspnet:10.0 as the runtime base and sdk:10.0 for building. Copy build configuration files first for layer caching, restore and publish the deployable project, and run as the non-root app user on ports 8080 and 8081.

Map three endpoints: /healthz/live for liveness, /healthz/ready for readiness, and /healthz/startup for startup probes. Configure liveness with a 60s period, readiness with a 5s delay and 180s period, and startup with a 10s period and 30 failure threshold.

Start with environment defaults: Integration uses 250m CPU and 256Mi memory requests, while Production uses 500m CPU and 512Mi memory requests with limits at 2x. Profile actual usage before adjusting, and set ephemeral storage at 1Gi request and 2Gi limit.

This skill standardizes on Kustomize with base manifests per deployment and overlays per environment. CI pins the image and namespace in the selected overlay using kustomize edit set image before applying with kubectl kustomize.

OOMKilled events indicate memory usage exceeds the configured limit. Monitor actual consumption, raise the memory limit beyond the 2x-request default if profiling supports it, and check for memory leaks in the application before increasing limits.

Add a ConfigMap only when the deployment has non-secret configuration to mount, and mount a Secret only when the workload consumes one. Never create empty ConfigMaps as placeholders or commit secret values to the repository.