# 20210714 Fedora CoreOS Virtual Meeting location: https://bluejeans.com/635151869/7555 ### Agenda #### Roll Call Add your name and involvement/interest in FCOS here: - Dusty Mabe - dusty@dustymabe.com - FCOS/RHCOS team at Red Hat - Jonathan Lebon - CoreOS team at Red Hat - Jason Brooks - Red Hat OSPO - Ben Howard - CoreOS Minion at Red Hat - Jaime Magiera - University of Michigan - Micah Abbott - CoreOS at Red Hat #### Action items from last meeting No meaningful action items from last meeting. #### Flock to Fedora 2021 (5th to 7th August 2021) - CFP closes 9th/16th July - https://github.com/coreos/fedora-coreos-tracker/issues/894 - Notes: - potentially a session from joe doss to talk about forem/FCOS - potentially a session on what's new in FCOS + update on integrating with the rest of Fedora - any takers on specific use cases of FCOS that might interest people? #### policy: setting single node defaults that don't enhance kubernetes - https://github.com/coreos/fedora-coreos-tracker/issues/880 - Notes: - seems to be agreement on moving forward with setting defaults for single node that don't enhance k8s - link for repo that OKD uses to tweak FCOS for OKD: https://github.com/openshift/okd-machine-os #### Migration API for breaking changes - https://github.com/coreos/fedora-coreos-tracker/issues/892 - Notes: - General idea: we don't currently have an API contract between FCOS and whatever is running on top - if people are just using podman then not a big deal, if they are using k8s then it could be a big deal - if we make a breaking change to FCOS we potentially break some k8s distros that integrate on top of FCOS - email communications require humans to make changes and account for potentially breaking changes in k8s distros - if we had some sort of contract/tools/knobs for these changes then it might make things a little easier - This is a way to optimize what we're already doing, but we'd make it easier for people to tweak things - feature flags are a bit more explicit, whereas editions are a bit more opaque - if we use editions we should probably be able to map them to feature flags and have them be able to be individually toggled - jlebon: would like to advocate for auto-migrating nodes when we can (even after a period of time) - darkmuggle: we are engineering for the unknown a bit, this still wouldn't prevent us from breaking people in all cases - darkmuggle: should we tighten the scope of this API guarantee to specifically the kubernetes use case? - jlebon: could we add feature flags and then add editions later if we decide we need them (editions map to features) - dustymabe: alternative would be to create explicit documentation for kubernetes distributors, table feature flags for now and come back to it later - bgilbert: the problem is that automatic updates to the OS is not good for k8s distributors to properly handle - jlebon: running `next`\`testing` streams would help #### New Package Request: oci-seccomp-bpf-hook - https://github.com/coreos/fedora-coreos-tracker/issues/887 -> not enough time today