update

1 files changed, 10 insertions, 12 deletions

diff --git a/f3s/registry/README.md b/f3s/registry/README.md
index a5f6a16..3049532 100644
--- a/f3s/registry/README.md
+++ b/f3s/registry/README.md
@@ -14,26 +14,24 @@ This document describes how to push Docker images to the private registry deploy
 
 0.  **Create the registry directory in the NFS share**
 
-1.  **Get the NodePort of the registry service:**
+1.  **Tag your Docker image:**
 
-    ```bash
-    kubectl get svc docker-registry-service -o jsonpath='{.spec.ports[0].nodePort}'
-    ```
-
-2.  **Tag your Docker image:**
-
-    Replace `<your-image>` with the name of your local Docker image and `<node-ip>` with the IP address of any node in your Kubernetes cluster and `<node-port>` with the port obtained in the previous step.
+    Replace `<your-image>` with the name of your local Docker image and `<node-ip>` with the IP address of any node in your Kubernetes cluster. The registry is available on NodePort `30001`.
 
     ```bash
-    docker tag <your-image> <node-ip>:<node-port>/<your-image>
+    docker tag <your-image> <node-ip>:30001/<your-image>
     ```
 
-3.  **Push the image to the registry:**
+2.  **Push the image to the registry:**
 
     ```bash
-    docker push <node-ip>:<node-port>/<your-image>
+    docker push <node-ip>:30001/<your-image>
     ```
 
-4.  **Pull the image from the registry (from a Kubernetes pod):**
+3.  **Pull the image from the registry (from a Kubernetes pod):**
 
     You can now use the image in your Kubernetes deployments by referencing it as `docker-registry-service:5000/<your-image>`.
+
+## Communication
+
+The Docker registry is exposed via a static NodePort (`30001`) and uses plain HTTP. It is not configured for TLS.