If you have an existing L3 gateway/router (your core switch, which I suppose is in a small network), I would use that and keep the controller as L2 as possible.
Clients need to send their traffic to a default gateway, and typically you would use an router/L3-switch for that. If your core switch has an IP in each VLAN and can route traffic; I would do it there. I also would probably put the DHCP on there as well and let the controller switch traffic. In SD-WAN scenarios this is different.
If your core does not have IP addresses in all VLANs, you could consider configuring those. It would work to route on the controller, but if you have something else that can do it, I would go for external routing.
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your HPE Aruba Networking partner, distributor, or Aruba TAC Support. Check
https://www.arubanetworks.com/support-services/contact-support/ for how to contact HPE Aruba Networking TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or HPE Aruba Networking.
In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
------------------------------