This is a tricky one, but I think B and D are the way to go. You need the Service Engine Group for the load balancing, and the NSX Advanced Load Balancer Controller to tie it all together.
I'd go with B and E. The Avi Kubernetes Operator is important for integrating with Kubernetes, and the Service Engine Group is key for the load balancing itself.
B and D seem like the obvious choices here. You need the Service Engine Group to handle the actual load balancing, and the NSX Advanced Load Balancer Controller to manage the whole setup.
Yes, having both the Service Engine Group and NSX Advanced Load Balancer Controller prepared in advance will make the workload management process smoother.
Malcom
7 days agoAleisha
8 days agoKing
12 days agoCarmen
14 days agoRaina
17 days agoMyra
18 days agoBrock
29 days agoBen
8 days agoTran
11 days agoOdette
14 days agoHarrison
16 days agoShawna
1 months agoGladys
4 days agoElouise
7 days agoCheryll
9 days agoKatie
18 days ago