3 ms·
I see the benefit of ECS/Kubernetes for managing many services. Say I already use ECS or Kubernetes for orchestration of some of my services. If I'm working on
by webo 11y ago
I see the benefit of ECS/Kubernetes for managing many services.
Say I already use ECS or Kubernetes for orchestration of some of my services. If I'm working on a new Rails/Node/Python app that doesn't talk to the rest of my services, would it make sense to stick the app into my existing cluster? If not, what would be an easy way to launch, deploy, and manage (non-PaaS) these kind of stand-alone services?
- eknkc 11y agoYou can create one node kubernetes clusters on micro instances, if you need it just for the tooling or environment consistency. Not sure if it's better to use larger clusters for unrelated stuff or this though.
- cpitman 11y agoI would deploy all of your applications to the same Kubernetes instance. If you need to worry about isolating specific applications on different hosts, that can be accomplished by labeling those hosts and setting up affinity rules. In other words, hosts can be split into different zones and pods deployed for specific zones, but still have one larger Kubernetes instance.
- boulos 11y agoIt's not a problem / wrong to put unrelated things in a single cluster (and just because they're not talking today, also doesn't mean they won't in the future). But if you really want hard separation between them, you could easily have separate clusters. It's a lot like a directory with files, if you put everything in one directory things like the output of ls have some noise in them, but if you're used to searching (service discovery) then it doesn't matter too much. Disclaimer: I work on Compute Engine (and I've always just used a single cluster)