-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Configuration driven from cloud-init style yaml files #4
Comments
Closed
mudler
added a commit
that referenced
this issue
Jan 29, 2021
mudler
added a commit
that referenced
this issue
Jan 29, 2021
mudler
added a commit
that referenced
this issue
Feb 4, 2021
Also drop finalizer from cos-config, not required anymore See #4
Closing this as we have a cloud-config mechanism, for the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
/etc
should be configured on boot driven by extensiblecloud-init
style yaml files.Similarly, users can drop config files into the
/oem
( or /usr/local/oem ) or/usr/local/setup
folder to achieve persistent configurations. The cloud-init format should allow extensions too.A default config should be among the lines of : https://github.com/rancher/k3os/blob/1688b718da51b39d48c17e2a20d453f37f3d58c7/overlay/libexec/k3os/boot
This issue is about finding a tool that accomplishes that, and embed it into the various stages of the OS (at least): initramfs, boot, network. Replacing also the current
skel
package that does handle/etc
setup.Ideally, the tool that mimic cloud-init shouldn't have dependency, and be portable (possibly written in Go) see for e.g.:
See also https://github.com/mocaccinoOS/os-commons/tree/master/packages/systemd/yip-systemd for a possible integration with systemd boot
The text was updated successfully, but these errors were encountered: