On Tue, Dec 31, 2019 at 09:36:58AM +0100, kvaps wrote:
>
> Of course you can use hostNetwork=true, but it is less secure and not
> redundant.
You can also use pipework or just correctly configure your firewall
rules. Either load the conntrack modules for tftp and nat, or use
additional software
On Tue, Dec 31, 2019 at 8:45 AM Kurt H Maier wrote:
> If you need this kind of functionality in Kubernetes you're much better
> off using a different CNI plugin to manage your networking. There's no
> inherent NAT requirement imposed by Kubernetes itself.
This is not about CNI networking,
On Mon, Dec 30, 2019 at 12:51:30PM +0100, kvaps wrote:
>
> Note that Kubernetes uses NAT for external services, so it's not possible
> to run TFTP-server for external clients there. There is one proposed
> solution for that, it suggests moving away from the RFC and implement
> --single-port option
