From 4b6da6f6de3d7a410f6d0f1ebf13084659b1db70 Mon Sep 17 00:00:00 2001 From: "motherofbots.eth" <126520850+apo77yon@users.noreply.github.com> Date: Thu, 16 Mar 2023 20:17:22 -0700 Subject: [PATCH] Update README.md --- kubernetes/node-server-example/README.md | 38 +++++++++++++++++++----- 1 file changed, 30 insertions(+), 8 deletions(-) diff --git a/kubernetes/node-server-example/README.md b/kubernetes/node-server-example/README.md index c15c0d4..5218812 100755 --- a/kubernetes/node-server-example/README.md +++ b/kubernetes/node-server-example/README.md @@ -1,32 +1,43 @@ -# Deploying a Node.js K8s Cluster with Kubectl +## deploying a node.js K8s cluster with kubectl + +
-Build the image: +1. Build the image: ``` make build: ``` +
-Run the container: +2. Run the container: ``` make run ``` -Check whether the server worked +
+ +3. Check whether the server worked ``` make curl ``` +
-Check container's status +4. Check container's status ``` $ make status ``` +
-#### Other useful commands +--- + +### useful commands + +
Exec inside the container: @@ -40,8 +51,13 @@ Check images in disk: $ docker images ``` +
-### Pushing the Registry to Kubernetes +---- + +### pushing the registry to kubernetes + +
In a real production system, we’ll want to build images in one place, then run these images in the Kubernetes cluster. @@ -66,7 +82,13 @@ Also, check out the service status with: $ kubectl get services ``` -### Clean up +
+ +--- + +### cleanning up + +
Removing the service and the deployment when you are done: