Stephen Levine

/remove-lifecycle rotten

@nikolay I can't seem to replicate your issue: ``` stephen@laptop test % yj -jc { "map": { "a": "1", "b": "2", "c": "3" } } "map" = { "a" =...

This feature is also useful for kube-dns. CC: @kvedurmu

Still seems important to me :) Not sure why the label was removed

> @sclevine This is relevant for you as well, you are going to run into a similar problem with /var/lib/teleport. Less worried about this for agents, given that it's much...

@rosstimothy @fspmarshall ready for scalability review 🙂

@russjones FYI: after chatting with Tim, I'm going to move the `cluster_maintenance_config` fields to a new `cluster_autoupdate_config` resource, so we have a clear UX for migrating to the new system,...

Notice: I moved groups into MVP, so that the first delivered version of this proposal will allow, e.g., separate staging and production groups that are updated at different times. Only...

Hey @adrian-doyensec, we expanded the scope of this RFD so that it supports dividing agents into groups that can be scheduled to update at different times. It also supports limiting...

Continued in https://github.com/gravitational/teleport/pull/47126