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
2 months agoAleisha
2 months agoCiara
1 months agoStephaine
1 months agoHyman
1 months agoKing
2 months agoCarmen
2 months agoRaina
2 months agoMyra
2 months agoBrock
3 months agoBen
2 months agoTran
2 months agoOdette
2 months agoHarrison
2 months agoShawna
3 months agoGladys
2 months agoElouise
2 months agoCheryll
2 months agoKatie
2 months ago