android-emulator: import orphaned namespace into state (lock-race recovery)
Pipeline 85 created the namespace but a Terraform pg-backend workspace-creation lock race (new stack schema initializing while other stacks applied concurrently) left it out of the recorded state — every later apply then died with 'namespaces android-emulator already exists'. Adopt it with an import block per the house recovery pattern; stanza gets removed once it has applied.
This commit is contained in:
parent
99c19584f7
commit
b948224008
1 changed files with 9 additions and 0 deletions
|
|
@ -8,6 +8,15 @@
|
|||
# - privileged + /dev/kvm hostPath (namespace is on the Kyverno exclude list)
|
||||
# - swiftshader rendering — deliberately NOT on the contended T4 GPU node
|
||||
|
||||
# Recovery stanza (delete after it applies once): pipeline 85's first apply
|
||||
# created the namespace but a PG-backend workspace-creation lock race left it
|
||||
# out of the recorded state, so subsequent plans tried to re-create it.
|
||||
# House pattern: adopt via import block, plan-to-zero, then drop the stanza.
|
||||
import {
|
||||
to = kubernetes_namespace.android-emulator
|
||||
id = "android-emulator"
|
||||
}
|
||||
|
||||
resource "kubernetes_namespace" "android-emulator" {
|
||||
metadata {
|
||||
name = "android-emulator"
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue