I think the issue is that you don't want a controller to do any of the routing. If you make a controller the default gateway of clients, you probably have to put a static route from your infrastructure to point to the controller so that traffic can find its way back to clients. You typically want the controller to be an overlay that bridges client traffic to an already established network.
It is administrative. If you feel strongly about it, go ahead and do it.
Others will want to do things like grow their networks or have redundant controllers and they will not be able to scale seamlessly. There is nothing stopping you from doing whatever you want.
At Aruba, we believe that the most dynamic customer experiences happen at the Edge. Our mission is to deliver innovative solutions that harness data at the Edge to drive powerful business outcomes.
© Copyright 2020 Hewlett Packard Enterprise Development LPAll Rights Reserved.