<p>I have requirement for setting SNMP client running on Kubernetes pod from where i need to send traps to SNMP alarm manager which is not Kubernetes based. Now, there are two problems:</p>

<ol>
<li><p>SNMP trap client send alarm with source IP and if i have more than one client then they are reaching on SNMP Alarm manager from same source IP i.e worker node IP.</p></li>
<li><p>SNMP Alarm Manager is sending trap to worker node IP on every 2 mins as per design and getting heartbeat failure as no SNMP client is running on worker node. As SNMP client is running on POD and for reaching pod in ingress we need Load balancer IP.</p></li>
</ol>

<p>Now it would have been resolved if we could have set source IP as Load Balancer IP for SNMP alarm manager to get traps from same IP and send get to same Load Balancer IP.</p>

<p>Looking forward for your suggestions on it.</p>

Rohit Sharma
<p>If you run your pods on <code>hostNetwork</code>(set the field <code>hostNetwork: true</code> in your pod template) then your pod's and worker node IP will be same.
This will solve the problem where the reply from SNMP Alarm Manager got missed.</p>

<p>If you want to run multiple SNMP clients then you can run them on different worker nodes with <code>hostNetwork</code> and all of them will have different IP address.</p>
