<njha>
travier: hi! you added ocf/strand into https://github.com/coreos/fedora-coreos-docs/issues/305 a while ago, but we ended up giving up on CoreOS and so are probably abandoning this early, so you might want to remove it now
<njha>
sorry about that :(
<njha>
the repository will stay archived in case (for whatever reason) this is useful to someone
c4rt0 has joined #fedora-coreos
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 268 seconds]
<travier[m]>
njha: Thanks, updated. Sorry Fedora CoreOS was not a good fit. Could you share some details about what you were missing? That would be interesting for us
c4rt0 has quit [Remote host closed the connection]
c4rt0_ has quit [Remote host closed the connection]
fifofonix has quit [Ping timeout: 268 seconds]
<njha>
mostly just papercuts-- I guess broadly the issue is that butane / ignition isn't robust enough to do a lot of things we needed to do (layer RPMs, etc) and rpm-ostree doesn't support a lot of things we need (teleport's rpm package writes to /usr/local, gpgcheck=1 doesn't work, there's no good way to set selinux rules)
<njha>
I guess how most people are using CoreOS is to bring up some base system and then have automation via ansible or some other config management tool that actually sets up Kubernetes
<njha>
which is fair, but at this point I'm writing all the things to automatically update safely (lock backend), and all the things to install kubernetes, and most of the config management i was doing was writing systemd services
<njha>
and I don't want to do all this just to have Kubernetes, so now I'm on a normal OS 😅
<njha>
fully aware that we're not the target audience for CoreOS so this isn't a complaint or anything