Hello,
The current TCP Service ConfigMap
<https://www.haproxy.com/documentation/kubernetes/latest/community/configuration-reference/controller/#--configmap-tcp-services>
is
relatively limited. For our use case, we are looking for the following
options to configure routes to TCP services:
* routing based on source IP
* routing directly to a pod instead of only to k8s services, this also adds
the requirement for the resolvers option
Something like this:
```
apiVersion: v1
kind: ConfigMap
metadata:
name: tcp
namespace: haproxy-controller
data:
3306: # Port where the frontend is going to
listen to.
service/mysql-ns/mysql:3306 # Kubernetes service in the format
ResrouceType/NS/Name:Port
pod/ns/service-pod:3306 # Routes to service-pod
service/redis-ns/redis:6379:sourceIP=10.10.10.10 # Routes to target if
sourceIP matches
```
Since pod IPs are not static it might be better to allow using the k8s pod
DNS It's mentioned here
<https://cbonte.github.io/haproxy-dconv/2.2/configuration.html#5.3.1> that
HAProxy will resolve at runtime.
Let me know if this is reasonable and how we would go about implementing it.
Thanks,
Yi
Disclaimer
The information contained in this communication from the sender is
confidential. It is intended solely for use by the recipient and others
authorized to receive it. If you are not the recipient, you are hereby notified
that any disclosure, copying, distribution or taking action in relation of the
contents of this information is strictly prohibited and may be unlawful.
This email has been scanned for viruses and malware, and may have been
automatically archived by Mimecast, a leader in email security and cyber
resilience. Mimecast integrates email defenses with brand protection, security
awareness training, web security, compliance and other essential capabilities.
Mimecast helps protect large and small organizations from malicious activity,
human error and technology failure; and to lead the movement toward building a
more resilient world. To find out more, visit our website.
