migrating to new cgroups

[till]

Description

Followed instructions here: https://www.flatcar.org/docs/latest/container-runtimes/switching-to-unified-cgroups/#migrating-old-nodes-to-unified-cgroups

But I think it's missing rm /etc/flatcar-cgroupv1

Impact

Instance claims it's still running legacy cgroups (it probably isn't but there's something somewhere in the motd files that prints a message). Wonder if that file also blocks updates to the latest stable (which no longer supports legacy cgroups).

Environment and steps to reproduce

Create a new node with legacy cgroups enabled and try to migrate off of it.

Expected behavior

No more legacy cgroups.

[t-lo]

Thank you for creating this issue. This should be pretty straightforward, the docs in question are here: https://github.com/flatcar/flatcar-website/blob/main/content/docs/latest/container-runtimes/switching-to-unified-cgroups.md?plain=1#L23

[CodEZ47]

@t-lo can I work on this issue?

[t-lo]

@t-lo can I work on this issue?

@CodEZ47 No need to ask, patches are always welcome ☺️

[parv18050212]

Hi team 👋

I noticed that the unified cgroups migration guide in flatcar-website has already been updated with detailed steps, fallback instructions, and Kubernetes compatibility notes. Is there any further work expected for #1789 or can we consider this resolved?

Thanks!

[till]

Still missing what I found. Or how did you gather it was updated?