This is an automated archive made by the Lemmit Bot.

The original was posted on /r/sysadmin by /u/adstretch on 2023-10-07 05:18:19.

Is anyone else getting burnt out chasing / managing the upgrades related to modern release cycles?

I’m finding more and more of my job is not maintaining a functioning environment but just keeping up with release cycles and trying to make sure what is coming down the road isn’t going to kill our environment.

Even if we aren’t prepping to move to new releases we need to confirm support for our existing releases and make sure no auto or unattended upgrades will force us there. Sometimes we don’t even get to kick the can that far down the road. (Looking at you 90 day deferral for macOS and iPadOS)

Dealing with aging VMWare (6.5), windows 10 -> 11. Windows server 2012r2/2016 -> 2022, macOS 14, iOS 17, palo 9.1 going eol, 18.04 going eol (yes I know this was LTS and we were way out ahead of it).

I generally keep my head above water with all of them but the fast past major release cycle is killing me. I’ll take 5+ years of minor patches and minor feature upgrades over all of these 1-2 year rewrites and major changes.

The upgrades would be easier to deal with too if so many of them weren’t buggy disasters at launch, but so many are.

That doesn’t even include Microsoft trying to kill off all their established on-prem services and pushing everything to Azure/entra.

/rant