Agenda for the Flatcar Office Hours on Wednesday, 12th of March 2025, 2:30pm UTC

[miao0miao]

In the office hours we discuss news and happenings in and around Flatcar, provide a space for our user community to discuss with maintainers, show demos, and do our release planning.

• Jitsi: https://meet.flatcar.org/OfficeHours
• Youtube live stream / recording: link
  • All recordings: https://www.youtube.com/@FlatcarLinux/live
• Community Calls calendar (all future calls): Google Calendar
  • iCal version: ical

Welcome

• Brief intro/check-in of the new participants joining the call. Please introduce yourself and share what brings you here today.

Announcements

End of support for CGroupsV1 in early 2025

Flatcar will stop supporting the cgroups v1 backwards compatibility mode in Q1 2025.

• With our adoption of systemd-256, support for legacy CGroupsV1 will end in Alpha, Beta, and eventually Stable.
• Enabling legacy CGroupsV1 during deployment will not be supported anymore.
• Nodes that use CGroupsV1 legacy mode will fail to update. This ensures your workloads will not be disrupted. Enable CGroupsV2 on your legacy CGroupsV1 nodes in order to successfully update.
• LTS-2024 will support CGroupsV1 until late 2025.

Agenda items

• KubeCon attendance

Release Planning

• Flatcar tactical, release planning, and roadmap (view)

Administrative tasks after meeting concluded

• Create a new Github discussion for the next Flatcar Office Hours: https://github.com/flatcar/Flatcar/discussions/new?category=flatcar-office-hours
• Close this discussion as "Resolved".

[chewi]

More agenda items:

• We are switching from BIOS to UEFI on AWS where supported. This affects new deployments only.
• The /boot space issue. Maybe not go into too much detail. The user-facing aspects are:
  • We will make the UEFI (but not BIOS) bootloader upgradable.
  • We will move the kernel+initrd to /usr.
  • We will change where we store the verity hash.
  • The space savings will allow us to enable more drivers.

[miao0miao]

would you mind adding it to our next meeting @chewi ?