Home
Help
Search
Login
Register
OPNsense Forum
»
English Forums
»
General Discussion
»
Port Forwarding - for redundant services
« previous
next »
Print
Pages: [
1
]
Author
Topic: Port Forwarding - for redundant services (Read 1140 times)
MSandro
Newbie
Posts: 1
Karma: 0
Port Forwarding - for redundant services
«
on:
February 13, 2020, 03:04:15 pm »
Hi,
I am new to OPNSense, we use two OPNSense (20.1) Firewalls since a few weeks in test environments.
We operate a Kubernetes cluster in the internal network behind the two Firewalls (HA Cluster).
Lets say we are hosting an Web-Aplication for one of our customer, this is running on Port 8080. We can use NAT Port Forwarding to publish the internal Port from the Node where the App is running on to the Internet.
But if this node fails, the App will instantly initialize on an other Node.
So in souch an scenario normal Port Forwarding is not an option.
As the first possible solution I thought about an Script. It shuld check if a Kubernetes Workload is moving to an other Node, so it should automaticaly edit the Port Forwarding rule vie API.
But as I noticated, there are currently no API features to edit Firewall Rules
Is there any other solution at the moment? I have some basic knowledge about Networking but I don't know souch an advanced thing to solve my problem.
It would be very nice if someon could give me an hint. Maybe someon was in an simular situation.
Logged
Print
Pages: [
1
]
« previous
next »
OPNsense Forum
»
English Forums
»
General Discussion
»
Port Forwarding - for redundant services