@brookelew Thank you! If I remember correctly, I mention this because in versions < 1.33 the revisionhistorylimit is immutable for STS. The field change isnt accepted, also e.g. if argocd is used it fails to sync, someone may try to delete an STS in order to get that diff applied and break their entire installation. It's more of a safe guard IMO.

There's a way to a get past that using kubectl delete sts <name> --cascade=orphan but then again for a critical installation like gitlab, i'm not sure this is a good idea.