So this is a weird problem that had me all sorts of confused for a while.
I still don't know why it's happening, but at least I know what's going on.
I have an issue where proxmox itself can't access the internet, but vms can.
This all happened after I had moved and redid the network configurations on two cluster nodes to get them back on the new network Vlans.
They are both having this exact same issue.
New Gateway defined on the interface 10.15.99.1
Old Gateway that is somehow still being used 10.15.15.199
interface file on node 1 (node 2 looks exactly the same just incremented ip address)

Firewall log in opnsense showing proxmox trying to find the old gateway for DNS.

The cluster works just fine, both nodes are aware of each other and all vms / containers have no issues.
I also have another cluster that I did the exact same process for moving the management interfaces onto vlan 99 and both nodes on that cluster work just fine.
The only difference is, those two on the second cluster that is working were originally pointing to 10.15.15.1 which still exists on the network as I haven't phased that subnet out completely yet. I might end up with this same issue down the road now that I'm thinking about it.
Is there any other place that a gateway might be defined that would be messing with the interface config?
Thank you in advance for any guidance you can provide.
I still don't know why it's happening, but at least I know what's going on.
I have an issue where proxmox itself can't access the internet, but vms can.
This all happened after I had moved and redid the network configurations on two cluster nodes to get them back on the new network Vlans.
They are both having this exact same issue.
New Gateway defined on the interface 10.15.99.1
Old Gateway that is somehow still being used 10.15.15.199
interface file on node 1 (node 2 looks exactly the same just incremented ip address)

Firewall log in opnsense showing proxmox trying to find the old gateway for DNS.

The cluster works just fine, both nodes are aware of each other and all vms / containers have no issues.
I also have another cluster that I did the exact same process for moving the management interfaces onto vlan 99 and both nodes on that cluster work just fine.
The only difference is, those two on the second cluster that is working were originally pointing to 10.15.15.1 which still exists on the network as I haven't phased that subnet out completely yet. I might end up with this same issue down the road now that I'm thinking about it.
Is there any other place that a gateway might be defined that would be messing with the interface config?
Thank you in advance for any guidance you can provide.