4 ms·
In general, if you can move any kind of logic to a lower level, that's better. For example, testing that kubernetes restarts work correctly is tricky and requi
by valenterry 1y ago
In general, if you can move any kind of logic to a lower level, that's better.
For example, testing that kubernetes restarts work correctly is tricky and requires a complicated setup. Testing that an erlang process/actor behaves as expected is basically a unit test.
- emoII 1y agoI bet the kubernetes project has test for that, why should I as an application developer care about testing something other than my own code?
- valenterry 1y agoOh of course, I'm sure the kubernetes project tests that they trigger restarts correctly etc. But that doesn't cover the behavior of your app, the specific configuration you ask kubernetes to use and how the app uses its health endpoints etc. - this is all purely about your own code/config, the kubernetes team can't test that.
- bccdee 1y agoThat's assuming your code is well-configured. How do you test your k8s configs?