The MSA 2052 (SAN) doesn't support LACP on its Controllers' host ports facing the storage network(s) so you need to rely on MPIO or MCS implementations (references here, here, here, here and here<-- look for any reference about SAN iSCSI topology, SAN cabling and/or controllers' host ports configuration through CLI/SMU)...I think that topologically speaking if two 10G Switches are going to be used between your hosts and the MSA SAN controllers - so for your storage network portion or along with the production network - you could deploy these two Switches as either an IRF stack (AKA adopting the virtual switching approach) or as two standalone separate devices...in both cases LACP between MSA host ports and those Switches is not supported. Production Network links can instead be deployed using LACP between your hosts and the above switches (if collapsed approach is used) or to other if you segregate Storage/Production networks using totally different devices.
Edit: I think I found the document you can use as generic baseline for your iSCSI deployment. It's not based around MSA storage series but it explains some concepts and provide some suggestions that can be easily generalized (Network best practices, VLAN Tagging, iSCSI MPIO, etc.). It also treat separated storage/production or collapsed storage+production network scenarios (clearly all is biased on HPE FlexNetwork/FlexFabric Ethernet Switch series implementations - Standalone or IRF - that support FCoE/iSCSI protocols on their ethernet ports and HPE ProLiant servers hosts). Download it here. I admin I wasn't able to find a Validated Reference Design (VRD) about HPE MSA 2052 (or just 2050) SAN using iSCSI with possible detailed networking scenarios explained.