Have had many hats on in my life: Developer, Team Lead, Scrum Master, Architect and Product Owner. Now back to developer \o/ Interested in product discovery, quality assurance and language design.
Hey Kelsey, good read. I just started with kubernetes and was just reaching the point where I asked myself how I can get a fluent dev workflow with it. It seems to be that, without significant effort, the workflow is "Push to production to run your code changes", which is, well, not optimal :-) I'll check out your links!
I'm a fan of Open Source and have a growing interest in serverless and edge computing. I'm not a big fan of spiders, but they're doing good work eating bugs. I also stream on Twitch.
We're starting to work with minikube for local k8s. This might be what you're looking for. I get to document it as it's new to our dev workflow, so maybe I'll do a blog post about it in the near future.
Have had many hats on in my life: Developer, Team Lead, Scrum Master, Architect and Product Owner. Now back to developer \o/ Interested in product discovery, quality assurance and language design.
Even with minikube, you have steps to push your local changes into the kube that take long and are hard to maintain. Think of the steps you have to take between saving you code in the editor until you see it live in your browser.
Minikube works except at some point you might end up where you have too many services to run locally (think if you need a database, and ElasticSearch, and few Java-based services). Your laptop will melt down.
Also you still need ways to deploy multiple services with a single command into minikube, etc.
I'm a fan of Open Source and have a growing interest in serverless and edge computing. I'm not a big fan of spiders, but they're doing good work eating bugs. I also stream on Twitch.
Hey Kelsey, good read. I just started with kubernetes and was just reaching the point where I asked myself how I can get a fluent dev workflow with it. It seems to be that, without significant effort, the workflow is "Push to production to run your code changes", which is, well, not optimal :-) I'll check out your links!
We're starting to work with minikube for local k8s. This might be what you're looking for. I get to document it as it's new to our dev workflow, so maybe I'll do a blog post about it in the near future.
Even with minikube, you have steps to push your local changes into the kube that take long and are hard to maintain. Think of the steps you have to take between saving you code in the editor until you see it live in your browser.
Minikube works except at some point you might end up where you have too many services to run locally (think if you need a database, and ElasticSearch, and few Java-based services). Your laptop will melt down.
Also you still need ways to deploy multiple services with a single command into minikube, etc.
I'm new to k8s, so thanks for that feedback Richard. Much appreciated.