From ebf5fff96653adbc10d8a9e0bacd54e773672ef5 Mon Sep 17 00:00:00 2001
From: mbadibanga <83414778+mbadibanga@users.noreply.github.com>
Date: Sat, 9 Oct 2021 17:26:51 +0200
Subject: [PATCH] Apply the Virtual Gateway manifest file

kubectl command to apply the manifest file to the EKS cluster, without it there is no ingress to test ...
---
 content/virtualgateway/nodejs-ingress.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/content/virtualgateway/nodejs-ingress.md b/content/virtualgateway/nodejs-ingress.md
index 66c94cb..4b47dda 100644
--- a/content/virtualgateway/nodejs-ingress.md
+++ b/content/virtualgateway/nodejs-ingress.md
@@ -86,6 +86,8 @@ spec:
             name: nodejs
 ---
 EOF
+
+kubectl apply -f ~/environment/eks-scripts/app-mesh-virtual-gateway.yml
 ```
 If you take a close look at the previous manifest file, you will notice we added one GatewayRoute with a single route for path /eks. In practical terms this means any requests that arrive at the NLB with path /eks will get rerouted to the Virtual Service nodeJS.