Comment # 4 on bug 1233410 from Matthias Gerstner

I suggest you do it in whatever way is best for you and the outcome of the
packaging. Doing it in a shared sysctl-common package also sounds good.

Are such high container loads common use cases? Maybe activating these
settings should be left to the users that actually need them?

You are right, when the settings are moved out of the sysctl.d directories,
then they won't popup in rpmlint anymore. But we do have some monitoring e.g.
of newly introduced systemd services and changes to them. It's a best effort
approach.