blaggacao
make tests accessible from host
When running tests manually, nixos gives us a machinery that's great for managing vms, but really terrible for inspecting the kuberentes cluster.
We need to expose the k8s api and extract the tls certs out into the host machine so that we can use tools like k9s or plain kubectl to debug the cluster.
If we provide e2e tests for users repo, the same requirement applies.
just to clarify, is the goal to create tests out of kubernetes hosts? Or access the testing framework from within modules?
The nixos test framework spans up those VMs. Though, I have a flaky kubernetes test and in order to debug, I need to directly be able to interact with the kubernetes cluster, without first going into the VM.
This is important because without access to my local (devshell) tools and the right ergonomy, debugging a k8s cluster is a nightmare.
https://github.com/blaggacao/kubenix/commit/9759a318f534681daeae7d14338ca89c8615a0f8 introduces this feature for the kubernetes test implementation. However the k3s test implementation is not compatible: int inlines the certificates into the kubeconfig file and also is exposed on another port 6443.