Deployment Governance
222 incident problems about Deployment Governance. Start with the reviewed ones.
먼저 읽을 가이드
추천 문제
All problems (222)
CICD-1275A deployment waits forever on a required checkA pipeline refactor creates reusable jobs and later environment approval appears successful while the release remains blocked.CI/CDAdvanced16 minProCICD-1370A policy-as-code gate passes in staging and fails in prodA policy-as-code gate passes in staging and fails in prod focuses on Deployment Governance and asks the reader to isolate the key signal in hashicorp. Policy failures can reveal stack-generation drift rather than a bad policy.CI/CDAdvanced16 minProCICD-1292A required deployment check never goes greenA team modularizes CI with reusable workflows and later finds that branch protection blocks every merge.CI/CDAdvanced16 minProCICD-1262A reusable workflow deploys correctly in the caller but silently loses its secret in the called workflowCI/CD incident scenario used for structured troubleshooting practice.CI/CDAdvanced16 minProCICD-1380A Sentinel or OPA gate passes in staging and fails in prodA Sentinel or OPA gate passes in staging and fails in prod focuses on Deployment Governance and asks the reader to isolate the key signal in hashicorp. Policy failures often reveal stack-generation drift rather than a bad rule.CI/CDAdvanced16 minProCICD-1308A speculative Terraform plan in VCS succeeds but the real apply failsA team trusts green speculative plans and later finds applies failing only when merged through the VCS trigger path.CI/CDAdvanced16 minProCICD-1338A Terraform apply deadlocks a rolloutA governance policy seems correct across most stacks and later one workspace category becomes permanently queued before apply.CI/CDAdvanced16 minProCICD-1372A Terraform Cloud apply works in lower environments and fails in productionA Terraform Cloud apply works in lower environments and fails in production focuses on Deployment Governance and asks the reader to isolate the key signal in hashicorp. Remote apply divergence often lives in workspace inheritance l...CI/CDAdvanced16 minProCICD-1362A Terraform Cloud apply works in staging and fails in prodA multi-environment Terraform setup behaves consistently until production alone begins creating resources in the wrong region after a variable-set refactor.CI/CDAdvanced16 minProCICD-1314A Terraform Cloud run queue backs upA governance rollout adds policy checks and later certain workspaces become permanently queued despite valid plans.CI/CDAdvanced16 minProCICD-1332A Terraform Cloud run succeeds on plan and fails on applyA Terraform Cloud run succeeds on plan and fails on apply focuses on Deployment Governance and asks the reader to isolate the key signal in hashicorp. Terraform review quality depends on freezing more than the code revision alone.CI/CDAdvanced16 minProCICD-1352A Terraform module upgrade succeeds in plan and fails in applyA Terraform module upgrade succeeds in plan and fails in apply focuses on Deployment Governance and asks the reader to isolate the key signal in hashicorp. Provider upgrades can break implicit data contracts even when schemas do not change.CI/CDAdvanced16 minProCICD-1360A Terraform policy check fails only in productionA Terraform policy check fails only in production focuses on Deployment Governance and asks the reader to isolate the key signal in hashicorp. Policy failures can expose module-generation drift rather than policy mistakes.CI/CDAdvanced16 minProCICD-1342A Terraform run applies cleanly and the next destroy failsA Terraform codebase is refactored into wrapper modules and later destroy or drift remediation affects the wrong target only for one resource family.CI/CDAdvanced16 minProK8S-1319A Traefik TCP route works in staging and fails in productionA TCP ingress setup that works in staging misroutes in production where more routers and entryPoint reuse exist.KubernetesAdvanced16 minProK8S-1314An ingress migration preserves the hostname and still failsAn ingress migration preserves the hostname and still fails focuses on Deployment Governance and asks the reader to isolate the key signal in Kubernetes. Controller migrations preserve intent less faithfully than YAML similarity suggests.KubernetesAdvanced16 minProK8S-1303Leader election looks healthy until the controller is Helm-migratedA controller is reinstalled or moved between namespaces and begins flapping without an obvious RBAC denial.KubernetesAdvanced16 minProCICD-1281A reusable workflow can mint an OIDC token in one repository but fails in anotherA deployment pipeline is refactored into a shared workflow and later only one repository can no longer assume the cloud role.CI/CDAdvanced17 minProCICD-1289A canary deploy health check stays redA canary deployment begins failing only after a cluster or auth dependency upgrade, even though application code and rollout logic are unchanged.CI/CDAdvanced18 minProCICD-1250A deployment concurrency rule exists but two production writes still overlapTeams split release and hotfix workflows and later discover both can deploy to the same target at once even though each workflow defines concurrency.CI/CDAdvanced18 minPro