chrome-service: TF-manage novnc image (ghcr:latest), drop its KEEL_IGNORE (ADR-0002 #29)
All checks were successful
ci/woodpecker/push/default Pipeline was successful
All checks were successful
ci/woodpecker/push/default Pipeline was successful
novnc's image was ignore_changed (KEEL_IGNORE) but nothing manages its tag (keel.sh/policy=never), so the earlier forgejo->ghcr repoint never took. Removing container[1].image from ignore_changes lets terragrunt own novnc=ghcr:latest and roll it. container[0]/[2] (pinned playwright) stay ignored. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
parent
94a3d1b870
commit
eb8b550521
1 changed files with 1 additions and 1 deletions
|
|
@ -440,7 +440,7 @@ resource "kubernetes_deployment" "chrome_service" {
|
|||
metadata[0].annotations["keel.sh/pollSchedule"], # KYVERNO_LIFECYCLE_V2
|
||||
metadata[0].annotations["keel.sh/match-tag"],
|
||||
spec[0].template[0].spec[0].container[0].image, # KEEL_IGNORE_IMAGE — Keel manages tag updates
|
||||
spec[0].template[0].spec[0].container[1].image,
|
||||
# container[1]=novnc now TF-managed on ghcr:latest (ADR-0002 #29) — was KEEL_IGNORE
|
||||
spec[0].template[0].spec[0].init_container[0].image,
|
||||
metadata[0].annotations["kubernetes.io/change-cause"],
|
||||
metadata[0].annotations["deployment.kubernetes.io/revision"],
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue