mirrors/docker-netbootxyz
1
0
Fork 0
mirror of https://github.com/netbootxyz/docker-netbootxyz.git synced 2025-08-07 14:47:24 +02:00
Code Issues Packages Projects Releases Wiki Activity

Update readme.md

Browse Source
This commit is contained in:
EHerzog76 2024-12-09 13:05:36 +01:00 committed by GitHub
parent d88a3ac33e
commit f13c29f61d
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
kubernetes/readme.md
View File

@ -1,6 +1,6 @@
# Kubernetes Deployment example
This is an example of one possibilty how to deploy netboot.xyz to a OKD/OpenShift cluster.
This is an example of one possibilty how to deploy netboot.xyz to a OKD/OpenShift cluster.
You can also use it for a Kubernetes cluster, but in this case you will add your ingress configuration instead of the route.
## Edit PVC config
@ -43,10 +43,10 @@ kubectl -n network apply -f service.yaml
Please notice the service configuration for the service:
- svc-pxboot
this is from **type: NodePort**.
This is important, because after a TFTP-client requests a file,
the TFTP-Server will initiate a new connection and send data back to the client over this new connection.
So you must configure your **CNI** to **not** use source nat (**SNAT**) for this connections !
this is from **type: NodePort**.
This is important, because after a TFTP-client requests a file,
the TFTP-Server will initiate a new connection and send data back to the client over this new connection.
So you must configure your **CNI** to **not** use source nat (**SNAT**) for this connections !
CNI configs:
- calico [SNAT-Config](https://docs.tigera.io/calico/latest/networking/configuring/workloads-outside-cluster)
- cilium [SNAT-Config](https://docs.cilium.io/en/stable/network/concepts/masquerading/)