Deployment Governance
222 incident problems about Deployment Governance. Start with the reviewed ones.
먼저 읽을 가이드
추천 문제
All problems (222)
K8S-1509A Gateway API canary route attaches and all traffic still lands on stableCanary weights never take effect on one controller revision after a Gateway API migration.KubernetesAdvanced11 minProK8S-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-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-1501A GitHub OIDC deploy succeeds in test and fails in prodOnly production deploys fail after an AWS federation alias cleanup while test continues to work.CI/CDAdvanced11 minProCICD-1591A GitHub OIDC deployment still fails in one accountDeployments fail only in one account after consolidating environment aliases.CI/CDAdvanced11 minProK8S-1573A ReferenceGrant is applied and one cross-namespace route still failsOne cross-namespace route fails after ReferenceGrant rollout.KubernetesAdvanced11 minProCICD-1493A Terraform Cloud speculative plan finishes and the comment never appearsDevelopers see completed speculative plans in Terraform Cloud but no PR comment after enabling an internal webhook relay.CI/CDAdvanced11 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 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 minProCICD-1555A canary analysis completes and rollback still misfiresA rollback triggers only in one region after telemetry bucket changes during canary analysis.CI/CDAdvanced12 minProCICD-1485A Flux image update commits the new tag and Argo still deploys the old digestGitOps promotion looks correct, yet one environment deploys the previous image after registry proxy caching changes.CI/CDAdvanced12 minProCICD-1491A GitHub Actions OIDC deploy works in one region and fails in anotherA multi-region deployment pipeline starts failing only in the disaster recovery account after environment names were cleaned up.CI/CDAdvanced12 minProCICD-1541A GitHub deployment job passes approvals and still failsDeployments fail only in one account after moving the production workflow into a new path.CI/CDAdvanced12 minProCICD-1521A GitHub environment approval passes and the deploy job still failsOnly production deploys fail after a workflow file move even though approvals complete normally.CI/CDAdvanced12 minProCICD-1531A GitHub OIDC deployment works in one account and fails in anotherDeployments fail only in one account after moving repositories under a new GitHub organization.CI/CDAdvanced12 minProK8S-1560A service mesh revision switch succeeds and one workload still routes to the old control planeOne workload remains on the old control plane after a mesh revision switch.KubernetesAdvanced12 minProSECURITY-1323A Grafana OAuth login works and role sync stays wrongAn IdP cleanup changes claim names and Grafana users later authenticate successfully but lose admin or editor access unexpectedly.SecurityIntermediate13 minProCICD-1467An Argo Rollouts analysis stays yellowCanary promotions stall right after a metrics label cleanup even though dashboards still show healthy rollout traffic.CI/CDAdvanced13 minProSECURITY-1351A Grafana login succeeds and team access disappearsAn SSO schema update lands and later Grafana users can log in but lose the permissions tied to their old team claim mapping.SecurityAdvanced14 minPro