Nixifying Kubernetes with nix-csi, easykubenix and dinix

Implemented support in nix-csi to set volumeAttribute $system (x86_64-linux usually) to a storepath, then nix-csi won’t do any building and just fetch that path from configured caches.

Implemented support in easykubenix to push the generated manifest to binary cache. If you set

volumeAttributes.${pkgs.system} = pkgs.hello;

the manifest depends on pkgs.hello which will be pushed to the cache as well, meaning it’ll be available for fetching by nix-csi :smile:

@claes Now I have a good example for how you’d develop your local application in a remote Kubernetes cluster swiftly and easily!