2 ms·
Sorry, what problem does this solve? Things are not as easy on other cloud providers where a host cannot get an entire subnet to itself. Rudder aims to solve t
by contingencies 12y ago
Sorry, what problem does this solve?
Things are not as easy on other cloud providers where a host cannot get an entire subnet to itself. Rudder aims to solve this problem by creating an overlay mesh network that provisions a subnet to each server. ... is unclear.
What host for virtualized infrastructure needs an entire, fake, non-internet-routable subnet that it cannot provision itself?
I believe there's a broken one size fits all network architectural assumption or provisioning methodology at the root of all this.
(Edit as reply to child as rate-limited: Sounds like I was right, and it's docker's fault. How is this not better solved with the standard approach of applying network namespaces and/or unique interfaces to containers?)
- wmf 12y agoIt solves port conflicts caused by running multiple copies of the same service on the same host. Kubernetes likes to have a few sidecar containers hanging off each service instance (e.g. memcached might have an sshd sidecar that wants to be on port 22 and nginx might want to have its own sshd sidecar also on port 22), and if your host only has one IP address then Docker has to do dynamic port mapping and your service discovery system has to track port numbers and such.
- jbeda 12y agosshd is kind of a poor example. Kubernetes has an idea of a pod -- a group of containers that share an netns and have an IP. Reasons you might want a pod: * A thick client or client side proxy that follows the ambassador pattern for service discovery and access. * A data-loader and data-server pair. The loader would grab data from some persistent source and write it to disk or a shared memory segment. The data-server would then use that data and serve it up. You'd could run the data-loader at a lower QoS so it doesn't stall the data-server. * Some sort of server and a log saver. The log saver could periodically batch up and compress structured log data and upload it to a persistent store (such as BigQuery in GCP). You want to build/configure/restart/upgrade the log saver separately from the server. You'd also run the log saver at a lower QoS. Inside of Google we have all sorts of examples where we have sets of containers/tasks/processes that are co-scheduled onto a machine and work together.