cost-model VS Kong

Kubecost gives you insight into where your Kubernetes spend is going. You can view your spend per namespace, service, or even team, and you can set budgets and get real-time alerts. Kubecost can also track other cloud spend from things like RDS and S3, and it also works with on-prem k8s clusters. Kubecost also offers an open source version.

kubecost - analyse cost of the cluster https://kubecost.com/

> No inheritance - no more digging through the massive world-tree of objects to find the code that actually does things.

That's not 100% accurate; as a concrete example, tell me which files (to say nothing of the actual downstream types!) contain the implementations of this interface method: https://github.com/kubecost/cost-model/blob/v1.88.0/pkg/clou... (err, without using github's fancy new SourceGraph-lite integration, of course, that'd be cheating)

I find the sibling "No declared interfaces - they are defined at the point of use, not declared elsewhere" similarly suspicious, but suspect we'd having a nomenclature mismatch

Kubecost (Stackwatch) | Senior Support Engineer | Remote (US-East/Central preferred) | https://kubecost.com

Our tooling and intelligence empowers teams to efficiently operate Kubernetes at scale—helping them manage cost, performance, and reliability. We're avid contributors to the open source community.

We're looking to add a second Senior Support Engineer to help us build a scalable, user-first support process, troubleshoot complex infrastructure issues, and influence the direction of our product by tracking and communicating user needs. Be one of our first 20 teammates!

Feel free to apply or reach out to us directly with your CV at [email protected] if you're interested!

Check out all of our open roles here: https://angel.co/company/kubecost/jobs

Kubecost (Stackwatch) | Senior Support Engineer | Remote (US-East/Central preferred) | Full time | https://kubecost.com

Stackwatch is a tight-knit, fast-growing team on the leading edge of cloud infrastructure technology. Starting with our flagship product Kubecost, we build tooling and intelligence that empowers teams to efficiently operate Kubernetes at scale—helping them manage cost, performance, and reliability.

As our second Senior Support Engineer, you’ll help us build a scalable, customer-first support process, troubleshoot complex infrastructure issues for our users, and influence the direction of our product by tracking and communicating customer needs. We’re looking for someone who is as passionate about our product and customers as we are—as one of our first 20 employees, you’ll have the opportunity to shape the future of our support organization and technology.

Feel free to reach out to us directly with your CV at [email protected] if you're interested!

NB: also hiring for Senior Software Engineers and Go-to-market!

Lens is the most powerful IDE for those who need to deal with Kubernetes clusters on a daily basis. It allows you to manage your cluster and view important health metrics. A Kubecost and Lens integration allows you to also visualize Kubernetes costs directly in the Lens UI. With Lens and Kubecost you can view costs and spend efficiency by namespace, pod, deployment and more!

First you have to be aware of your costs :) This open source project can help https://kubecost.com, `helm install` and get started in 5 minutes

Happy to share some of the lessons we've learned if you want to reach out to team [at] kubecost.com. We worked on this problem at Google before launching Kubecost open source.

Kong: A cloud-native, fast, scalable, and distributed Microservice Abstraction Layer (also known as an API Gateway or API Middleware). Made available as an open-source project in 2015, its core functionality is written in Lua and it runs on the nginx web server.

OPeNsOuRcE. Good time to switch to Kong, better option anyways.

Sounds like you want an API gateway? What about Kong?

Unquestionably no, Kong is "OpenResty plus a management plane" and they're Apache 2: https://github.com/kong/kong#license

Kong (https://konghq.com) | Gateway Senior Engineer | REMOTE Europe | Full-time

The Kong Gateway is an API Management solution, which serves as a foundation for many other solutions by the company. The business model is open-core: an Open Source solution exists (https://github.com/kong/kong), and there's an Enterprise version with more features and dedicated support.

The tech stack is a modified Openresty with of Lua code on top. The ideal candidate would be someone who is already familiar with Kong. Alternatively, if you are familiar with Openresty or other API management solution, we also would love to talk with you.

I am personally interested in finding people to join me in the European Gateway Team. The role involves adding features, fixing bugs, and collaborating with other teams. Here's that position:

https://jobs.lever.co/kong/c1a2b204-45a8-4c19-9cd4-d9824a778...

We have many projects and many teams all around the world (current headcount is ~450), using other technologies like Node in the Kong Manager or Go in the Koko project, and we are constantly looking for people. Please visit our careers page to find out more!

https://konghq.com/careers/

Kong Gateway allows the complexity of service-tier APIs to be reduced to a collection of endpoints (or URIs) focused on meeting a collection of business needs and functionality. Often-duplicated components (like authentication, logging, and security) are handled by the gateway and can be removed from the service-tier design.

I am seeing different companies taking different approach. I am not sure anymore where each should be actually used. On top of that tech like Kong make me question whether API Gateway should be one thing for all. Some perspective into this would be really appreciated.