Erikson Tung

Thanks for the issue. We'll take a closer look at this.

> I don't think a migration is needed as the setting is persisted and restored by prairiedog in the bootconfig initrd. Older versions of prairiedog will just ignore the setting....

Tested check-repo-expirations: ``` $ cargo make -e BUILDSYS_VARIANT=aws-k8s-1.23 -e BUILDSYS_ARCH=x86_64 check-repo-expirations [cargo-make] INFO - cargo make 0.35.15 [cargo-make] INFO - Build File: Makefile.toml [cargo-make] INFO - Task: check-repo-expirations [cargo-make] INFO...

Thanks for bringing this up! > The thing that seems suspicious to me is the AVC avc error, but I am a little out of my depth on that one....

Hi @diranged, I just checked our 5.10 kernel config and it does seem like we have most of the IPVS modules enabled (including `ip_vs_sh`): ``` # IPVS transport protocol load...

Hi @backjo , thanks for creating the issue. We'll look into supporting this as a Bottlerocket setting.

This sounds like a good idea. I agree the current behavior with `settings.boot` is not ideal where the user has to manually reboot the host to apply boot settings specified...

With #868, majority of the metrics have regained metadata information. However a lot of filesystem and io related metrics are still missing metadata. (e.g. `container_fs_limit_bytes`, `container_fs_io_time_seconds_total`)

Hi @rubroboletus , thanks for opening this issue. We'll take a look into supporting that.

Hi @cwwarren, it would seem that currently the [NFS CSI driver](https://github.com/kubernetes-csi/csi-driver-nfs) is in alpha and does not yet support pod inline volumes like the one you're trying to do here....