CKA
955 incident response problems that help with CKA prep.
먼저 읽을 가이드
추천 문제
All problems (955)
K8S-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 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 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 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 minProK8S-1551A Cilium policy rollout finishes and one node still bypasses egress rulesOne node bypasses egress policy after identity translation rules change.KubernetesAdvanced12 minProK8S-1501A Cilium policy rollout looks correct and one namespace still drops east-west trafficCross-cluster service traffic fails only from one node pool after a Cilium peering update.KubernetesAdvanced12 minProK8S-1531A Cilium rollout finishes and one service path still dropsTraffic drops only from one node after a service rollout on Cilium.KubernetesAdvanced12 minProK8S-1491A Cilium upgrade completes and east-west traffic still dropsCross-cluster service calls fail only between one peered segment after a Cilium control-plane upgrade.KubernetesAdvanced12 minProK8S-1511A Cilium upgrade finishes and one node still drops service trafficOnly one node drops service traffic after a high-churn rolling update on a Cilium cluster.KubernetesAdvanced12 minProK8S-1493A Kubernetes API priority and fairness change lands and kubelet heartbeats still starveNode heartbeats degrade only for fresh autoscaled nodes after API priority and fairness tuning.KubernetesAdvanced12 minPro