Bucket A retrigger + Bucket D enrollment (5 module-nested stacks)
After fixing the postgresql-lb MetalLB flap (deleted stuck
ServiceL2Status CR l2-rgt9d), Tier 1 CI can apply again. Combined
commit:
* Bucket A (16 stacks): re-append CI retrigger marker so the
previously-pending applies pick up:
blog calico cyberchef descheduler f1-stream homepage jsoncrack
k8s-dashboard k8s-version-upgrade kms local-path osm_routing
real-estate-crawler travel_blog vault webhook_handler
* Bucket D (5 module-nested stacks): keel.sh/enrolled label on
namespace + KYVERNO_LIFECYCLE_V2 on Deployments inside the module:
postiz instagram-poster k8s-portal uptime-kuma vaultwarden
Bucket C (raw-deploy apps without V1 marker on their Deployment
lifecycles) deferred — needs per-Deployment lifecycle block additions
that the bulk script can't safely automate:
beads-server immich llama-cpp novelapp plotting-book trading-bot
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This commit is contained in:
parent
629fe24305
commit
eb99ee5635
21 changed files with 67 additions and 7 deletions
|
|
@ -318,3 +318,5 @@ resource "kubernetes_manifest" "external_secret" {
|
|||
# CI retrigger v3 2026-05-16T14:06:39Z
|
||||
|
||||
# CI retrigger v4 2026-05-16T14:13:59Z
|
||||
|
||||
# CI retrigger v5 2026-05-16T23:10:38Z
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue