test (e2e) : Add steps in Application Deployment Scenario to verify N…

…odePort Add additional steps in Application Deployment scenario to verify that application has Kubernetes Service and it's exposed as NodePort. Also application is accessible from outside the crc cluster using crc ip and Node Port. Signed-off-by: Rohan Kumar <[email protected]>
crc-org · Feb 28, 2025 · 44a78f3 · 44a78f3
1 parent f1e8c68
commit 44a78f3
Showing 1 changed file with 6 additions and 0 deletions.
diff --git a/test/e2e/features/application_deployment.feature b/test/e2e/features/application_deployment.feature
@@ -30,8 +30,14 @@ Feature: Application Deployment Test
         And stdout should contain "1/1     Running"
         And executing "oc get svc -lapp=quarkus" succeeds
         Then stdout should contain "quarkus"
+        # Access application via Route
         And executing "oc get routes -lapp=quarkus" succeeds
         Then stdout should contain "quarkus"
         And with up to "4" retries with wait period of "1m" http response from "http://quarkus-testproj.apps-crc.testing" has status code "200"
         Then executing "curl -s http://quarkus-testproj.apps-crc.testing" succeeds
         And stdout should contain "{"applicationName":"JKube","message":"Subatomic JKube really whips the llama's ass!"}"
+        # Access application via Service's NodePort
+        And executing "QUARKUS_NODEPORT=`oc get svc quarkus -o jsonpath='{.spec.ports[0].nodePort}'`" succeeds
+        And executing "CRC_IP=`crc ip`" succeeds
+        Then executing "curl -s http://$CRC_IP:$QUARKUS_NODEPORT" succeeds
+        And stdout should contain "{"applicationName":"JKube","message":"Subatomic JKube really whips the llama's ass!"}"