From 9eae7cf25e09a856e9cb06fdc9fbe81d5d94e877 Mon Sep 17 00:00:00 2001
From: benbierens <thatbenbierens@gmail.com>
Date: Thu, 1 Jun 2023 12:44:48 +0200
Subject: [PATCH] Fixes issue where containers with no exposed ports cannot
 start.

---
 KubernetesWorkflow/StartupWorkflow.cs | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/KubernetesWorkflow/StartupWorkflow.cs b/KubernetesWorkflow/StartupWorkflow.cs
index 96706a9..59fe617 100644
--- a/KubernetesWorkflow/StartupWorkflow.cs
+++ b/KubernetesWorkflow/StartupWorkflow.cs
@@ -98,7 +98,7 @@ namespace KubernetesWorkflow
         {
             var serviceName = "service-" + numberSource.WorkflowNumber;
             var namespaceName = cluster.Configuration.K8sNamespacePrefix + testNamespace;
-            var port = recipe.ExposedPorts.First().Number;
+            var port = GetInternalPort(recipe);
 
             return new RunningContainerAddress(
                 $"http://{serviceName}.{namespaceName}.svc.cluster.local",
@@ -111,6 +111,12 @@ namespace KubernetesWorkflow
             return 0;
         }
 
+        private static int GetInternalPort(ContainerRecipe recipe)
+        {
+            if (recipe.ExposedPorts.Any()) return recipe.ExposedPorts.First().Number;
+            return 0;
+        }
+
         private ContainerRecipe[] CreateRecipes(int numberOfContainers, ContainerRecipeFactory recipeFactory, StartupConfig startupConfig)
         {
             log.Debug();