From a227396e544f304e2aa2e82ffdc9daf5cf59fc58 Mon Sep 17 00:00:00 2001 From: vncmail-ci Date: Wed, 12 Aug 2026 13:21:01 +0000 Subject: [PATCH] chore(deploy): point prod overlay at sha-cfdd091d (not synced - manual gate in ArgoCD) [skip ci] --- .../k8s/overlays/prod/image-tag/kustomization.yaml | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/deploy/k8s/overlays/prod/image-tag/kustomization.yaml b/deploy/k8s/overlays/prod/image-tag/kustomization.yaml index d8191fe5..64820366 100644 --- a/deploy/k8s/overlays/prod/image-tag/kustomization.yaml +++ b/deploy/k8s/overlays/prod/image-tag/kustomization.yaml @@ -1,12 +1,11 @@ -# Owned by CI (the bump-prod job in .gitlab-ci.yml), not by hand — same -# reasoning as overlays/dev/image-tag/. Starts pointed at an obviously-fake -# tag on purpose: nothing has been promoted yet, and vncmail-prod's ArgoCD -# Application has manual sync anyway, so this being "wrong" doesn't deploy -# anything wrong — it just means there's nothing to sync until a real -# `git push` to main updates it. +# Owned by CI (bump-prod job in .gitlab-ci.yml) - regenerated every +# push to main. Do not hand-edit; edits here get overwritten. Bumping +# this is NOT the same as deploying it - vncmail-prod's ArgoCD +# Application has manual sync, see the note in the parent +# kustomization.yaml. apiVersion: kustomize.config.k8s.io/v1alpha1 kind: Component images: - name: vncmail-plus newName: registry.gitlab.vnc.biz/gitlab-instance-b9b5cf2f/vncmail-plus - newTag: not-yet-promoted + newTag: sha-cfdd091d