Kubernetes
586 incident problems in Kubernetes environments.
먼저 읽을 가이드
추천 문제
All problems (586)
K8S-1499A Gateway API canary route looks correct and 100 percent of traffic still lands on stableCanary weight changes never take effect after moving from Ingress to Gateway API on one controller revision.KubernetesAdvanced11 minProK8S-1553A Gateway API listener changes and one edge pod still serves the old routeA route change fails on one edge pod while the rest of the gateway fleet is correct.KubernetesAdvanced11 minProK8S-1523A Gateway API route attaches and one worker still serves the old backendA backend switch never takes effect on one gateway worker after a route change.KubernetesAdvanced11 minProK8S-1513A Gateway API route attaches and still serves the old backendA backend switch never takes effect on one gateway worker after a Gateway API change.KubernetesAdvanced11 minProCICD-1536A GitOps image update lands and rollback failsRollbacks fail only after registry digest alias cleanup in a GitOps workflow.CI/CDAdvanced11 minProCICD-1546A GitOps image update lands and rollback failsRollbacks fail only after digest alias cleanup in a GitOps flow.CI/CDAdvanced11 minProK8S-1571A Hubble relay update rolls out and one flow stream still tags the old identityOne Hubble relay still tags the old identity after a Cilium rollout.KubernetesAdvanced11 minProK8S-1590A mesh egress policy updates and one sidecar still allows the old hostOne sidecar still allows the old host after mesh egress policy updates.KubernetesAdvanced11 minProSECURITY-1385A Prometheus exporter secret is rotated and alerting still uses the old...A Prometheus exporter secret is rotated and alerting still uses the old... focuses on Identity And Access and asks the reader to isolate the key signal in Kubernetes. Hot-reload automation can succeed technically while watching the...SecurityIntermediate11 minProK8S-1573A ReferenceGrant is applied and one cross-namespace route still failsOne cross-namespace route fails after ReferenceGrant rollout.KubernetesAdvanced11 minProK8S-1563A TLSRoute attaches cleanly and one gateway pod still serves the old backendOne gateway pod serves the old backend after a TLSRoute change.KubernetesAdvanced11 minProCICD-1507An Argo CD repo-server trust update lands and one Git mirror still failsOnly one Argo CD repo-server pod rejects a rotated Git mirror key after a trust bundle update.CI/CDAdvanced11 minProSECURITY-1405An htpasswd secret is updated and the ingress still accepts the old passwordAn htpasswd secret is updated and the ingress still accepts the old password focuses on reload-behavior and asks the reader to isolate the key signal in Kubernetes. Secret reload problems can come from normalization logic in th...SecurityIntermediate11 minProK8S-1490An ingress-nginx admission patch succeeds and websocket upgrades still failWebSocket upgrades fail only for canary users after ingress annotations were centralized.KubernetesAdvanced11 minProK8S-1559An IRSA migration completes and one DaemonSet still loses cloud accessA DaemonSet loses AWS access only on older nodes after IRSA migration.KubernetesAdvanced11 minProK8S-1580An Istio subset update rolls out and one sidecar still uses the old destinationOne sidecar keeps using the old destination subset after a rollout.KubernetesAdvanced11 minProK8S-1481A Cilium FQDN policy looks updated and pods still failPods stay blocked after an egress FQDN rule is tightened even though the updated policy is visible on the node.KubernetesAdvanced12 minProK8S-1561A Cilium kube-proxy replacement rollout finishes and one node still sends traffic to the old backendOne node still sends requests to an old backend after kube-proxy replacement rollout.KubernetesAdvanced12 minProK8S-1521A Cilium node upgrade finishes and one service path still dropsTraffic drops only from one node after a high-churn service rollout on Cilium.KubernetesAdvanced12 minProK8S-1541A Cilium node upgrade finishes and one service path still dropsTraffic drops only from one node after a service rollout on Cilium.KubernetesAdvanced12 minPro