4 ms·

Wait, how can this version churn even happen : don't they have a range of versions they support between open beta and long term support ones ? Unless the "long"

Wait, how can this version churn even happen : don't they have a range of versions they support between open beta and long term support ones ? Unless the "long" term support one has a comically short term ??

Radim 3y ago
The OP may have – unwillingly and unwittingly – become a part of the SaaS product's testing team. This happens more often that people realize. Behind the scenes, SaaS can be a shit show: Customer files a ticket => SaaS devs cannot reproduce (or don't bother to reproduce) but fix the presumed bug maybe => a new SaaS release => notify customer to upgrade, close their ticket => wait for response from the customer to see if the fix helped. Rinse & repeat, act aloof. Pretend it's the customer's fault all along.
- deathanatos 3y ago
  100% I've been in that cycle.
deathanatos 3y ago
> don't they have a range of versions they support between open beta and long term support ones ? Clearly not. Azure AKS is in this category. I think the upgrade cadence is (roughly, it isn't always the same) once per every 3 months, or you'll end up on an unsupported version. The support window is longer — about a year — but that's really only how long you can put off an upgrade if you're at the top of the window, and it's not sustainable. (And if you're running on fumes like I am and at the back end of the support window, then it's effectively 3 months of support, then I have to upgrade or the support ticket gets closed.) (Further, AKS has restrictions/gotchas that can prevent you from upgrading. That won't stop support from closing tickets though! We had to abandon & recreate an AKS cluster due to that, and it was a quarter of work for me.) Azure Gateway: we have a gateway from them that is simply no longer supported. They have other "SKUs", but there is no way for us to transition from our current SKU to a still-supported SKU. (Short of outright deleting the gateway and recreating it, which would be such a colossal pain that at that point I'm self-hosting.) RDS, although this was a few years back; it seemed like that was the only response we ever got from them in support tickets. It seemed like new minor versions rolled out pretty frequently. (IIRC, on the order of monthly.) (We had several issues with servers ending up with the wrong certificate, as well as with failovers exceeding their SLA.)

Radim 3y ago

The OP may have – unwillingly and unwittingly – become a part of the SaaS product's testing team. This happens more often that people realize. Behind the scenes, SaaS can be a shit show: Customer files a ticket => SaaS devs cannot reproduce (or don't bother to reproduce) but fix the presumed bug maybe => a new SaaS release => notify customer to upgrade, close their ticket => wait for response from the customer to see if the fix helped. Rinse & repeat, act aloof. Pretend it's the customer's fault all along.

deathanatos 3y ago
100% I've been in that cycle.

deathanatos 3y ago

> don't they have a range of versions they support between open beta and long term support ones ? Clearly not. Azure AKS is in this category. I think the upgrade cadence is (roughly, it isn't always the same) once per every 3 months, or you'll end up on an unsupported version. The support window is longer — about a year — but that's really only how long you can put off an upgrade if you're at the top of the window, and it's not sustainable. (And if you're running on fumes like I am and at the back end of the support window, then it's effectively 3 months of support, then I have to upgrade or the support ticket gets closed.) (Further, AKS has restrictions/gotchas that can prevent you from upgrading. That won't stop support from closing tickets though! We had to abandon & recreate an AKS cluster due to that, and it was a quarter of work for me.) Azure Gateway: we have a gateway from them that is simply no longer supported. They have other "SKUs", but there is no way for us to transition from our current SKU to a still-supported SKU. (Short of outright deleting the gateway and recreating it, which would be such a colossal pain that at that point I'm self-hosting.) RDS, although this was a few years back; it seemed like that was the only response we ever got from them in support tickets. It seemed like new minor versions rolled out pretty frequently. (IIRC, on the order of monthly.) (We had several issues with servers ending up with the wrong certificate, as well as with failovers exceeding their SLA.)