Bruce this sounds reasonable from a packaging standpoint and also presents an interesting challenge - and one that seems to be broader than just yocto projects. It is a challenge we are seeing for edge deployments of k8s everywhere. Embedded systems are traditionally shipped with longer update/upgrade lifecycles than cloud native software. A typical embedded lifecycle seems to be anywhere from 2-5 years minimum. Kubernetes on the other hand ships new releases about 3x / year.
As we move toward projects that include cloud native technology at the edge, I think we will need to resolve for a more rapid software lifecycle. One solution I know of when using k3s is the system-upgrade-controller. This can upgrade the k3s binary according to a configured plan. It is also possible to use the same controller to update any arbitrary binary in the system - assuming, of course that these are not residing on the immutable part of the file system. Also, the system-upgrade-controller works with any kubernetes not just k3s.
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#6770): https://lists.yoctoproject.org/g/meta-virtualization/message/6770 Mute This Topic: https://lists.yoctoproject.org/mt/85503951/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/meta-virtualization/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
