231–240 of 266 posts
I'm literally not surprised... https://github.com/weaveworks/weave/issues/3868#issuecomment... And my comment: "Why would someone pay for something that is broken?" If you only prioritize work for paying customers, and don't do things to grow ... you'll eventually die from attrition.
They clearly do not understand how to engage with the community.
That whole CloudNative industry seems to be going downhill since the end of the free-money era. It is surprising that it took that long. Very few companies really have the need to run at scale distributed systems on K8S. But as soon as you get into that world, you suddenly need an operational team of 15 people to manage the 50000 moving pieces in that ecosystem.
Of the maybe hundred of companies I've worked with trying to onboard to Kubernetes, I don't think a single one really had a use case that justified the increased complexity.
Kubernetes seems so great until you're suddenly drowning in YAML, un-upgraded clusters out of their support window, the need for an unbelievable amount of extra tooling (e.g. ArgoCD, Helm, CSI plugins, Operators), etc.
Plenty of places made it work by paying for huge teams to manage it, but deploying software on regular old Linux servers is fine for most people with just a small amount of discipline.
Use boring technology.
Can someone please explain what this company actually did? I’m not a cloud person per se, but I find it strange that I’ve never heard of them given the overwhelming number of people here who are familiar.
Outside of the Containers / Cloud Native world, not much. But they were the 10th-biggest contributor to Kubernetes as of 2020, which for a ~50-person company is something. Weaveworks created “GitOps” as a buzzword. Weaveworks created and/or substantially funded these Open Source projects: - FluxCD - Cortex (scalable Prometheus) - Weave Net - Weave Scope (seen in 2023 KubeCon keynote) - EKSctl - Kubeadm - Kspan Plus m…
Earlier quoted context omitted.
> Something is clearly better than nothing. To you and I, this is patently obvious. This is not true however for VCs. In a lot of them, they'd prefer you fail entirely rather than limp along making 1x, 1.5x their investment. Zeroing out is preferable sometimes, weirdly.
Do you have any sense why this is true? I get preferring (10x or 0x) to (1.5x). I don’t get preferring a near-certainty of 0x to some recovery of their capital with a pivot to selling a smaller-but-sustainable business. Is it something like they’re measured by LP’s (or someone?) on only non-zeroed investments?
Earlier quoted context omitted.
> Also it really feels like all the air has been let out of the docker/kubernetes/cloud-native balloon that was so popular in the late 2010s. Not really, the space has simply grown faster than these companies could keep up with and were left behind. I can code up a CICD pipeline that does per-PR namespace isolated deploys of an app stack on EKS using Github actions in well under a week. With docker compose for local…
How does your pipeline work with an app that requires many other services to work?
As of a year ago this is possible in a fully declarative way with Flux 2, but there’s a lot more moving parts and security footguns - and the idea that the maintenance of this project has lost one of its primary sponsors is worrying at best.
https://github.com/fluxcd/flux2/discussions/831
https://blog.kluctl.io/introducing-the-template-controller-a...
I know this isn't the craziest startup shutdown story, but wow. At $10MM of revenue they can afford to keep a staff of 50 at a fully loaded cost per employee of $200,000. Yet, according to Linkedin they peaked at nearly 200 employees. On top of this, they appear to have raised $36 million three years ago - https://www.weave.works/press/releases/weaveworks-raises-36-... In other words they somehow were running at a lo…
> According to the CEO's linkedin post, they were basically trying to keep up appearances of being a 200 person company until some greater fool bought them out, which appears to have failed. Because that is what startups do. 80% of startups that are "successful" follow this pattern You shoot for the moon, if you don't take massive risks, then you won't be rewarded. It sounded like they were about to be bought out or…
Earlier quoted context omitted.
Outside of the Containers / Cloud Native world, not much. But they were the 10th-biggest contributor to Kubernetes as of 2020, which for a ~50-person company is something. Weaveworks created “GitOps” as a buzzword. Weaveworks created and/or substantially funded these Open Source projects: - FluxCD - Cortex (scalable Prometheus) - Weave Net - Weave Scope (seen in 2023 KubeCon keynote) - EKSctl - Kubeadm - Kspan Plus m…
But what do you pay them money for? What problems do they solve for you?
Then commercial versions of some OSS projects.
Probably consultancy was the biggest revenue source overall.
Earlier quoted context omitted.
Outside of the Containers / Cloud Native world, not much. But they were the 10th-biggest contributor to Kubernetes as of 2020, which for a ~50-person company is something. Weaveworks created “GitOps” as a buzzword. Weaveworks created and/or substantially funded these Open Source projects: - FluxCD - Cortex (scalable Prometheus) - Weave Net - Weave Scope (seen in 2023 KubeCon keynote) - EKSctl - Kubeadm - Kspan Plus m…
But what do you pay them money for? What problems do they solve for you?
Earlier quoted context omitted.
Probably most popular thing they built was FluxCD if you are confused where you have heard their name before. Their company provided a ton of extra tooling and consulting around the product. Hopefully as FluxCD user, this doesn't impact the development of Flux.
People like the weave network policy controller too.. at least in the earlier days of kubernetes, their cni was pretty popular for awhile.
Earlier quoted context omitted.
Kinda surprised anyone would still using WeaveNet as a CNI.. it was a bit of a dumpster fire: https://blog.quentin-machu.fr/2020/08/07/our-breakup-with-we...
It has been 100% fine for me, was easiest to deploy, very easy to encrypt all network communication. Has been anything but a dumpster fire, will likely wait it out a see what happens with the plugin, rather than switch to something else.
https://github.com/rajch/weave/tree/reweave
If you use Weave net still, definitely follow his work and consider learning to build the image, so you can keep it ahead of CVE scanners. (You are using a CVE scanner in your clusters, right?)