diff options
| author | Paul Buetow <paul@buetow.org> | 2025-07-30 14:37:40 +0300 |
|---|---|---|
| committer | Paul Buetow <paul@buetow.org> | 2025-07-30 14:37:40 +0300 |
| commit | d0a0804fbfcade7893c5c215ea4b2fea830efbd3 (patch) | |
| tree | b8232dafae554e61c93cbcc807b89a1d32fd6da4 | |
| parent | 0801cfdf018b003f9cceddb5254fbe5f24d9232b (diff) | |
update
| -rw-r--r-- | f3s/registry/README.md | 22 | ||||
| -rw-r--r-- | f3s/registry/pv.yaml | 5 | ||||
| -rw-r--r-- | f3s/registry/pvc.yaml | 2 | ||||
| -rw-r--r-- | f3s/registry/service.yaml | 1 |
4 files changed, 16 insertions, 14 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. diff --git a/f3s/registry/pv.yaml b/f3s/registry/pv.yaml index 74a6583..fb747ca 100644 --- a/f3s/registry/pv.yaml +++ b/f3s/registry/pv.yaml @@ -5,7 +5,10 @@ metadata: spec: capacity: storage: 5Gi + volumeMode: Filesystem accessModes: - ReadWriteOnce + persistentVolumeReclaimPolicy: Retain hostPath: - path: "/data/nfs/k3svolumes/registry" + path: /data/nfs/k3svolumes/registry + type: Directory diff --git a/f3s/registry/pvc.yaml b/f3s/registry/pvc.yaml index 192013c..e769c89 100644 --- a/f3s/registry/pvc.yaml +++ b/f3s/registry/pvc.yaml @@ -4,9 +4,9 @@ metadata: name: docker-registry-pvc namespace: infra spec: + storageClassName: "" accessModes: - ReadWriteOnce resources: requests: storage: 5Gi - storageClassName: local-storage diff --git a/f3s/registry/service.yaml b/f3s/registry/service.yaml index 35c6fac..a97f14e 100644 --- a/f3s/registry/service.yaml +++ b/f3s/registry/service.yaml @@ -10,4 +10,5 @@ spec: - protocol: TCP port: 5000 targetPort: 5000 + nodePort: 30001 type: NodePort |
