Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Migrating from Heroku to EKS

blog.hellolanding.tech

Post reply on HN
Print view View original

21–29 of 29 posts

Re: Migrating from Heroku to EKS

#21

Post by blymd »

sunguroku wrote: post #9
mrj wrote: post #2

Porter looks cool and I would love to not hand roll kubernetes stuff. But the pricing looks curious. Their "default infrastructure" is $300 a month set up in AWS plus usage costs on Porter. It's already 6x what I'm spending on Heroku, why would I pay usage costs per CPU to Porter if they're not running any CPUs? Honest question really because I'm interested, it just seems far out of line price-wise. I would totally p…

Co-founder here. Thanks for asking this - we get this question a lot and have tried our best to address it in the FAQ section of our pricing page ( https://porter.run/pricing ). Infrastructure provisioned by Porter is constantly managed by Porter so that the end user does not have to worry about the details of maintaining a Kubernetes cluster. In this regard, our pricing structure is identical to traditional platform…

Not sure about Heroku, Render, and Vercel, but Fly.io doesn't resell AWS/GCP.

Re: Migrating from Heroku to EKS

#22

Post by tristanMatthias »

whakim wrote: post #16
DancerOfFaran wrote: post #5

So they went from Heroku buildpack-based ops, to Kubernetes on EKS, through a 3rd party orchestration service? The post is essentially just content marketing for Porter. This is like a case study in what not to do and I think a future followup to this post will read like a mea culpa. The level of complexity they took on unwittingly is massive, and it seems like little research was done if they chose EKS -- which is e…

As someone who hasn't used Porter, it would be awesome if you could follow up this oh-so-snarky response with some actual concrete information? * What is the "unwittingly massive" level of complexity that they took on? Sure, k8s is complicated, but isn't the promise of this platform that it abstracts away all of that complexity? After all, AWS is very complex but we don't say that Heroku users are unwittingly taking…

AWS copilot is a great CLI for orchestrating ECS stacks. Takes a lot of the pain away

Re: Migrating from Heroku to EKS

#23

Post by MuffinFlavored »

mrj wrote: post #2

Porter looks cool and I would love to not hand roll kubernetes stuff. But the pricing looks curious. Their "default infrastructure" is $300 a month set up in AWS plus usage costs on Porter. It's already 6x what I'm spending on Heroku, why would I pay usage costs per CPU to Porter if they're not running any CPUs? Honest question really because I'm interested, it just seems far out of line price-wise. I would totally p…

> Porter looks cool and I would love to not hand roll kubernetes stuff.

    cat ./yaml/applications/kubernetes-dashboard.yaml | ./scripts/kubectl-apply.sh && ./scripts/run-argocd-sync-and-wait-pipeline.sh "kubernetes-dashboard"
What am I missing?

Re: Migrating from Heroku to EKS

#24

Post by nasmorn »

DancerOfFaran wrote: post #5

So they went from Heroku buildpack-based ops, to Kubernetes on EKS, through a 3rd party orchestration service? The post is essentially just content marketing for Porter. This is like a case study in what not to do and I think a future followup to this post will read like a mea culpa. The level of complexity they took on unwittingly is massive, and it seems like little research was done if they chose EKS -- which is e…

I just managed to get a client off their desired path to use kubernetes and set them up with ECS Fargate where they can actually make the real ops work someone else’s problem.

Re: Migrating from Heroku to EKS

#27

Post by rcarmo »

Nice, but... Anything simpler that one can deploy atop one's own K8S? There were a few dokku-inspired things that would generate the right manifests and leverage the same build packs, but things seem to have stalled on that front and "simple" solutions are thin on the ground.

Re: Migrating from Heroku to EKS

#28

Post by mrkurt »

itake wrote: post #20
DancerOfFaran wrote: post #13

Earlier quoted context omitted.

I've felt like v2 is MUCH better than the v1 system, and pricing is still much better than alternatives. With that said, our core systems are still on GCP and we use Fly exclusively for Next.js UIs so the comparison is to systems like Netlify and Vercel, both of which are far less reliable in our experience, and far costlier (Netlify is at the point of nickel and diming people).

I'm more annoyed that I had to deal with the change. The migration took a couple hours and I'm still not sure if I configured it correctly to mirror the v1 setup I had. They also changed regions during the migration. My db (hosted in a different app) was in LAX, but the new machines were in SEA.

This was a bug, I'm sorry we broke your app. We stopped migrations when we hit this issue and wrote a bunch more tests. I know this doesn't help you specifically, though.

Re: Migrating from Heroku to EKS

#29

Post by josegonzalez »

rcarmo wrote: post #27

Nice, but... Anything simpler that one can deploy atop one's own K8S? There were a few dokku-inspired things that would generate the right manifests and leverage the same build packs, but things seem to have stalled on that front and "simple" solutions are thin on the ground.

Dokku [deploys to Kubernetes](https://dokku.com/docs/deployment/schedulers/kubernetes/) with an officially maintained plugin and we have a few folks actively using it.
Post reply on HN