Dynamic IP address ( ranges IP ) for proxies

[sysadm.es]

I'm wondering about the posibility of work with dynamic proxies, pasting a pool of IP address or IP ranges.

Like in the agent you can post a row of servers separed by a comma

Zabbix server should listen a pool of proxies, this would be good in order to work with dinamic infraestructure like kubernetes clusters with a replica pod in each node.

At the moment you can work modify the network of your kubernetes cluster, should be good ( and much easier ) if zabbix will be able to listen a pool of IP's for proxies.

[kloczek]

Exact proxy is identified by its name which is part of the proxy setup.
Ergo: in case of active proxy the proxy IP or DNS name can change at any time.
In case of passive proxy settings needs to be updated after address change.
Generally if you can you should always use active proxies because in that case does not need to allocated fixed srv<>prx tcp session.
Each such connectivity it is single srv process and connectivity to the srv db backend which on the larger scale is biggest bottleneck.
With active proxies you can have smaller proxies connections pool than actual number of proxies.

The same principals are ruling what happens with connections to the agents.

[sysadm.es]

Exact proxy is identified by its name which is part of the proxy setup.
Ergo: in case of active proxy the proxy IP or DNS name can change at any time.
In case of passive proxy settings needs to be updated after address change.
Generally if you can you should always use active proxies because in that case does not need to allocated fixed srv<>prx tcp session.
Each such connectivity it is single srv process and connectivity to the srv db backend which on the larger scale is biggest bottleneck.
With active proxies you can have smaller proxies connections pool than actual number of proxies.

The same principals are ruling what happens with connections to the agents.

Yes, that's how a proxy works but doesn't have any relation with what i explain i believe.

Imagine:

I have a cluster with two nodes ( 192.168.1.75 MASTER & 192.168.1.76 WORKER ), the easiest scenario.
You have one DNS address ( zbx-prx-01.sysadm.local ) this is the address that you have bound in your Active Proxy in zabbix, and your zabbix server can resolv this address as A reg to 192.168.1.75 or even another proxy like any other CNAME, those DNS names will be resolved to the master node, becouse you can have 1 proxy replicated in 10 nodes ( each node has his own IP address ).

Zabbix server will bind the DNS address ( zbx-prx-01.sysadm.local ) to the resolved IP address, that's why when each replicated proxy ( same proxy ) will send the information, only the resolved DNS address will be accepted, as you can see in the pic, whole other address will be rejected.

At the moment if you wanna use kubernetes as proxy platform, must route each outbound address through one IP address ( the resolved IP address for zabbix-server ).

That's why in my opinion, dynamic ip ranges for accept connection is a good thing.

[kloczek]

This is why usiong CNAMEs in clustering is bad idea. You should be using separated VIP which should be moved between cluster nodes.
Other cons of usng CNAME is DNS TTL.