Hacker News Reader

Comment by sheepo39 | Hacker News Reader

I hate when open source projects (especially common in the Kube-sphere I feel) adopt these super buzzwordy roles in their announcements.

View on HN

What is super buzzwordy to you?

API Gateway is a bit of a buzzword. I think part of it's because of Amazon API Gateway. People like to imagine they're recreating big parts of AWS, and a lot of Amazon's other products have names that are trademarked or are clunky to use.

I mean, the title says Gateway API, because it's literally about an API named Gateway. Idk how you avoid it.

The text repeats it a lot. Maybe more than it should. Also GatewayClasses. It’s nitpicky, but I’m trying to understand OP’s comment.

The Kubernetes API is structured as "resources". (I'm oversimplifying but it's OK for what we are going to explain here).

In this case. Gateway is merely a new resource type introduced to replace the aging and inadequate Ingress resource. GatewayClass was introduced alongside it as a way for the infrastructure providers to define essentially a "template" for how Gateways can be created that are tied back to a specific implementation.

This is similar to how StorageClass and PersistentVolume (two other resources) already work for defining block storage in Kubernetes.

This isn't buzzword soup and the original commenter just has no clue what they are talking about so there isn't any point in defending their potential point because there isn't one there. The text repeats these terms a lot because they are what are being discussed, as in -concrete- things. Not buzzwords.

FWIW I hate buzzwords, marketing and pretty much everything else of that ilk. Talk is cheap, show me the code. In this case, this is the code.

I understand what GatewayClass means and still think it could have been repeated less. I didn't say it was buzzword soup. I think it's good but I wouldn't want this to become the prevailing style.

This paragraph:

> Subsequently, cluster operators utilize these GatewayClasses to deploy gateways. A Gateway in Kubernetes' Gateway API defines how external traffic can be directed to Services within the cluster, essentially bridging non-Kubernetes sources to Kubernetes-aware destinations. It represents a request for a load balancer configuration aligned with a GatewayClass’ specification. The Gateway spec may not be exhaustive as some details can be supplied by the GatewayClass controller, ensuring portability. Additionally, a Gateway can be linked to multiple Route references to channel specific traffic subsets to designated services.

Well it's the subject of the vast majority of the sentences. I fail to see how you can write this information in a way that doesn't use it multiple times without going out of your way to imply the subject instead of just stating it clearly as is done here.

Unfortunately, in terms of Kubernetes this is written pretty clearly about what it’s doing and how it interacts with other parts.

It's OK, but almost impossible to search.

At least when using Google search where double-quotas seem to be not always understood as the "required term" anymore.

Especially that API Gateway used to encompass several more services provided by middlewares than the rather limited AWS one.

Since I got downvoted, anyone could explain what is incorrect with my statement?

Reply on news.ycombinator.com