Runtime Configuration
147 incident problems about Runtime Configuration. Start with the reviewed ones.
먼저 읽을 가이드
추천 문제
All problems (147)
K8S-1376A kube-state-metrics dashboard goes blankA label cleanup normalizes metric sets and later deployment or StatefulSet dashboards render empty despite healthy scrapes.KubernetesIntermediate12 minProK8S-1391A metrics pipeline looks healthy and kube-state-metrics dashboards still miss...A metrics pipeline looks healthy and kube-state-metrics dashboards still... focuses on runtime-configuration and asks the reader to isolate the key signal in grafana. Monitoring regressions after chart upgrades often come from selector voc...KubernetesIntermediate12 minProLINUX-1333A package install completes and a service still starts with missing modulesA new module or runtime is installed and a service launched by systemd cannot see it even though the command works interactively.LinuxIntermediate12 minProK8S-1383A Prometheus adapter exposes an external metric and the HPA never scalesA Prometheus adapter exposes an external metric and the HPA never scales focuses on runtime-configuration and asks the reader to isolate the key signal in grafana. Autoscaling adapters fail quietly when a single ownership label disappears bet...KubernetesIntermediate12 minProK8S-1350A Prometheus scrape target keeps flapping (servicemonitor-still-targeted-old-port-name)A Prometheus scrape target keeps flapping (servicemonitor-still-targeted-old... focuses on runtime-configuration and asks the reader to isolate the key signal in grafana. Monitoring often binds to names, not just numbers, and chart cleanups can qui...KubernetesIntermediate12 minProCICD-1337A reusable workflow keeps skipping one deploymentA shared deployment workflow is reused across environments and one path silently stops running after the input defaults are refactored.CI/CDIntermediate12 minProLINUX-1381A rootless Podman service survives package updates and failsA rootless Podman service survives package updates and fails focuses on Runner Hygiene and asks the reader to isolate the key signal in Linux. Rootless runtimes depend on user service policy as much as on package installation.LinuxIntermediate12 minProK8S-1364A ServiceMonitor exists and Prometheus scrapes nothingA monitoring manifest cleanup centralizes resources and later one application's metrics vanish despite healthy endpoints.KubernetesIntermediate12 minProK8S-1374A ServiceMonitor exists and Prometheus scrapes nothingA monitoring cleanup centralizes manifests and later one application's metrics vanish despite healthy endpoints.KubernetesIntermediate12 minProLINUX-1361A systemd path unit stopped triggering after a deployment model switched from in-place writes to symlink swaps for the current release pointerThe watched path still changes logically, yet no event fires because the release tool now updates a symlink target instead of modifying the file directly.LinuxIntermediate12 minProLINUX-1371A systemd PathUnit never triggers after a blue-green releaseA deployment hook relies on a PathUnit to reload a service and later one release lands without any of the expected follow-up actions.LinuxIntermediate12 minProLINUX-1341A systemd service works by hand and fails on bootA systemd service works by hand and fails on boot focuses on cluster-maintenance and asks the reader to isolate the key signal in Linux. Systemd may need files to exist before the process ever starts, not only by the time the command runs.LinuxIntermediate12 minProLINUX-1373An apt hardening migration looks complete and old packages still come from an...An apt hardening migration looks complete and old packages still come from... focuses on runtime-configuration and asks the reader to isolate the key signal in ubuntu. A correct signed-by migration can still be undermined by one forgotten sour...LinuxIntermediate12 minProLINUX-1345An Ubuntu cloud image keeps restoring the wrong routeA network incident is repaired interactively and the host reverts to the old broken route after reboot or reprovision events.LinuxIntermediate12 minProK8S-1381Metrics Server stays ready and the HPA still shows unknownMetrics Server stays ready and the HPA still shows unknown focuses on runtime-configuration and asks the reader to isolate the key signal in Kubernetes. Autoscaling failures often come from address selection drift between components rather...KubernetesIntermediate12 minProLINUX-1325sudo stops honoring one permissionA host hardening change adds a new sudoers.d file and later one operational command begins prompting or denying unexpectedly.LinuxIntermediate12 minProCICD-1325A compose dependency waits foreverA base image update lands and downstream services stop starting because a health gate never turns green anymore.CI/CDIntermediate13 minProCICD-1307A compose profile cleanup breaks startup orderingA team simplifies local profiles and later one environment hangs with no obvious container crash.CI/CDIntermediate13 minProCICD-1302A container stays unhealthy forever after a bad migrationA deployment looks protected by health checks until one release wedges a service in an unhealthy-but-still-running state.CI/CDIntermediate13 minProLINUX-1303A database health check goes green before transactions are actually accepted, so dependent services migrate against a server that is still replaying recovery statePort checks pass, yet migrations fail because the real readiness condition trails behind the simplistic health command.LinuxIntermediate13 minPro