|
@thattommyhall | |||||
|
"What should our kubernetes strategy be?"
"Mate, you need a business strategy first"
|
||||||
|
||||||
|
Eagle Man
@thattommyhall
|
11. pro |
|
"We need to make sure our app is deployed in multiple clouds"
"Do you have an app?"
|
||
|
|
||
|
Eagle Man
@thattommyhall
|
11. pro |
|
"we need to get ready for a million users"
"yeah, well I saw an email asking someone to manually add a user into the database so it seems like you can't sign up one user via the extant API"
(PS, this actually happened)
|
||
|
|
||
|
Noah Cantor
@nrcantor
|
11. pro |
|
More cowbell.
|
||
|
|
||
|
Dr Fabian Seymour
@DrFabianSeymour
|
11. pro |
|
Kubernetes? Did they attack the ship and cause the warp drive to fail? Captain, it'll be weeks before we can recharge the dilithium crystals!
|
||
|
|
||
|
mark
@deligatedgeek
|
11. pro |
|
Normal kubernetes strategy is to spend 6 months making it do work reliably and then monitor like crazy.
You could most likely do what you need on swarm or mesos.
If you really need kubernetes then it's a fantastic product, if you've been managed into it, run.
|
||
|
|
||