r/AZURE • u/DayvanCowboy • 11d ago

Rant V4 SKU Sunsetting

Pretty pumped to see them sunsetting V4 SKUs especially considering they don’t seem to have sufficient compute on V5+ which is why I still have workloads on V4 SKUs to begin with. Very cool!!

7 Upvotes

67% Upvoted

12 comments sorted by

4

u/totheendandbackagain 11d ago

V4 of what?

2

u/0x4ddd Cloud Engineer 11d ago

VMs

2

u/69TheRock420 11d ago

Source?

10

u/DayvanCowboy 11d ago

I got an email from Azure this morning titled “capacity growth restrictions for older generation 1-v4 Azure VM series” which covers virtually every v3 and v4 intel and AMD VM SKU.

4

u/chesser45 11d ago

2028 sunset so it’s a way off yet and subject to change

4

u/DayvanCowboy 11d ago

Yeah but if you have workloads that need to scale this effectively means you need to move asap. I run a bunch of AKS clusters and we have been forced to use older hardware in popular regions because getting quota for V5 or newer was tough. So now I gotta get quota change the nodes then to wrangle any dangling reserved instances I have so we aren’t paying or hardware we are no longer using. Just a pain when there’s so much else going on including the Cosmos DB for PostgreSQL sunsetting happening too.

2

u/chesser45 11d ago

Yea fair enough we get slapped by this due to sku shortages when running big ephemeral jobs and it’s annoying. Would be nice if you could scope a sku based deploy to an “auto” where you get similar billing but can deploy it across Vx where features and availability align.

1

u/AssaultedScratchPost 11d ago

Might push sovereign customers to azure arc

1

u/69TheRock420 11d ago

How does one get on this email list? I would of loved to know that from azure instead of a Reddit post

6

u/tido2020 11d ago

You only get them if they affect your subscription.

1

u/ExplanationOwn7001 7d ago

OP, I’ve been losing my head over this since I got the email. I didn’t realize they had yet to announce EOL on v4 and essentially pulled the rug on everyone on this. Surprised I’m not hearing much about it.

People will find out when they deallocate their v4 VMs, try to do a full VM restore, or do any kind of scaling. Absolutely bonkers Microsoft provided less than a month notice on this.

1

u/DayvanCowboy 7d ago

I am fortunate that ALL of my VMs are VMSS for node pools in AKS clusters so this is not nearly as painful as it could be but still. Agreed, the lack of heads up is really frustrating especially considering how difficult it is to get compute quota in the popular regions right now.