Agenda for the Flatcar Developer Sync on Wednesday, 26th of March 2025, 2:30pm UTC

[tormath1]

In our monthly Flatcar developer syncs maintainers review development / roadmap progress, discuss special projects like OS composability, secure / trusted boot, vendor support, and CNCF incubation status. We provide an overview of ongoing work, give an outlook of future work, and plan the next release.

Join if you're curious about current or future Flatcar development and/or to raise visibility of a feature, bug, or PR.

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

Welcome

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

News and 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.

Monthly Contributions and Advisory status Review

1. Discuss the latest Monthly Contributions Report
   • First-Time Contributors in last 2 months:
     • @reavessm: for a great documentation to setup HA Kubernetes
     • @dreamingdeer: fixed some Ignition documentation
     • @bexelbie: add some documentation around systemd user units
2. Review of last month's advisory stats in the latest Contributions Report
   a. Advisory status and planning: Flatcar tactical, release planning, and roadmap (view)

Ongoing and Planned Tasks Review

Discussion

• add "infra-rework" and "Nebraska" tabs to project board: Flatcar tactical, release planning, and roadmap (view)

1. Roadmap review: Flatcar tactical, release planning, and roadmap (view) (@t-lo, @miao0miao )
2. Projects status review:
   a. Composable OS: sysext and ClusterAPI (@tormath1) - Flatcar tactical, release planning, and roadmap (view)
   b. SecureBoot / Trusted Boot (@sayanchowdhury ) - Flatcar tactical, release planning, and roadmap (view)
   c. CNCF Incubation process (@miao0miao) - Flatcar tactical, release planning, and roadmap (view)
   d. Flatcar infrastructure status (@tormath1) - Flatcar tactical, release planning, and roadmap (view)
3. Maintainer team tactical / implementation (aka "line work") status review (@sayanchowdhury): Flatcar tactical, release planning, and roadmap (view)
4. Open Mic: Work to assign / User issues and PRs to discuss?

Release Planning

• Ongoing and upcoming releases tracker: (Flatcar tactical, release planning, and roadmap (view)) (@sayanchowdhury)
• Talk about the upcoming release and the status of the packages
• Status of the ongoing release
• Preparation of the next release

Q&A

• Questions from community participants, answered by the Flatcar maintainers

Administrative tasks after meeting concluded

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

[chewi]

Carried over since I missed the last meeting:

• Whether we should still support BIOS for new deployments on AWS.
  • Supporting TPM requires making the image UEFI-only.
  • Older instance types don't support UEFI.
  • Should we create two AMIs? This seems possible but messy.
  • See Register AWS AMIs as preferring UEFI over legacy BIOS mantle#582.

[tormath1]

Closed in favor of: #1713