Kubernetes
586 incident problems in Kubernetes environments.
먼저 읽을 가이드
추천 문제
All problems (586)
K8S-1438A Velero restore brings back CRDs and one controller stays brokenA Velero restore brings back CRDs and one controller stays broken focuses on admission-control and asks the reader to isolate the key signal in Kubernetes. Restore-time webhook gaps can become persistent if controllers cache th...KubernetesAdvanced14 minProK8S-1418A Velero restore completes and one workload never stabilizesA Velero restore completes and one workload never stabilizes focuses on admission-control and asks the reader to isolate the key signal in Kubernetes. Restore timing bugs around CRDs often come from webhook reachability windows rat...KubernetesAdvanced14 minProK8S-1310Grafana Agent remote_write looks connected but drops a burst of cluster metricsMetrics ingestion resumes after pressure recovery, but dashboards never fill the missing historical gap from the outage window.KubernetesIntermediate14 minProK8S-1306Promtail tails files successfully until log rotation acceleratesA noisy cluster starts losing short-lived container logs even though Promtail itself reports no crash or auth error.KubernetesIntermediate14 minProK8S-1316A mutating webhook seems available and pod creation still slows to a crawlA mutating webhook seems available and pod creation still slows to a crawl focuses on cluster-maintenance and asks the reader to isolate the key signal in Kubernetes. Fresh endpoints do not guarantee fresh dataplane state on every node.KubernetesIntermediate15 minProK8S-1311A StatefulSet rollout stalls only on replacement nodesA storage add-on update seems fine until stateful workloads land on new nodes and never attach volumes successfully.KubernetesIntermediate15 minProK8S-1584A cert-manager issuer switch is correct and one order still waitsOne cert-manager order remains pending after issuer switch.KubernetesIntermediate8 minProK8S-1606A CoreDNS rewrite fix lands and one namespace still resolves old namesOne namespace still resolves old names after a CoreDNS rewrite fix.KubernetesIntermediate8 minProK8S-1586A CoreDNS rewrite fix lands and one namespace still resolves stale namesOne namespace still resolves stale names after a CoreDNS rewrite fix.KubernetesIntermediate8 minProK8S-1596A CoreDNS rewrite is fixed and one namespace still resolves stale namesOne namespace still resolves stale names after a CoreDNS rewrite fix.KubernetesIntermediate8 minProK8S-1576A CoreDNS rewrite rule changes and one service still resolves the old suffixOne service keeps resolving the old suffix after a CoreDNS rewrite update.KubernetesIntermediate8 minProK8S-1574A signerName update lands and one cert request still waitsOne certificate request stays pending after signerName standardization.KubernetesIntermediate8 minProK8S-1598A webhook config is updated and one API server still ignores the new timeoutOne API server still ignores a new webhook timeout after config updates.KubernetesIntermediate8 minProK8S-1588A webhook timeout is lowered and one API server still waitsOne API server still waits too long after webhook timeout reduction.KubernetesIntermediate8 minProK8S-1608A webhook timeout update lands and one API server still waitsOne API server still waits too long after a webhook timeout update.KubernetesIntermediate8 minProK8S-1483A CoreDNS autopath optimization speeds most lookups and one namespace loopsA migrated namespace sees intermittent DNS loops after autopath optimization is enabled cluster-wide.KubernetesIntermediate9 minProK8S-1516A CoreDNS change is applied and one namespace still resolves stale IPsOnly one namespace behind one node-local cache keeps seeing stale service IPs after a CoreDNS update.KubernetesIntermediate9 minProK8S-1474A CoreDNS negative cache hides a fixed ServiceA service recovers, yet callers keep failing for several minutes because the negative DNS result is still cached.KubernetesIntermediate9 minProK8S-1496A CoreDNS rollout succeeds and pods still resolve stale service IPsOnly pods behind one node-local DNS cache keep resolving a retired service IP after a CoreDNS rollout.KubernetesIntermediate9 minProK8S-1506A CoreDNS rollout succeeds and pods still resolve stale service IPsOnly pods behind one node-local cache keep resolving a retired service IP after a DNS rollout.KubernetesIntermediate9 minPro