Bernd Rodler
177b2aca57
Direct SSH access to the actual clusters (node1-3 "prod" HA, dev-k8s-1-3
"dev") revealed two things that made the previous design wrong:
1. Neither cluster has vncmail/vnc-ca namespaces or a bulwark ingress at
all - the "live sandbox" referenced in this repo's docs/manifests was
never actually applied anywhere. Both ingress.yaml's ingressClassName
(public) and cert-manager issuer (letsencrypt-prod) were also wrong:
both clusters run Traefik (class is literally named `traefik`), and
only dev-k8s has any ClusterIssuer at all (`letsencrypt-staging`).
node1-3 has zero ClusterIssuers configured.
2. dev-k8s already has ArgoCD installed, idle, zero Applications - more
idiomatic to use it than have GitLab Runner execute kubectl directly.
Pivots .gitlab-ci.yml: build+push image, then commit the tag into a small
per-overlay Component (overlays/{dev,prod}/image-tag/) that ArgoCD's
Application watches - CI never touches the cluster, only the registry and
this repo. dev's Application (vncmail-dev) is registered and applied
already (manual sync for now, until the one-time namespace secret
bootstrap is done - see VNCMAIL-SETUP.md). prod's Application is
scaffolded in deploy/argocd/ but deliberately not applied - it targets a
different cluster (node1-3) that isn't registered with ArgoCD yet, and
there's still no real prod hostname/Stalwart/ClusterIssuer.
Fixes base/ingress.yaml to the real ingressClassName: traefik (was the
nginx-style `public`, which doesn't exist on either cluster) and gives
each overlay its own cert-manager issuer patch instead of one hardcoded
value, since dev and prod need different (or, for prod, nonexistent)
issuers.
22 lines
738 B
YAML
22 lines
738 B
YAML
apiVersion: kustomize.config.k8s.io/v1beta1
|
|
kind: Kustomization
|
|
namespace: vncmail-prod
|
|
resources:
|
|
- ../../base
|
|
- namespace.yaml
|
|
# - secret.yaml # create from secret.example.yaml; not committed
|
|
|
|
patches:
|
|
- path: patch-ingress.yaml
|
|
- path: patch-deployment.yaml
|
|
|
|
components:
|
|
- image-tag
|
|
|
|
# NOT MEANT TO BE SYNCED AS COMMITTED. Scaffolding only (see the pipeline
|
|
# plan's Phase C/D) — image-tag/'s placeholder tag is obviously-invalid on
|
|
# purpose. The bump-prod job in .gitlab-ci.yml keeps that tag pointed at
|
|
# whatever's already on dev once main advances, but vncmail-prod's ArgoCD
|
|
# Application has manual sync — a human still has to click Sync (or
|
|
# `argocd app sync vncmail-prod`) for any of this to actually apply.
|