Used to do DevOps before they even called it that way: Linux. Python. Perl. Java. Docker. For fun and profit. CTO level generalist working for a mid-sized tech-centric company.
Dresden, Germany
Well. Yes. Question's valid, and your answer is obvious and true: Know what you are using. And know why you are using it. I've seen several projects the last couple of years which tried best to work "using docker and kubernetes" because everyone does it so it can't be all too wrong, can it? Personal experience, throughout the last two decades of IT in various environments: Your actual enemy is not lack of tools. Your enemy is complexity that gets into your way on many different levels. Adding more tools immediately will add more complexity to wrestle with. You should only do that if these tools clearly solve an actual problem in your environment that can't be solved by easier means. So get your requirements right, evaluate solutions - and then do what needs to be done. Maybe kubernetes and docker are good for your environment. But it's only you and your team who can figure that out. ;)
@kr428
Thanks and that's a very realistic answer!
It's very important what you need and what you really want to do. These days people are like "Kubernetes is the best" enthusiastically kinda too much to me. I really would like to step back a bit and think if this is a really good answer. Knowing pros and cons, especially cons, and comparing other possibility take more time and boring but you cannot avoid it.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Well. Yes. Question's valid, and your answer is obvious and true: Know what you are using. And know why you are using it. I've seen several projects the last couple of years which tried best to work "using docker and kubernetes" because everyone does it so it can't be all too wrong, can it? Personal experience, throughout the last two decades of IT in various environments: Your actual enemy is not lack of tools. Your enemy is complexity that gets into your way on many different levels. Adding more tools immediately will add more complexity to wrestle with. You should only do that if these tools clearly solve an actual problem in your environment that can't be solved by easier means. So get your requirements right, evaluate solutions - and then do what needs to be done. Maybe kubernetes and docker are good for your environment. But it's only you and your team who can figure that out. ;)
@kr428
Thanks and that's a very realistic answer!
It's very important what you need and what you really want to do. These days people are like "Kubernetes is the best" enthusiastically kinda too much to me. I really would like to step back a bit and think if this is a really good answer. Knowing pros and cons, especially cons, and comparing other possibility take more time and boring but you cannot avoid it.