When running the distributed system / store under test on k8s, it's better to use k8s' very own pod-based mechanisms to mess around with "nodes" rather than taking the regular ssh-to-node-or-container based approach.
I took the Docker remote as an example to introduce some very simplistic first k8s remote coming with this PR. I could have isolated this in my own jepsen tests, but thought it might be helpful for other people, and maybe it can grow since k8s is growing, and also all kids of systems get their footprint on it more and more.
When running the distributed system / store under test on k8s, it's better to use k8s' very own pod-based mechanisms to mess around with "nodes" rather than taking the regular ssh-to-node-or-container based approach.
I took the Docker remote as an example to introduce some very simplistic first k8s remote coming with this PR. I could have isolated this in my own jepsen tests, but thought it might be helpful for other people, and maybe it can grow since k8s is growing, and also all kids of systems get their footprint on it more and more.
Hope it's ok. Thanks.