webb

To give engineering, platform, and other teams a (multi-cloud) cost monitoring that is standardized across all major providers...

I've actually worked with 100+ companies that use labels heavily. It's way more common when you have multiple engineering teams and nobody everybody knows all projects in a cluster. Also, it's common to start with namespace labels which are generally easier to manage.

Yeah, I agree. I actually think that labels are a much better fit for this reference.

> Instead, Kubernetes annotations are meant for sharing information with other colleagues. For example, you may use an annotation to record the phone number of the person responsible for a pod

But it can be super helpful to put owner/contact info for alerting purposes as teams scale.

I also agree that having this metadata on the controller is helpful.

Thanks, simonebrunozzi!

With a growing number of teams using Prometheus-based observability solutions, we've seen more and more integrating Kubecost with their existing Prometheus. The majority still use our bundled offering, which is typically a little easier to setup, but many likely the flexibility to switch if desired.

There would be a number of differences with these products. First, Kubecost does not egress any data from your infrastructure, it's based on open source technologies (e.g. Prometheus), and because it is build specifically for Kubernetes it takes a pretty different approach for determining the cost of a tenant, workload, etc.

Disclaimer: I'm a founder of Kubecost.

I agree that appropriate configuration/policy management is part of the solution for preventing these attacks on Kubernetes, but our view is that monitoring also plays an important role.

Today kubecost is different in a number of ways 1) open source with easy installation 2) exclusively focused on kubernetes-centric infrastructure and 3) offers a fully deployed solution.

Giving out stock can be far from free..

Matt, my recommendation would be to address your parents' situation before trying to handle everything going on in your personal life. If they approaching a condition where they will be unable to take care of themselves there are ways to respectfully bring this to their attention. You will get your career back on track. But you may not get your parents back on track if they injure themselves due to lack of assistance as one of my grandparents did.

Not much different than building an iPhone interface programmatically. They recently bundled the GWT Designer, which is a WYSIWYG layout tool. UiBinder is another option that let's you build interfaces in XML.

Strange. What browser? Just tested in chrome, safari, and firefox and it works fine.

I know this is a broad statement on my part. Apples says the following in the hello world tutorial, "In general, however, you should try to avoid using autorelease wherever possible since it means memory may be reclaimed later than it would be if you used release."

I don't know the history here, but based on the autopool directives it looks like they toyed with the idea.