From 00bbbe0838fd5b7838799a437e7bc9b218ae881f Mon Sep 17 00:00:00 2001
From: Viktor Barzin <vbarzin@gmail.com>
Date: Tue, 26 May 2026 08:19:24 +0000
Subject: [PATCH] url/shlink-web: containerPort 8080 -> 80

shlinkio/shlink-web-client:0.1.1 listens on port 80 (nginx default),
not 8080 like the prior :latest images. Keel auto-bumped the tag
on 2026-05-23; liveness/readiness probes have been failing ever since
because they still hit :8080. Pod was stuck restarting, the
DeploymentReplicasMismatch alert fired.

Aligns containerPort + both probes + service target_port with the image.
---
 stacks/url/main.tf | 11 +++++++----
 1 file changed, 7 insertions(+), 4 deletions(-)

diff --git a/stacks/url/main.tf b/stacks/url/main.tf
index 99823ebd..62001de0 100644
--- a/stacks/url/main.tf
+++ b/stacks/url/main.tf
@@ -377,13 +377,16 @@ resource "kubernetes_deployment" "shlink-web" {
               memory = "64Mi"
             }
           }
+          # shlinkio/shlink-web-client >=0.1.0 listens on port 80 (nginx default);
+          # prior :latest builds listened on 8080. Keep both probes + service
+          # target_port aligned with the image.
           port {
-            container_port = 8080
+            container_port = 80
           }
           liveness_probe {
             http_get {
               path = "/"
-              port = 8080
+              port = 80
             }
             initial_delay_seconds = 15
             period_seconds        = 30
@@ -393,7 +396,7 @@ resource "kubernetes_deployment" "shlink-web" {
           readiness_probe {
             http_get {
               path = "/"
-              port = 8080
+              port = 80
             }
             initial_delay_seconds = 5
             period_seconds        = 30
@@ -436,7 +439,7 @@ resource "kubernetes_service" "shlink-web" {
     port {
       name        = "http"
       port        = 80
-      target_port = 8080
+      target_port = 80
     }
   }
 }