Daniel Iziourov

I'm reading the comments and I'm a bit confused what you want to achieve. `00-k0s-privileged` and `99-k0s-restricted` [Pod Security Standards](https://kubernetes.io/docs/concepts/security/pod-security-standards/) should be ok. I'd avoid replicating more granular admission controller...

Referencing @mrk-its [comment](https://github.com/delta-io/delta-rs/issues/97#issuecomment-1173174328) from #97 so it's not lost. > @rtyler @fvaleye It looks like there are still two serious issues with vacuum implementation: > > * vacuum lists all...

/kind documentation

What I got so far is: - for falco w/ eBPF to start it'll require: - CAP_SYS_RESOURCE - CAP_SYS_ADMIN - mounting `debugfs` in the host: `mount -t debugfs nodev /sys/kernel/debug`...

It would be great if you could narrow the capabilities instead going for `--privileged`. Not many people will use kernels `>= 5.8` any time soon.

@jpmcb took me some time but I've added tests for `UseLine`.

@marckhouzam I see that you were active recently. Could you take a look at this PR? I addressed the previous comment about adding tests. I had to reshuffle `Command` struct...

Here's what Pants is trying to do https://github.com/pantsbuild/pants/issues/7369

So what's the direction? Do you look for contributions?

Check out [turbo-cache](https://github.com/allada/turbo-cache). Maybe some parts could be reused