I would like To customize the Source-IP of a custom deployments for all traffic going outside the cluster.
Following this stack exchange: https://stackoverflow.com/questions/60113934/how-to-modify-source-ip-for-a-pod-in-kubernetes
Our setup result in multiples Kubernetes clusters deployed across multiples VLANs. We would like to allow our deployments within Kubernetes to use a custom IP (for external traffic) in order to restrict the access from our firewalls as well toward applications not hosted on Kubernetes.
My question is: Is it by design possible to pool from Metallb configmap (or some other solutions) a private IP and bind it to all traffic coming from a specific deployment and going outside our Kubernetes Cluster in order to use our NextGen Firewall. ?
