Closed awanaut closed 5 months ago
Hi @awanaut! Thanks for this report! I added constraints for the CNI plugin in https://github.com/hashicorp/nomad/pull/20244 but you're right that doesn't restrict the client version appropriately. I'll get this fixed for the final release.
Fix is up in #20623
Nomad version
Output from
nomad version
mix of 1.8-beta+ent and 1.7.4+entOperating system and Environment details
Debian 12 client nodes with Nomad 1.8-beta+ent and Consul 1.17.2 Debian 12 client nodes with Nomad 1.7.4+ent and Consul 1.17.2
Issue
When scheduling a job that contains the new transparent_proxy{} block, it seems Nomad will ignore that attribute and possibly schedule it on non-transparent proxy nodes. In my case it would be client nodes that are version 1.7.4. To workaround, I created a constraint for nomad.version to ensure it's schedule on the correct node.
Reproduction steps
Expected Result
I'm sure I could add in a health check, but I would expect Nomad to read the transparent_proxy{} block and read the attributes of the nodes before making the scheduling decision just like the other attributes.
Actual Result
Nomad will schedule transparent_proxy jobs on nodes without transparent proxy
Job file (if appropriate)