1 Answer
- Newest
- Most votes
- Most comments
0
Hi,
What are the rationale in having it done this way? I would suggest to use LoadBalancer type to expose your service to the Internet. Having it you will be able to have:
- your node group in the private subnet
- static IP address instead of having service bound to the one node to have the same
- potential HA if application you are running is supporting multiple instances at time
apiVersion: v1
kind: Service
metadata:
name: domino-nrpc
spec:
type: LoadBalancer
Relevant content
- asked 4 years ago
- asked a year ago
- Accepted Answerasked 4 months ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated a year ago
Unfortunately, I can not use Load Balancer.
Problem with Load Balancer is that I can not specify a target port on TCP 1352. Target Port should start at 30000.
And my pod has to listen, internaly and externaly, on port 1352. I can not change that.
Is similiar to having a POD with an SMTP Server that should listen on port 25 and you can not change that port since external clients would no be able to connect it...
I do not care to tie the pod to an specific node.