You Don't Need to Rebuild Your Development Docker Image on Every Code Change

Re:You Don't Need to Rebuild Your Development Docker Image o... by orlovs on Monday May 31, 2021 @12:46PM (#27345906)

I have never understood kubernetes development in local development workflow unless kubernetes functionality being developed or some yaml magic. It’s super overhead IMHO. If needed to test api’s as unit test you can always port-forward traffic of desired enpoint or use something like telepresence. Less kubernetes is always better

[ Parent | on HN ]

Re:You Don't Need to Rebuild Your Development Docker Image o... by erulabs on Monday May 31, 2021 @01:09PM (#27346131)

It’s cpu/memory overhead yes, but between matching prod and dev, extremely simple config (redis is always located at “redis:6379”), zero setup instructions (skaffold dev), remote/local hybrid development, and fostering prod-ready skills for developers (still working on that devops koolaid), I find it -extremely- worthwhile. I’ve yet to meet someone who doesn’t hate it to start (because kubernetes) and winds up loving it and swearing by it.

It’s essentially a vastly superior “vagrant up” on anabolic steroids

[ Parent | on HN ]

Re:You Don't Need to Rebuild Your Development Docker Image o... by orlovs on Monday May 31, 2021 @01:32PM (#27346369)

I agree, for e2e/integration testing, excellent

[ Parent | on HN ]