Agenda for the Flatcar Developer Sync on Wednesday, 23rd of July 2025, 2:30pm UTC

[t-lo]

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: https://www.youtube.com/live/T-VKvgMog-A
  • 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 Stable release 4230.2.0 (published June 25, 2025)

• With our adoption of systemd-256, support for legacy CGroupsV1 ended with Stable release 4230.2.0.
• Enabling legacy CGroupsV1 during deployment is not 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 (release series 4081.3.x) will continue to support CGroupsV1 throughout its lifetime. It is expected to be EOL'd in early 2026. Please use this time to upgrade your workloads to support CGroupsV2.

Monthly Contributions and Advisory status Review

1. Discuss the latest Monthly Contributions Report
   • Also see https://insights.lfx.linuxfoundation.org/foundation/cncf/overview/github?project=flatcar&repository=&routedFrom=Github
   • First-Time Contributors in the last month:
     • kimsondrup: fix documentation on Kubernetes
     • arcln: initial proxmox documentation
     • hokutolabs: documentation (workaround on ISO + Ignition)
     • krook: CNCF footer on the website
     • arilou: enable ftrace syscalls on arm64
     • ananthb: sysext-bakery nomad
     • AncutaIoan: ue-rs github actions improvement
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

1. Roadmap review: Flatcar tactical, release planning, and roadmap (view) (@t-lo, @miao0miao )
2. Projects status review:
   a. Composable OS: sysext and ClusterAPI (@t-lo) - Flatcar tactical, release planning, and roadmap (view)
   b. SecureBoot / Trusted Boot (@sayanchowdhury ) - Flatcar tactical, release planning, and roadmap (view)
   c. CNCF Incubation process (@John15321 ) - Flatcar tactical, release planning, and roadmap (view):
   d. Flatcar infrastructure status (@tormath1) - Flatcar tactical, release planning, and roadmap (view)
   e. Nebraska status (@ErvinRacz) - Flatcar tactical, release planning, and roadmap (view)
   Nebraska OIDC Refactor with breaking change
3. Maintainer team tactical / implementation (aka "line work") status review (@sayanchowdhury): Flatcar tactical, release planning, and roadmap (view)

Open Mic: Work to assign / User issues and PRs to discuss?

• Brief Maintenance Mode Planning

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]

@ader1990 @jepio I'll talk through my new "tiny initrd" plan to address the space in /boot and try to answer any questions you may have. Bear in mind that I haven't had sufficient time to work out all the details yet.

[John15321]

CNCF Section

🎯 CNCF Onboarding Progress

CNCF Onboarding update - tracking in flatcar/Flatcar#1800

✅ Completed checkpoints:

• DCO (Developer Certificate of Origin) - All commits now require sign-off across the organization (#1807 - ✅ closed)
• CNCF Slack integration - Thank you all for joining the CNCF Slack workspace!
• Website footer compliance - LF footer has been added per guidelines (#1806 - ✅ closed)

🔄 Remaining items:

• Domain transfer to CNCF (in progress)

📋 Maintainer Onboarding Initiative

Create a maintainers onboarding checklist to help new maintainers get started with the Flatcar project. We're actively collecting input from existing maintainers to define essential onboarding topics and resources.

🎓 CNCF Incubation → Graduation Progress

OpenSSF Best Practices Badge Status - tracking in #1819 | Badge Progress

🎉 Excellent progress: Currently at 97% completion - huge thanks to Thilo for driving the OpenSSF requirements review! (#1819)

📝 2 remaining items for 100% completion:

1. Test Policy Requirement

   • Need formal/informal policy stating that major new functionality should include tests in the automated test suite
   • Policy can be established even by word of mouth

2. Test Policy Evidence

   • Need evidence showing the test policy has been followed in recent major changes
   • Should be visible in release notes - perfection not required, just evidence of typical practice

Overall graduation tracking: flatcar/Flatcar#1818

---

🔧 Repository Standardization Initiative

Standardize Pull Request, Merging workflow and branch protection rules

We will now be starting to encourage maintainers of repositories with individuals mentioned as core maintainers (such as scripts) to begin implementing the standardized branching and PR rules. This effort includes:

• Default branch standardization (main preferred)
• Squash-only merging policy
• Unified branch protection rules
• Consistent PR workflow across all repos

Documentation update effort: #1816 - updating contributing documentation and templates across all repositories to reflect the new standardized workflow.

List of where those standards have been implemented as of now: #1714 (comment)

🔍 CODEOWNERS Implementation

Implement CODEOWNERS file for standardized PR review workflow

We'd like to resurrect the conversation about CODEOWNERS files. Under our current lazy consensus approach, this would work as follows:

For most repositories (with flatcar-maintainers as maintainers):

• CODEOWNERS file would contain just the flatcar-maintainers group
• Every PR automatically assigned for review to all flatcar-maintainers
• This works well for repos that rarely receive contributions

For high-activity repositories (like scripts with more contributors):

• Individual GitHub Teams would be created (e.g., flatcar-scripts)
• These teams serve as focused tags that maintainers can join (arbitrarily many)
• CODEOWNERS would reference these specific teams
• Reduces noise and allows people to focus attention where needed
• Ensures we allocate attention to every PR across the org as best as possible

The exact number of teams and initial membership is open for discussion. Please visit #1791 to share your ideas and feedback on this approach!

[travier]

I can do a small introduction about a new project to manage systexts:

• https://github.com/travier/sysexts-manager
• https://asciinema.org/a/726958