31–40 of 58 posts
Earlier quoted context omitted.
I downvoted this because even though I like it, it belongs at the bottom of the conversation below any real discussion of the actual article.
Personally I think it belongs at the top. When the article looks like it is generated by the buzzword generator, that should be the real discussion.
Why would GCP restrict the ports like this?
GCP has a lot of ports restrictions. A place I used to work at migrated from GCP to AWS because they don't allow port 25 incoming; if you're doing e-mail, you 100% need this.
I've yet to see a compelling argument for the complication of kubernetes or the 'its not AWS' nature of GCP over a bog standard AWS ALB with ECS cluster tasks attached to it.
Earlier quoted context omitted.
Personally I think it belongs at the top. When the article looks like it is generated by the buzzword generator, that should be the real discussion.
It's quite a good article with a solution for a real problem. That it looks like a buzzword generator to HN says more about HN than it does about the article, IMO.
CLOUD NATIVE DEVOPS RAFT-BASED BLOCKCHAIN-ENABLED MULTI CLOUD RESILIENT CONTAINERIZED MULTI-REGION MULTI-AZ static blog generator.
I downvoted this because even though I like it, it belongs at the bottom of the conversation below any real discussion of the actual article.
I've yet to see a compelling argument for the complication of kubernetes or the 'its not AWS' nature of GCP over a bog standard AWS ALB with ECS cluster tasks attached to it.
Because k8s mostly prevents lock-in. A much better idea is to run EKS on Fargate. You still won't have to manage a cluster, but at least you can now use standard k8s manifests that work in any other cluster instead of the ECS homebrew stuff. You can keep ALB, because ALB can run as an Ingress Controller.
AWS is the VMWare of our age, you'll never get fired for suggesting it. There are workloads that are inappropriate for it (see: Dropbox) but those are few and far between.
I've yet to see a compelling argument for the complication of kubernetes or the 'its not AWS' nature of GCP over a bog standard AWS ALB with ECS cluster tasks attached to it.
This seems to be a common rhetoric from people who have not invested the time in k8s. It is not as complicated as people think.
Also not having load balancer support built in kills it for me. Yeah you can do metallb or nginx ingress but it means they punted one of the major components needed to make it, 'cloud agnostic.'
Meanwhile in AWS we have ECS which works out the box on fargate, their EC2 hosts, or your own EC2 hosts and on hardware I can easily get (and dev) on docker swarm.
Why would GCP restrict the ports like this?
GCP has a lot of ports restrictions. A place I used to work at migrated from GCP to AWS because they don't allow port 25 incoming; if you're doing e-mail, you 100% need this.
The point is to make sure that anything sending email from GCP has someone properly attending to it, so that GCP does not become a source of spam, rather than to prevent email service providers or the like from using GCP.
For many companies that aren't an email service provider, it's often a better use of IT funds to send via one anyway, given how much work is involved in maintaining security and deliverability of an outbound email server in 2020. Most of those support sending through ports that aren't 25, and Google has some nice free tier deals for GCP customers.
Is the title peak buzzword-era, or is there more to come?
However, this is embarrassing to GCP that this isn’t easier. These were very basic requirements from this customer, yet so much rigmarole was needed to get it set up.
CLOUD NATIVE DEVOPS RAFT-BASED BLOCKCHAIN-ENABLED MULTI CLOUD RESILIENT CONTAINERIZED MULTI-REGION MULTI-AZ static blog generator.