5 ms·
Testcontainers aren't even compatible with kubernetes, that's a tool from the past.
by mrAssHat 3y ago
Testcontainers aren't even compatible with kubernetes, that's a tool from the past.
- dboreham 3y agoROAC "runs on any computer", which k8s does not.
- the_jeremy 3y agoWe use [kubedock](https://github.com/joyrex2001/kubedock https://github.com/joyrex2001/kubedock) to run testcontainers in kubernetes clusters. As long as you're only pulling the images, not building or loading them (explicitly not supported by kubedock), it works pretty well.
- marginalia_nu 3y agoWhy'd you run them in kubernetes? Seems like extreme overkill for launching a short lived container for an integration test. What could kubernetes possibly add to that?
- mrAssHat 3y agoBecause we are a big company and would like to utilize resources better. We also want homogeneity in tech when possible (we already heavily use kubernetes, we don't want to keep docker hosts anymore). Teams of testers need to be accounted in terms of resource quotas and RBAC. What exactly do you see as an overkill in wanting to run short-lived containers in kubernetes rather than in docker (if we already have kubernetes and "cook" it ourselves)?
- politelemon 3y agoThat reasoning seems more like one from policy/cargo cult rather than reasoning specific to your org. For something short lived and meant to be isolated I wouldn't want to subject them to even more infrastructural dependencies outside their control.
- mrAssHat 3y agoBetter resources utilization definitely sounds like cargo cult, riiight.
- marginalia_nu 3y agoIt's overkill because these containers typically have a lifetime counted in single digit seconds, and it takes kubernetes not only more time but also more compute resources to decide where to allocate the pod than to actually just run the thing.