It would be nice if the pool spec supported a knob that controlled the various bootc transient options: https://github.com/bootc-dev/bootc/blob/946874cfacef88e596b3e6233feaf4df698d5dd4/docs/src/man/bootc-setup-root-conf.5.md?plain=1#L26. We should also support special-casing some paths to persist (e.g. /var/lib/containers). And perhaps even expose the read-only /etc mode.
This allows us to pass on that stronger zero/low drift story from bootc to bootc-operator users in an easy way, and can be especially appealing to users used to $cloud's flavour of managed K8s (e.g. EKS/AKS/GKE) where the default path is often just nuke and reprovision to "update" a pool rather than in-place (which is the nuclear "no drift" option).
Needs design work.
It would be nice if the pool spec supported a knob that controlled the various bootc transient options: https://github.com/bootc-dev/bootc/blob/946874cfacef88e596b3e6233feaf4df698d5dd4/docs/src/man/bootc-setup-root-conf.5.md?plain=1#L26. We should also support special-casing some paths to persist (e.g.
/var/lib/containers). And perhaps even expose the read-only/etcmode.This allows us to pass on that stronger zero/low drift story from bootc to bootc-operator users in an easy way, and can be especially appealing to users used to $cloud's flavour of managed K8s (e.g. EKS/AKS/GKE) where the default path is often just nuke and reprovision to "update" a pool rather than in-place (which is the nuclear "no drift" option).
Needs design work.