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
25 days agoAleisha
26 days agoCiara
7 days agoStephaine
13 days agoHyman
15 days agoKing
30 days agoCarmen
1 months agoRaina
1 months agoMyra
1 months agoBrock
2 months agoBen
26 days agoTran
29 days agoOdette
1 months agoHarrison
1 months agoShawna
2 months agoGladys
22 days agoElouise
25 days agoCheryll
27 days agoKatie
1 months ago