Relative canary and stable maintenance timing settings for projects at the folder level
Right now, it is possible to define maintenance windows for some GCP resources like Cloud SQL instances and GKE clusters at the resource level:
CloudSQL even allows to define relative maintenance timing settings
between instances in the same project: https://cloud.google.com/sql/docs/mysql/instance-settings#maintenance-timing-2ndgen
> The relative timing of updates is not observed between projects; if you have instances with an earlier timing setting in a different project than your instances with a later timing setting, Cloud SQL makes no attempt to update the instances with the earlier timing setting first.
However, I like to separate staging/pre-production and production environments in independent projects.
It would be awesome if GCP provided relative canary and stable maintenance timing settings for projects attached to a same organization, maybe at the folder level.
That way, I'd be able to define staging/pre-production projects as "canary" and production as "stable" to get updates earlier in the former.
When disruptions would be noticed in staging/pre-production during maintenance, fixes could be implemented or on-call could be prepared when the same maintenance will happen in production.