Thanks. Great video. Something that I like to understand is why NSX/NCP creates a logical segment for each namespace? Is it possible to have one segment for all namespaces in a k8s cluster?
Great videos! The one comment is that you mention istio and say that nsx can replace all the l2-l7 products mentioned but nsx does not offer a service mesh as far as I know. There is tanzu service mesh but that is just commercialized multi cluster istio
Yes, I should have been more clear about that. The NSX "family" can cover all those use cases including service mesh, but not NSX-T on its own. I still think of it as NSX Service Mesh as the re-name to Tanzu Service Mesh is relatively recent.
![ค้าง (STILL) - GEMINI [ OFFICIAL MV ]](http://i.ytimg.com/vi/Ftxx3hk5vkU/mqdefault.jpg)
Thank you, excellent video. I appreciate you taking the time to explain this information is great detail.
Thank you, thanks for leaving a comment.
This is awesome
Thank you
Thanks. Great video.
Something that I like to understand is why NSX/NCP creates a logical segment for each namespace?
Is it possible to have one segment for all namespaces in a k8s cluster?
I’m really not sure. Try
Docs (dot) VMware (dot) com
Great videos! The one comment is that you mention istio and say that nsx can replace all the l2-l7 products mentioned but nsx does not offer a service mesh as far as I know. There is tanzu service mesh but that is just commercialized multi cluster istio
Yes, I should have been more clear about that. The NSX "family" can cover all those use cases including service mesh, but not NSX-T on its own. I still think of it as NSX Service Mesh as the re-name to Tanzu Service Mesh is relatively recent.
@@jasonmeers with the rate at which the tanzu portfolio names are changing it may be back to nsx service mesh soon 😜
genius
Thank you very much