6 ms·

Right, so in the WordPress example you would have: - a WebApp pod for the WordPress, which can be scheduled/load balanced across several nodes - a MySQL Mast

Right, so in the WordPress example you would have: - a WebApp pod for the WordPress, which can be scheduled/load balanced across several nodes - a MySQL Mast pod, and possibly MySQL Slave pods which would be scheduled/load balanced I REALLY want to get into all this but this seems like SO MUCH MORE WORK than just running them traditionally...

liotier 9y ago
> I REALLY want to get into all this but this seems like SO MUCH MORE WORK than just running them traditionally... It is... Unless you have hundreds of servers - and then it pays off handsomely.
- jalfresi 9y ago
  Absolutely! I can definitely see the payoff there. It just seems that everyone is packaging projects as Docker now and its a bit confusing that orchestration seems to be a bit of an afterthought in the docker world, when I'm sure most applications will require a database. Still, I'll keep on plugging away at kubernetes; I actually quite like the design of the system, very tidy!
teraflop 9y ago
> this seems like SO MUCH MORE WORK than just running them traditionally Here's an analogy: let's say you've written a command line tool and you want to install it. The simple answer is to just copy the binary to /usr/bin. Does it need config files? Library dependencies? That's fine, copy them to the appropriate directories. But then you, as the sysadmin, have the responsibility of remembering exactly what the state of the system is. If you need to make changes later on, you need to spend time figuring out exactly what needs to be updated, and then manually apply those changes without making mistakes. The cleaner solution is to use a package manager like rpm or apt-get. You have to spend some time up front to package your code, including explicitly defining things like package dependencies and clean-up scripts. But once that's done, you can let the package manager do the work of figuring out how to get the system into the desired overall state. You're doing more work in the short term, but it pays dividends in terms of maintainability.
- jalfresi 9y ago
  Another great explanation - so its kinda-like a package manager for complete systems (like my above WordPress example). Neat! Think I'm getting the appeal now
  - raesene9 9y ago
    TBH the package manager for applications thing that was described is just Docker, you don't need Kubernetes for that. Kubernetes makes more sense if you're running big clusters of systems.
nickik 9y ago
Take a look at the Helm Package Manager. Once you have Kubernetes running you can very easily install MySQL (even more complex high availability clusters). If you can put your application in a docker you are almost there. If you don't manage Kubernetes yourself this is actually not that much more work. It is sort of a shift in thinking, and you have to retrain, but once you do that it should actually be faster. I am doing this right now and the paradigm shift is just really big, that's why it seems to take so much longer.

liotier 9y ago

> I REALLY want to get into all this but this seems like SO MUCH MORE WORK than just running them traditionally... It is... Unless you have hundreds of servers - and then it pays off handsomely.

jalfresi 9y ago
Absolutely! I can definitely see the payoff there. It just seems that everyone is packaging projects as Docker now and its a bit confusing that orchestration seems to be a bit of an afterthought in the docker world, when I'm sure most applications will require a database. Still, I'll keep on plugging away at kubernetes; I actually quite like the design of the system, very tidy!

teraflop 9y ago

> this seems like SO MUCH MORE WORK than just running them traditionally Here's an analogy: let's say you've written a command line tool and you want to install it. The simple answer is to just copy the binary to /usr/bin. Does it need config files? Library dependencies? That's fine, copy them to the appropriate directories. But then you, as the sysadmin, have the responsibility of remembering exactly what the state of the system is. If you need to make changes later on, you need to spend time figuring out exactly what needs to be updated, and then manually apply those changes without making mistakes. The cleaner solution is to use a package manager like rpm or apt-get. You have to spend some time up front to package your code, including explicitly defining things like package dependencies and clean-up scripts. But once that's done, you can let the package manager do the work of figuring out how to get the system into the desired overall state. You're doing more work in the short term, but it pays dividends in terms of maintainability.

jalfresi 9y ago
Another great explanation - so its kinda-like a package manager for complete systems (like my above WordPress example). Neat! Think I'm getting the appeal now
- raesene9 9y ago
  TBH the package manager for applications thing that was described is just Docker, you don't need Kubernetes for that. Kubernetes makes more sense if you're running big clusters of systems.

nickik 9y ago

Take a look at the Helm Package Manager. Once you have Kubernetes running you can very easily install MySQL (even more complex high availability clusters). If you can put your application in a docker you are almost there. If you don't manage Kubernetes yourself this is actually not that much more work. It is sort of a shift in thinking, and you have to retrain, but once you do that it should actually be faster. I am doing this right now and the paradigm shift is just really big, that's why it seems to take so much longer.