Closed grs closed 4 weeks ago
On further investigation the issue here is that the control plane assumes that false is the default for these attributes whereas they actually default to true, though they only actually have any effect if the http attribute is true (which it is not by default).
I am seeing unexpected values returned by a query of listeners for the attributes websockets, healthz and metrics.
In the following configuration file, these attributes are set to false for the listeners on ports 55671 amd 45671, bu it the query listed after that, they are returned as true. The listeners on ports 5671 and 5672 however seem to be set as expected (the difference between these is mostly in the role I believe). (Originally these attributes were not being set at all, but even with an explicit setting the values seem unexpected).
I got the following query results: