Can grains contains the ip of minion connection to the master?

[rodgerzh]

Then we can use the minion connection ip,like:
salt -G 'connection_ip:x.x.x.x' test.ping
Perhaps it is useful.
When the minion has multiple ips,we must use the right one.

[Ch3LL]

I do not see a specific grain for the IP address used to connect to the master. But if your objective is to just target a minion based on its ip address you can use ip address matching: https://docs.saltstack.com/en/latest/topics/targeting/ipcidr.html

salt -S 192.168.40.20 test.ping

[rodgerzh]

-S can not use * or list to match several targets,like
-S 192.168.4*.20
-S 192.168.40.20,192.168.40.21

-G ipv4:192.168.4*.20 can match sereral targets,but can not match the connecting ip when use NAT.
salt-run manage.present show_ipv4=true can show the connecting ips use NAT.But it is not salt command.

[rodgerzh]

Another scenario like:

minion-1:
  - 192.168.20.41  (connected to master)
  - 192.168.20.42
minion-2:
  - 192.168.20.42  (connected to master)
  - 192.168.20.43

If I want to just let minion-2 to do test.ping,
but salt -S 192.168.20.42 test.ping will let both minion-1 and minion-2 to do test.ping.

[Ch3LL]

i'll go ahead and approve as a feature request. Seems it might be good to add targeting for connected minions. Looks like the manage.present salt runner uses ckminions.connected_ids(show_ip=show_ip, subset=subset) to get the ip addresses for connected minions so we could use that similar logic.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue.

[stale[bot]]

Thank you for updating this issue. It is no longer marked as stale.