3 ms·
Another case: People who want to run workloads that are inherently incompatible with Kubernetes networking model. For example: * For some cursed reasons you w
by rfoo 5mo ago
Another case: People who want to run workloads that are inherently incompatible with Kubernetes networking model.
For example:
* For some cursed reasons you want to make sure every single one instance of a large batch job see just one NIC in its container and they are all the same IP and you NAT to the outside world. Ingress? What ingress? This is a batch job!
* Like the previous point, except that your "batch job" somehow has multiple containers in one instance now, and they should be able to reach each other by domain.
- PunchyHamster 5mo agoYou can configure k8s so pod to pod networking works just fine so I'm not even sure what complaint here is
- zbentley 5mo agoThat is indeed a weirdly cursed requirement. Why? Black box of legacy stuff? A system that was never designed to be run in multiple does so if all the nodes think they’re the same machine? Defeating a license restriction?
- rfoo 5mo agoEasier checkpoint & restore.