Skip to content

Commit 2dca181

Browse files
committed
sample-app: Fix port of node-server-svc (80 to 8080)
Without this, following the instructions that don't require port forwarding (e.g. using "minikube tunnel") fails: the service is exposed on port 80, which is not what the frontend expects. After this commit the setup mimics that of the frontend service, which works both with and without port forwarding. Signed-off-by: Guzman <guzman@guzman.fi>
1 parent 0a9d913 commit 2dca181

File tree

3 files changed

+3
-3
lines changed

3 files changed

+3
-3
lines changed

code-samples/eventing/bookstore-sample-app/solution/node-server/config/100-deployment.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,6 +29,6 @@ spec:
2929
app: node-server
3030
ports:
3131
- protocol: TCP
32-
port: 80
32+
port: 8080
3333
targetPort: 8000
3434
type: LoadBalancer

code-samples/eventing/bookstore-sample-app/start/node-server/config/100-deployment.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,6 +29,6 @@ spec:
2929
app: node-server
3030
ports:
3131
- protocol: TCP
32-
port: 80
32+
port: 8080
3333
targetPort: 8000
3434
type: LoadBalancer

docs/versioned/bookstore/page-0.5/environment-setup.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -278,7 +278,7 @@ node-server-svc LoadBalancer 10.101.90.35 <pending> 80:31792/T
278278
If port forwarding is required, open a new terminal and run:
279279

280280
```shell
281-
kubectl port-forward svc/node-server-svc 8080:80
281+
kubectl port-forward svc/node-server-svc 8080:8080
282282
```
283283
You should see the following output:
284284

0 commit comments

Comments
 (0)