From a3aaf430294300a15570823ff8be1da9714b794f Mon Sep 17 00:00:00 2001
From: Sumit Ghosh <13281246+sughosneo@users.noreply.github.com>
Date: Wed, 13 Jan 2021 19:37:02 +0530
Subject: [PATCH] Fixed Doc bug #1577

---
 Deploy-to-Local-Kubernetes.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/Deploy-to-Local-Kubernetes.md b/Deploy-to-Local-Kubernetes.md
index 11d4249..95e2622 100644
--- a/Deploy-to-Local-Kubernetes.md
+++ b/Deploy-to-Local-Kubernetes.md
@@ -360,10 +360,11 @@ helm uninstall $(helm ls --filter eshop -q) --dry-run
 
 You can expose internal services by using [NodePorts](https://kubernetes.io/docs/concepts/services-networking/service/#nodeport) (among some other options)
 
-To expose the SQL Server service and the RabbitMQ admin port, when deploying to local Kubernetes, you can run the following script, from the `k8s` folder:
+To expose the SQL Server service and the RabbitMQ admin port, when deploying to local Kubernetes, you can run the following commands, from the `k8s` folder:
 
 ```powershell
-.\deploy-nodeports.ps1
+kubectl apply -f .\nodeports\rabbitmq-admin.yaml
+kubectl apply -f .\nodeports\sql-services.yaml
 ```
 
 This will expose the following infrastructure services: