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.
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.
>The default installation of Kubecost includes an optimized Prometheus server that only contains metrics that are useful to Kubecost. This optimized version retains 70-90% fewer metrics than a standard Prometheus deployment. You can also use an existing Prometheus installation.
I really like this approach. What do customers say about it?
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.
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.
I should've said "limited in usefulness for detecting moderately-clever attackers" rather than just flat-out "useless". Monitoring is obviously a useful tool regardless of whether it will always help you detect attackers in your network. You could use nf_conntrack on the host as well but that could also be bypassed by a root process on the host.
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.
It's pretty free. Hacker News loves the corrections. All good.
I founded and ran a good part of an A-round startup for a while.
I'm aware what stock does to equity, but it has minimal value to employees if it's not going to be a thing, and for a startup watching burn rate, it's pretty freaking free.
Are you going to give it all up and waste the option pool? Of course not. To me, I'd rather have employees with a good chunk of the equity because they were all doing a good chunk of the work, but I also want to see them treated well in stock. And you know your thing might not work out. Being stingy to employees with stock doesn't feel right.
I don't believe in founders hording stock when everybody working for them built a good chunk of what they sell. They should keep a decent chunk, but sharing stock well is basic ethics and costs nothing on the burn rate. It's the same reason I don't believe CEO's should make 50x of what an employee makes in a given year.
Stock is pretty cheap to give away in a startup. It's not cheap in a private company. I do especially object when it's used in lieu of market-rate compensation on the hope of future gain, with "we're giving you lots of stock" and then expecting the long hours and then it doesn't pay off for folks.
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.
