3 ms·

Thx for writing that. To me it seems mind-boggling that in the 21st century you still have to point out to people that you shouldn't just adopt a technology bec

Thx for writing that. To me it seems mind-boggling that in the 21st century you still have to point out to people that you shouldn't just adopt a technology because it seems cool. Of course you should ask yourself what problem you're trying to solve. Apparently people still don't get this. I'm not sure I agree about templating YAML files–why is templating JSON any better, really?–but YMMV.

hpoe 6y ago
I agree that technology shouldn't be adopted just because it is new unfortunately the job market makes it so many early engineers (and already established engineers that will want to move at some point) end up practicing RDD as a matter of self interest.
rektide 6y ago
there's basically no other options for running your own cloud & there's no particular major weak points for Kubernetes that other containerizing automation engines don't also have. people think they're being smart by telling you to check whether such and such fits your needs. usually it's not bad advice. but the deck is pretty stacked here. nothing else has shown itself to be as flexible, as extensible, as consistent. well demonstrated but it's capability at handling many different add-ons (controllers, operators). rarely is cloud architecture do readily deployable to other non-core concerns, especially via the core tools & constructs. if you want to go march off in to tech that does less, that will only do a little bit, that less people will be familiar with, that has less community, sure. spend a couple hours justifying to yourself why you are not going to use the really amazing all encompassing tech that's quickly supplanted everything else. pick some other combination of technologies which you will assemble, make your own stack, yeah, you're an independent thinker, you don't need convention or all this extra stuff! it's just gonna slow you down. go for it. Kubernetes is not easy. but I find arguing against it to be difficult. there have been tools upon tools upon tools for so long. but little out there has brought the different concerns together, found overarching paradigms to create a basic, trusted quality of life that Kubernetes has clarified. again, it's not easy, but learning it ought to keep paying forward again & again, as you pick up new interests, want new services. even if those are Amazon services, ACK now will let you build Kubernetes deployment units that include those AWS services. the paradigm works.

hpoe 6y ago

I agree that technology shouldn't be adopted just because it is new unfortunately the job market makes it so many early engineers (and already established engineers that will want to move at some point) end up practicing RDD as a matter of self interest.

rektide 6y ago

there's basically no other options for running your own cloud & there's no particular major weak points for Kubernetes that other containerizing automation engines don't also have. people think they're being smart by telling you to check whether such and such fits your needs. usually it's not bad advice. but the deck is pretty stacked here. nothing else has shown itself to be as flexible, as extensible, as consistent. well demonstrated but it's capability at handling many different add-ons (controllers, operators). rarely is cloud architecture do readily deployable to other non-core concerns, especially via the core tools & constructs. if you want to go march off in to tech that does less, that will only do a little bit, that less people will be familiar with, that has less community, sure. spend a couple hours justifying to yourself why you are not going to use the really amazing all encompassing tech that's quickly supplanted everything else. pick some other combination of technologies which you will assemble, make your own stack, yeah, you're an independent thinker, you don't need convention or all this extra stuff! it's just gonna slow you down. go for it. Kubernetes is not easy. but I find arguing against it to be difficult. there have been tools upon tools upon tools for so long. but little out there has brought the different concerns together, found overarching paradigms to create a basic, trusted quality of life that Kubernetes has clarified. again, it's not easy, but learning it ought to keep paying forward again & again, as you pick up new interests, want new services. even if those are Amazon services, ACK now will let you build Kubernetes deployment units that include those AWS services. the paradigm works.