Zac
Zac
Without going through the process of downloading/installing, etc - is this project still working / alive? Any issues if I fork?
**Issue number:** Related to #2204 **Description of changes:** This refactor is in preparation for the upcoming additions related to static addressing. Almost no code was changed minus the few clippy...
As time goes on and we continue to add kernel modules to support new and different hardware, we don't want our non-metal variants to carry all of the extra modules....
Currently the only way to configure a network device in `net.toml` is by device name: ``` [eno1] ... ``` It would be nice to be able to use MAC address...
For our metal variants, we should greatly expand our hardware compatibility. Ideally, we would support all main classes of server hardware.
Metal images require a few extra files (`net.toml`, `user-data.toml`, and `bootconfig.data`) to be provisioned to boot and properly function. I'd like the ability to build an image which includes these...
- Depends on #2214 **What I'd like:** I would like the ability to set up a static IP for a network interface. This means we will need to be able...
As we require additional network config options, we'll need to bump the version in `net.toml`. The code needs to support deserialization of different versioned files.
We currently package the `bootconfig` CLI from the current version of the 5.10 kernel. Though `bootconfig` doesn't receive a ton of updates, it does pull in some header files from...
Bottlerocket carries [a patch to `cri`](https://github.com/bottlerocket-os/bottlerocket/pull/1180) that sets a default `RLIMIT_NOFILE`, introduced to help remediate [this OOM issue](https://github.com/bottlerocket-os/bottlerocket/issues/1136). This configurable limit seems more generally useful, so we should upstream the...