Let's FLEX with the new VMSS orchestration model and all it's great new capabilities! Please make sure to read the description for the chapters and key information about this video and others. ⚠ P L E A S E N O T E ⚠ 🔎 If you are looking for content on a particular topic search the channel. If I have something it will be there! 🕰 I don't discuss future content nor take requests for future content so please don't ask 😇 Thanks for watching! 🤙
@openalpha012 жыл бұрын
You videos are far more comprehensive than the official documentation.
@laurensbot2 жыл бұрын
That's the thumbnail we all looked forward to 😆 Thank you so much for another great video.
@NTFAQGuy2 жыл бұрын
lol
@AnushaKulkarni-h9h9 ай бұрын
Veey well explained, John 👏
@NTFAQGuy9 ай бұрын
Thanks! 😃
@lifechamp0072 жыл бұрын
Super helpful, as always - thank you John!! Stay blessed n happy ,,,
@NTFAQGuy2 жыл бұрын
My pleasure! You too.
@evolagenda7 ай бұрын
The last point about grouping constructs being the desired default is interesting. The thing I really liked about uniform was how easy it was to check the model version and update user data. That makes less sense when you're not grouping based on application. But it's still annoying that the only way to upgrade a flex node is to recreate it.
@fitzgeraldsteele2 жыл бұрын
I think my favorite 'flex' is your KZbin 100k Subscriber plaque casually in frame :D
@Cloud-rb9oo Жыл бұрын
This is cool. Azure may get to deprecate Availability Set and streamline the Cloud Product Catalog. :) Hope a single HostGroup supports multiple AZs . This would simplify deployment for folks who want VMSS on their own dedicated hosts.
@christianibiri2 жыл бұрын
Awesome! love Azure
@patrickboucher8922 жыл бұрын
merci John. Extremely clear. I assume I can see Availability Set as a workaround when AZ are not available in a specific region?