vSphere 7 Kubernetes Hot Take
Transcript
hey guys go on teeth townsend from the CTO of Iser hopefully on in frame i'll pull back a little bit more just to make sure this is the first time i'm trying to use this with the front-facing camera we're going to talk about vmware vsphere 7 in kubernetes and my reaction to the tech field day presentation from third this past Thursday you know what for our marathon were they covered way too much material in for ingest a four hour period I think they touched five or
six different products within that time so we couldn't go into death in some of the areas that I wanted to go to personally I love just be back to the VMware team next time you guys do a tech building presentation to mount a massive number of announcements I personally prefer to spend a lot of time deep diving into the bigger portions of it that really impact the entire ecosystem specifically this vSphere 7 release with support for kubernetes so we're going to talk about that primarily today
you get specific questions at me on twitter at CTO advisor on twitter cuz i'm not watching the periscope feed so first off it wasn't what I expected and that's not necessarily a bad thing is more of a gut reaction when Pat and team announced kubernetes on vSphere during vent world 2019 I expected kubernetes on the sphere what do I mean by that so what the CRX and making and elevating kubernetes to equal tenant as a virtual machine is basically bare metal kubernetes on vSphere so what
I expected was if you're a vSphere customer you could be a licensing I expected some level of Licensing tie into that so you know you might have to be a be spear Enterprise or whatever the equivalent version of the highest version of V spear itself in order to get that feature set you need it to be a customer at that licensing level makes sense if you're running kubernetes on vSphere you're probably doing it at scale so you require the highest licensing for vSphere that's not what
it is what it is is an extension of VMware Cloud foundation so what does that mean VMware cloud foundation built on VMware vSphere Innis xt and i think some v realized we basically the ability to run these beer or sddc a reference design for sddc software-defined data centers vmware sees it across any environment google cloud simple is based off of VCF lien where cloud foundation or VMware cloud V cloud providers all leverage VCF to make sure you get a consistent experience across all of the VMware
vCloud partners including cloud partners versus Microsoft Azure in Google cloud simple so that means that I have to deploy VCF near without foundation in order to get kubernetes is that a bad thing what if I want VMware cloud whatever I want VMware Cloud foundation no not at all if I'm already bought into that concept but if I bought into the higher end software-defined data center concept of VMware has been selling us for the past 10 years I don't need VCF to have a bit more clout
to have a VMware cloud foundation type experience I could go with NetApp storage dil UMC storage basic beast which is coming out vsphere I can build a very robust software-defined data center without the opinionated approach of VCF so when you bring when you bought both kubernetes on to that and forced me to use kubernetes with VCF and primarily the impact is that I have to use NSX T and if I feel we're customers talking containers I'm going to use n SXT I don't have a problem
with that the biggest thing I think is the and I haven't gotten an answer from them where is tying the use of this and for the management platform for kubernetes for tenzou kubernetes I'm not quite clear as to why that's needed it's just keeping as I understand it state and sharing speed across PI across clusters across the tenzou grid on a shared storage underlay my concept of understanding of VM FS VMware's file system is that it is distributed distributed file system across all your V spear
holes if I don't have beasts in I still have VMFS I don't see why being where it could have not just extended VMFS to give whatever capability that V sin was giving why do I have a problem because you can obviously use once you've deployed beasts and for this small dependency you can use whatever storage you want for your permanent and persistent storage layer for your pots and applications this is just for tenzou management it creates complexity if I need to deploy V send as a
base capability to get the benefits of tenzou then then were really needs to quantify why I'm adding another layer of complexity to my environment how is that adding complexity well I'm running be sad I'm running a enterprise storage platform this end is not a toy is not you know it's not a storage appliance like we saw in the early days of Software Defined neck it is a full enterprise class storage solution and I'm deploying it for a single requirement of kubernetes management configuration state I'm I'm
a little bit taken aback up by that requirement so that's kind of the if there's a negative there's a negative I'm just not understanding why I need to deploy this and I'm not sure why VMware it didn't give what I interpreted as a promise of allowing kubernetes to run on vSphere without me adding on the BCF licensing scheme that just reeks of just licensing to me second uh takeaway namespaces Wow VMware really killed it with this idea so they demonstrated this throughout all of their demonstrations
with net incitement net their net network insight project product V realized in general beasts and eventually to VMware storage beasts and storage and then even obviously to kubernetes and then eventually to virtual machines the ability to apply namespaces and namespace management to be spirit constructs so instead of going independently into the API to provision network storage of computer whatever I'm making a PA API calls to namespaces this is how application development works if you hear a little bit of excitement in my voice it is because
it is a exciting innovation I haven't thought about applying the concept of namespaces to the software-defined data center in general so I'm really excited to see how the folks in the industry are infrastructures cold folks take these new constructs for virtual machines networking and storage and the software-defined data center and extended I'm even more excited about that then kubernetes coming to the spear and gentlemen I'm not overly ecstatic about that that's kind of like okay whatever what any other vSphere seven enhancements that really struck to
me I think the only other thing is how am I going to consume this thing the namespace thing is a huge learning curve period implementing tenzou we haven't even gotten into the not opinionated approach that VMware took torch kubernetes net been events over at net on the clouds took the position that VMware wasn't aggressive enough or opinionated enough on the point kubernetes so deploying and managing kubernetes itself isn't as simple you still have to meet all the design decisions you needed to make before with kubernetes
inside of ten zoo and project pacific whatever it tends to whatever project pacific is called now I think it's ten ten zoom create basically so I'm not overly excited about kubernetes on V spear in general I'm just mostly excited about about namespaces I'd love to hear what you're excited about let me know on Twitter at CTO visor on Twitter followed me on the web the CTO advisor dot-com more importantly register for the conference the virtual conference happening April 21st it is CTO AV c-calm CTO advisor
virtual conference dot-com free tunein users still looking for sponsors talk to you next CTO dos video livestream whatever we call it
