3 ms·

People with Kube experience, at what point should someone on Heroku consider switching to Kube with something like GKE? I have a rough idea of the pros and cons

People with Kube experience, at what point should someone on Heroku consider switching to Kube with something like GKE? I have a rough idea of the pros and cons, particularly cost vs. time overhead, but curious about more subtle things.

marenkay 8y ago
I'm migrating "legacy" applications (as in non-containerized ones) to container environments for medium to large companies, and I would suggest two things: - get a local test setup with minikube (https://github.com/kubernetes/minikube https://github.com/kubernetes/minikube) and Helm (https://www.helm.sh/ https://www.helm.sh/) and try out a few applications - convert a project of yours to a Kubernetes deployment, then a Helm chart If both steps are successful and you still feel like Kubernetes is doing a better job for you then Heroku, get a Kubernetes professional. I promise you, there will be as many problems as with any other environment. The only difference is that the Kubernetes issues are not documented.
- te_chris 8y ago
  "The only difference is that the Kubernetes issues are not documented." Move that one to the icebox then!
base698 8y ago
I run a platform that is running applications multicloud, one of which is Heroku. Our devs that use heroku absolutely hate k8s. They feel it's way more complicated and cumbersome and say they don't want to write thousand line YAML files and YAML engineering isn't their job. Also, the pipelines Heroku provides and new CD is far superior. They don't want to reinvent Heroku. Personally after I got k8s I felt about it how I felt about git. I think it's game changing and everyone should learn something about it. Can understand the frustration though.
sciurus 8y ago
If you want to migrate in order to use some of the many services offered by Google Cloud, migrating from Heroku to App Engine is likely an easier path.
pas 8y ago
Istio and Knative (and so on) are the PaaS-on-k8s projects you should watch and try. k8s by itself is not targeting that workflow.

marenkay 8y ago

I'm migrating "legacy" applications (as in non-containerized ones) to container environments for medium to large companies, and I would suggest two things: - get a local test setup with minikube (https://github.com/kubernetes/minikube https://github.com/kubernetes/minikube) and Helm (https://www.helm.sh/ https://www.helm.sh/) and try out a few applications - convert a project of yours to a Kubernetes deployment, then a Helm chart If both steps are successful and you still feel like Kubernetes is doing a better job for you then Heroku, get a Kubernetes professional. I promise you, there will be as many problems as with any other environment. The only difference is that the Kubernetes issues are not documented.

te_chris 8y ago
"The only difference is that the Kubernetes issues are not documented." Move that one to the icebox then!

base698 8y ago

I run a platform that is running applications multicloud, one of which is Heroku. Our devs that use heroku absolutely hate k8s. They feel it's way more complicated and cumbersome and say they don't want to write thousand line YAML files and YAML engineering isn't their job. Also, the pipelines Heroku provides and new CD is far superior. They don't want to reinvent Heroku. Personally after I got k8s I felt about it how I felt about git. I think it's game changing and everyone should learn something about it. Can understand the frustration though.

sciurus 8y ago

If you want to migrate in order to use some of the many services offered by Google Cloud, migrating from Heroku to App Engine is likely an easier path.

pas 8y ago

Istio and Knative (and so on) are the PaaS-on-k8s projects you should watch and try. k8s by itself is not targeting that workflow.